Email	Print Reprint
	add to:
	Del.icio.us Digg Google Furl	Slashdot Y! MyWeb Blink
	TABLE OF CONTENTS The Discipline of Regular Delivery The Discipline of Quality The Discipline of Active Stakeholder Involvement Discipline at Scale The Discipline of Teamwork

The Discipline of Teamwork

Agilists, when given the opportunity, will rarely work alone because they know it is too risky to do so. It requires discipline to follow non-solo practices such as pair programming and modeling with others because it's too easy to assume that you're smart enough to get the job done quickly by yourself. It also requires discipline to be responsible for the entire system, not just your little part of it, motivating you to work closely with and thereby learn from people with different backgrounds than your own.

It requires discipline on the part of management to stay out of people's way and allow them to self organize, even when it's clear that the team is likely making a mistake, and not try to plan everything in detail for the team. Providing people with learning opportunities such as this can be frustrating at times but is absolutely critical for growing your staff. Another aspect of agile project management discipline is the act of holding a daily stand up meeting to promote communication within the team about issues that really matter, such as what everyone is doing and what problems they're running into. This forces you to confront and deal with problems as they arise, instead of papering them over with overly optimistic status reports.

Agile software development, when done properly, is highly disciplined. Agile is much more highly disciplined than traditional development, which in turn is more disciplined than code-and-fix development. If anyone tells you that Agile isn't disciplined, then ask if they have ever been involved with an Agile project, and if so, whether it met the criteria defined earlier. I have yet to meet someone with both real-world Agile and traditional experience who claims that traditional is more disciplined, and it appears to me that traditionalists are clearly throwing stones in their glass house by claiming otherwise.

I'd like to thank Ted Rivera of IBM for his detailed feedback regarding the initial draft of this column and Bill Krebs, also of IBM, for the various insights that I gleaned from him in the conversations that we've had around this topic.

How to Tell the Agilists from the Code-and-Fixers Sadly, there is no official definition for "Agile Software Development" against which you can determine whether a team is agile. However, I've found true Agile teams: • Take a test-driven approach to development. • Work very closely with their stakeholders on a daily basis, and the stakeholders have active roles on the team. • Produce working software on a regular basis and can show a clear track record of doing so throughout the project. • Work in an open, collaborative, and self-organizing manner. —SWA

Previous Page | 1 The Discipline of Regular Delivery | 2 The Discipline of Quality | 3 The Discipline of Active Stakeholder Involvement | 4 Discipline at Scale | 5 The Discipline of Teamwork

RELATED ARTICLES OutSystems Updates Agile Platform Danube Releases ScrumWorks Pro 4.1 Agile Self-Evaluation Tool Released Why We Need a Theory for Software Engineering Nokia Takes Task Management For A Spin		TOP 5 ARTICLES No Top Articles.