Section 3.7. Evidence That Phase 1 Is Complete


3.7. Evidence That Phase 1 Is Complete

There are only two requirements to complete Phase 1: planning in fixed-length development iterations and delivering functionality instead of components. When you have completed at least one time-boxed iteration where you can demonstrate customer-visible functionality, you have completed Phase 1.

Remember that you must continue to focus on moving toward agility. Under pressure, it's normal to revert to your usual behavior, so continue to make decisions based on this question: Which option puts more functionality in my customer's hands at the end of this iteration?

The risk that normally comes with developing functionality in iterations is that the design of the code will degrade as changes are layered on top of each other. In the long term, you will use agile techniques like source code refactoring and automation to reduce this risk, but at this phase of the transition, you still have designed the system in the traditional way, so your code should be structured to allow those subsequent modifications. If you start seeing the quality of the design degrade, look to source code refactoring to help you resolve those issues.




Refactoring to Agility
Refactoring to Agility
ISBN: B000P28WK8
EAN: N/A
Year: 2006
Pages: 58

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net