Scrum Documentation

Many people feel that scrum means that they don’t have to document the project anymore. That is simply not the case. The reality is that the type of documentation required for scrum is significantly different than the type required for a waterfall-driven project.

Below is an overview of the types of documentation that a scrum project requires.

Product Backlog

    • Describes “what” will be built
    • Managed by product owner
    • Translated requirements into user stories
      • User stories = one or two sentences in language of customer
    • Contains rough estimates (in days)
    • Contains priorities, reprioritized after each sprint

    Sprint Backlog

      • Produced from Spring Planning Meeting
      • Tasks can be of the following types:
        • Design tasks
        • Coding tasks
        • Testing tasks
        • Documentation tasks
      • Tasks are not assigned, but signed up for
        • Each person is working on one task at a time
        • Estimate of the task adjusted daily
      • Tasks cannot be added, but can be removed if out of time
        • Velocity will be established over iterations
          • # of tasks that the team can complete in one sprint

      Sprint Burn-down Chart

        • Shows the number of hours of work left to satisfy all the requirements of the sprint

        5 thoughts on “Scrum Documentation

        1. I think this is a good article for beginners to know about the basics of scrum !

        2. I learned about the need for Definition of Done, sprint planning, burn down list and so on but this is the first article I’ve read that indicates that these do have to be documented. Thank you!

        Leave a Reply

        Your email address will not be published. Required fields are marked *