facebooktwittergoogle_plusredditpinterestlinkedintumblrmailby feather

Objectives:
Know how to write user stories
Know how a product backlog works
Know how to use a sprint backlog
Know how to make and interpret a burndown or burnup charts




  Prior learning test
Test 4 - Key Artifacts

Firstly Scrum is a framework and does not seek to specify all the documentation that a product may require; your company will have other documentation that can be included in the system.  However it has some very important documents (artifacts) which hold the framework together:

  1. User Stories
  2. Product Backlog
  3. Sprint Backlog
  4. Progress charts ( not strictly required by the Scrum Framework, but really useful)

Artifact Overview

 

User Stories

word summary much thanks to http://businessanalysisexperts.com/

Product Backlog & Sprint Backlog

In the overview and other sections we have discussed product backlogs and sprint backlogs.  Typical product backlog  are often computerised even though this reduces transparency.  On smaller products a white board can be used.

product board productbacklogPC

The sprint backlog should always be represented on visible system like a white board.

sprintboard

More detail on Sprint Backlog and Product Backlog to be reviewed for PSM

Burndown and Burnup Charts

 

 

Conclusions

You should now have a firm understanding of:

Objectives:
Know how to write user stories
Know how a product backlog works
Know how to use a sprint backlog
Know how to make and interpret a burndown or burnup charts




  Post learning test
Test 4 - Key Artifacts

If you are planning to take the professional scum master 1 certificate you should get 90% in the following test