Scrum Documentation: Here is what you need

New and experienced scrum practitioners often have questions about scrum documentation. Some are of the mind that, “If little documentation is good, then none is better”, while others have the standpoint of “If we don’t have documentation, what will we do when we need to look backward?” Like many things, the answer is somewhere in the middle. Note: For the sake of illustration, in this article I am excluding regulated industries with more strict and prescribed documentation/compliance requirements.

Typical Examples of Agile Documentation

Here are some of the typical documentation/artifacts you would need as part of your agile project:
Product Backlog: The product backlog is an ordered “wish list” of all the features of the product. It’s maintained by the product owner and is periodically refined to ensure the most valuable items are at the top, and the less valuable items are near the bottom. ┬áThe product backlog typically takes the form of a collection of user stories.

Release Plan: A release plan helps us understand the general direction of the release from a feature perspective, and gives us a more holistic view of what we are developing.

Sprint Plan: A sprint plan is a list of items (usually a subset of the release plan) that will be worked on in each sprint.

Task Board: A task board is a simple kanban board that helps us understand what is not yet started, what is in progress, and what is done in our sprint.

Sprint Review Deck: A sprint review deck is a short presentation that helps communicates to stakeholders what has been completed this sprint, and what to expect for the next sprint.

Sprint Retrospective Backlog: A sprint retrospective backlog is a backlog of improvements that have been decided on in the sprint retrospective.

Team Working Norms: Team working norms (also known as working agreements) are the “norms” that a team agrees upon. These might include items like “work from home on Fridays” or “Core office hours are 10-4”

Definition of Ready: The definition of ready is a list of requirements, decided by the team, that product backlog items must fulfill before the team agrees to work on them.

Definition of Done: The definition of done is a list of requirements, decided by the product owner, that product backlog items must fulfill before the product owner accepts the item as done.

@tirrellpayton

There was an issue loading your timed LeadBox™. Please check plugin settings.

Leave a Reply