In traditional waterfall type, we emphasize on more documentation.But in agile project management, what are the minimum and key documentation we have to prepare ? Saving Changes...
Sort By:
Greg RobinetteDirector of ERP Services| Herdt ConsultingRichmond, Va, United States
I don''t think that AGILE represents a departure from documentation but a focus on documentation being second to production of value generating elements. The documentation also has value but is not a focus, it is less important than the output but still important. To keep it in focus in IT projects I have created documentation user stories that are weighted and delivered for a given sprint. They are important but not more important than the software developed for a sprint. Saving Changes...
Thanks Greg.But Is there any equivalent documents of traditional model -project charter , scope , risk register etc.to be used in agile projects? Saving Changes...
Priya PatraDelivery Director| Capgemini India Technology Services LtdMumbai, India
I keep getting these questions.. does agile mean "No documentation " in every forum I go to :).
Being Agile doe snot mean we stop documenting, it just means we do just enough documentation. We actually go for tool based documentation, we use confluence for documenting our use cases, technical documentations, reviews / review comments etc. Saving Changes...
The point here is "just enough" - and this can vary from project to project. If you have to produce documentation for legal or compliance reasons you will do so - because otherwise there would be less or even no value in the increments/product. Simple as that. The task is to identify what is r e a l l y necessary. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
There is a big mistake outside there. You can apply agile with waterfall life cycle. The mistake is some people mix life cycle (iterative, waterfall, V, etc) with approach (agile, lean, predictive, etc) with method/methodology (PRINCE2). That is a big mistake. In fact, there is not "agile project management". There is project management that you apply in a combination of approach/life cycle/method. So, documentation is the result of an activity in some organizational process. Documentation must be keep inside a configuration management environment to give it the value it deserves. Saving Changes...
