This Executive Update takes the thinking presented in my last Update ("Enterprise Architects and Organizational Change: A Requirement or an Option?")1
October 28, 2009 | Authored By: Paul Teeuwen
Showing 1201 - 1220 of 2385
Give a software team an interesting project and you will have a group of happy campers -- true or false? Well, you might say, interesting projects are fine, but team performance is also influenced by good management and a decent salary. Very few happy campers earn a poor salary.
July 1, 2004 | Authored By: E.M. Bennatan
Measuring Up to Metrics
February 28, 2005 | Authored By: E.M. Bennatan
You'll likely decide to make the transition to agile if there is a compell
August 3, 2009 | Authored By: Bob Fischer
In this Executive Update and the concluding one that follows, we continue our examination into the subject of lessons learned based upon the results of a recent Cutter Consortium survey.
January 31, 2006 | Authored By: Robert Charette
Volume 1, No. 4; December 2002
November 30, 2002 | Authored By: Tom Welsh
February 28, 2005 | Authored By: Kenneth Rau
Only recently have most companies started to seriously consider the changes they must make to their core information systems in order to successfully deploy major appli
December 31, 1999 | Authored By: Daniel Riscalla, Paul Harmon
Volume XII, No. 1; January 2002
December 31, 2001 | Authored By:
Abstract Agile adoption initiatives both succeed and fail, and t
December 31, 2008 | Authored By: Amr Elssamadisy
In Part I of this two-part Executive Update series, we explored the value of architecture and the function of the architect.1 Here, we discuss the various stag
March 7, 2009 | Authored By: Charles Bess, Philip Mullis
Enterprise architecture (EA) managers often wonder about the best way to organize the EA department, but before addressing that issue, we first must answer the question, "How many architects do we need in the first place?" Of course, there is a difference b
December 27, 2009 | Authored By: Paul Teeuwen
The Software Modeling Revival
July 31, 2004 | Authored By: E.M. Bennatan
Design notations, such as UML, and long-lived design documents have at least one advantage: if you're overseeing the work of a software team, they are tangible, auditable deliverables that allow you to assess the team's design practices.
July 1, 2009 | Authored By: Laurent Bossavit
INTRODUCTION Ah yes, the much endorsed, much maligned business case. Before I dive into the business case for visualization, let me share some assumptions regarding business cases that will guide this discussion.
March 1, 2006 | Authored By: Vince Kellen
Volume IX, No. 7; July 1997
June 30, 1997 | Authored By:
This Executive Report explores what you can do as the leader of your IT organization to promote more effective leadership at all levels and by all members of your team. By developing the capacity of people to think, act, and respond as leaders to the situations they encounter, you will build a stronger organization and achieve your goals more effectively.
October 7, 2014 | Authored By: Moshe Cohen
It has become fashionable to design and develop business systems by starting in the middle, with the latest technological or e-commerce fads, which, supposedly
July 31, 2002 | Authored By: Haim Kilov