Continuous Documentation

Document only what is necessary and reflecting the final deliverable

Agile software is built in iterations, as the team learns from their users what are the most valuable functionalities that are expected. As such, documentation must wait for the stabilization of the information, but not delay so much as to miss out on the opportunity to capture the knowledge as it is being digested. With the passage of time the team will face other challenges and may forget details of what was constructed in each iteration.

Continuous documentation attempts to capture the iteration's knowledge as it is solidified into a deliverable. Teams may choose to capture during each sprint, after a sprint is completed, or as epics are completed. The choice of the team depends on its composition, delivery cadence, maturity and other aspects - but documentation must be captured as the project matures.

Related Articles Show Summaries