Ken Orr wrote ( in Cutter IT Journal Vol.3, No. 7 ):

Agile . since Jun 23 . Index . DOCs TOP TOC

NOTES


1When I started writing this introduction, I was quite proud of my analogy of Luther's 95 Theses and the Agile Manifesto. Unbeknownst to me, Cutter Consortium Fellow Robert Charette had not only picked up on the same analogy, but he had done one better by dressing up like Luther at a software conference and tacking a copy of the Agile Manifesto to a fake cathedral door!

2Most students of technology recognize the importance that the DOD Advanced Research Project Agency played in the development of high technology. This organization gave early support of research into computers, software, databases, and, of course, the Internet. Other major technology research funding came from various military and intelligence services.

3To be honest, DOD has never been as successful in its software management activities as it has with its hardware, but, then again, no other organization has been uniformly successful when it comes to developing really large, state-of-the-art software systems.

4DOD has reinforced this by making systems development and systems management methods part of the standards that vendors must comply with to get DOD projects.

5According to the SEI, roughly 40% of all CMM Level 4 and Level 5 certifications are for Indian firms.

6It is important to note that CMM means mostly software management processes such as estimating, scheduling, quality control. The CMM has historically been faulted for its lack of interest in product development process, which we will see is where agile development excels.

7One of the most controversial ideas behind CMM is whether the software development process can be managed as closely as a manufacturing one. Indeed, there are a number of major thinkers that consider the idea of quality CMMs as fundamentally flawed.

8Council Fellow Ed Yourdon remarked that there was less cultural resistance to the kind of structure imposed by CMM in India than in the US. How much of a role cultural differences play in implementing rigorous software processes is still an open question.

9In response to the criticism about CMM's lack of objectivity, the SEI has created a measurement program to support CMM certification; this program is called the Software Engineering Measurement and Analysis Initiative.

10There are some notable exceptions, of course. Council Fellow Jim Highsmith, author of two influential books on agile development [2, 3] is a pioneer in systems methodologies going back to the 1970s. Cutter Consortium Fellow Robert Charette, Steve Mellor, and Ken Schwaber are other greybeards that have joined forces with the agile camp.

11There are a number of other agile methodologies that have signed on to the Agile Manifesto. Some of the better known are Scrum, Dynamic Systems Development Method (DSDM), Feature Driven Development (FDD), and Crystal Light. All of these methods share most of the basic tenets with XP, especially the high level of user involvement and the importance of rapid prototyping.

12Throughout this section, I use XP and agile development interchangeably since XP is arguably the best known and best documented of all the agile development approaches.

13My own personal opinion is that automated refactoring tools will become more and more important to the success of agile development projects.

14In true team environments, the team succeeds -- individuals only succeed as part of the team.

15Recently, a friend of mine related a story of why "team teaching" had failed in a specific university setting. It was concluded that team teaching failed because many, if not most, university professors go into teaching because they prefer working alone. Even if team teaching might be better for students, it didn't fit the personality profiles of the teachers.

16As you can see in our earlier discussion, agile development is clearly not an undisciplined programming approach; however, it's how many people from a more traditional standpoint see the movement.

17The CMM folks maintain that CMM and agile development are compatible. Barry Boehm in a recent dialogue with Council Fellow Tom DeMarco maintained that some CMM Level 5 organizations are working to integrate the two approaches.

18To quote Council Fellow Tom DeMarco, "The truth will make you free, but first it will make you miserable!"

19Fragging is when an officer is shot, usually in the back, by his own troops.

Agile . since Jun 23 . Index . DOCs TOP TOC

REFERENCES


1. Beck, Kent. Extreme Programming Explained. Addison-Wesley, 2000.

2. Highsmith, Jim, and Ken Orr. Adaptive Software Development: A Collaborative Approach to Managing Complex Systems. Dorset House, 2000.

3. Highsmith, Jim. Agile Software Development Ecosystems. Addison-Wesley, 2002.

4. Humphrey, Watts S. Managing the Software Process. Addison-Wesley, 1989.

5. Humphrey, Watts S. "Three Dimensions of Process Improvement (Part I: Process Maturity)." Crosstalk, February 1998.

6. Raynus, Joseph. Software Process Improvement with CMM. Artech House, 1998.

Agile . Index . DOCs . TOC