| Chapter 61 Review Draft - Defining Done |
|
|
|
| Tuesday, 12 February 2008 | ||||||
|
Please send me / post comments and feedback on this chapter! "Are you done yet?" The answer to this question may sink your career, your team and your project. If you respond with a "yes," you may be forced to take on additional work. If you say "no," you may be branded as someone who can't get things done. This innocent question is asked countless times on almost every software project. The way we answer, however, is anything but innocuous. If team members’ answers vary, it can degrade stakeholders’ trust in the project team. Establishing an upfront, common understanding of "done" can save teams and businesses countless hours of refactoring, process-thrash, unclear communication and hidden work. In this chapter, you will learn what a done list is, how it adds value, and the value it communicates to stakeholders. Then, I’ll present an exercise that will help you build your own done list and manage it over time.
Powered by !JoomlaComment 3.12 Copyright (C) 2007 Alain Georgette / Copyright (C) 2006 Frantisek Hliva. All rights reserved. |
||||||
| < Prev |
|---|