|
Agile Software DevelopmentDocumenting chunks of the methodology is not at all the same as providing understanding, and having understanding does not presuppose having documentation. Understanding is faster to gain, because it grows through the normal job experiences of new employees. · The second is that the needs of the organization are always changing. It is impractical, if not impossible, to keep the thousand-page text current with the needs of the project teams. As new technologies show up, the teams must invent new ways of working to handle them, and those cannot be written in advance. An organization needs ways to evolve new variants of the methodologies on the fly and to transfer the good habits of one team to the next team. You will learn how to do that as you proceed through this book. Reducing Methodology Bulk There are several ways to reduce the physical size of the methodology publication: Provide examples of work products Provide worked examples rather than templates. Take advantage of people's strengths in working with tangibles and examples, as discussed earlier ...» |
Код для вставки книги в блог HTML
phpBB
текст
|
|