Locked lesson.

Upgrade

About this lesson

Sprint Controls are the project management tools that are used by the Scrum Master and Scrum Team to assess performance.

Exercise files

Download this lesson’s related exercise files.

Sprint Controls.docx
101.6 KB Sprint Controls - Solution.docx
99.6 KB

Quick reference

Sprint Controls

Sprint Controls are the project management tools that are used by the Scrum Master and Scrum Team to assess performance.

When to Use Sprint Controls

The two primary controls during a Sprint are the Scrum Board and the Burn Down Chart. These are baselined during the Sprint planning session and are updated daily following the Scrum Team meeting. The Velocity chart is created over a period of several Sprints and is used by the Scrum Master and Product Owner when doing Release planning to size Sprints.

Instructions

The Agile/Scrum process does not rely on traditional project management tools and techniques. It is not a top-down planned and executed project. The project control tools are therefore quite different.

  • The primary tracking tool is the Scrum Board. 
    • This tool uses the Kanban philosophy. Kanban is a visual scheduling approach that directs an activity to be started based upon a resource becoming available to do the work. Activities are not started and then left on hold, rather they are started and worked through to completion; then the next is started.
    • The Scrum Board tracks the current status of all the Stories. They are either in the Sprint backlog waiting to be started, in the Work-In-Process (WIP) column while Scrum Team members are working on them, or in the Done column. 
    • The final column is the Roadblock column. This is the list of currently identified Roadblocks. The Scrum Master is responsible for finding a workaround for each Roadblock. 
    • Another column that is often used is the Not Selected column. This contains Stories that were not included in the Sprint Backlog.
    • The Scrum Board is initialized during the Sprint Planning meeting when all of the Stories are placed in the Sprint Backlog column. Many times the Stories are further subdivided into Tasks to complete the Story.  
    • The Scrum Board is maintained by moving the stories from column to column as the work is started and completed. This is usually updated at each Scrum Team meeting, but some Scrum Masters update the Board more frequently.
    • The primary topic of Scrum Team meetings is the status of the Stories so this meeting is usually done in front of the Scrum Board.
  • The Burn Down Chart is a visual indication of the progress made on the Sprint as compared to the goal.
    • The Burn Down Chart shows the amount of estimated effort needed to complete the Sprint Backlog.
    • The Burn Down Chart is initialized following the Sprint Planning meeting.  At that time all of the estimated effort for all of the Stories and Tasks in the Sprint Backlog are added and the value is the initial value of the vertical axis on the Burn Down Chart. The number of time increments for the Sprint – normally days – is then counted along the horizontal axis. A straight line is drawn from the total effort at Sprint time zero, to the total Sprint time and remaining effort of zero. This is the reference line on the Burn Down Chart.
    • At each Scrum Team meeting, the Scrum Team members provide an estimate of the amount of effort needed to complete the open Stories. Following the meeting, the Scrum Master will add these estimates along with the estimate for any Stories that are still in the Sprint Backlog column. The total is then plotted and the team can see how much effort is still required as compared to the original planned estimate.
  • Velocity is a measure that is created over a series of several Sprints and is used to better estimate the size of the Sprint Backlog.
    • After each Sprint, the original estimate of time for each of the completed Stories from that Sprint are summed together to create a score of how much estimated work was done. 
    • This score is then tracked over several Sprints to determine a typical or average amount of work. 
    • This score is also sometimes used to improve the estimating done by Scrum Team members.
    • There is often a high degree of volatility in these numbers until the Scrum Team becomes experienced then they stabilize, often with a slight upward trend.

 

Hints and Tips

  • These charts are easy to create and maintain. If they are hard, you are doing something wrong.
  • Senior managers and traditional project managers will not understand these tools. They may insist on a Gantt chart or RACI matrix. Don’t fall into the trap of trying to create them. Instead have the Scrum Master meet with them and explain the process.
Login to download
  • 00:02 Hi this is Ray Sheen.
  • 00:04 Some people apply that agile scrum projects are out of control,
  • 00:08 because they don't use traditional project management tools.
  • 00:11 It's not out of control.
  • 00:13 Let's look at the tools and techniques that are used for planning and
  • 00:16 tracking Agile Scrum.
  • 00:18 We'll start with the Scrum board, this is the primary tool used for
  • 00:22 controlling and tracking the work of the sprint.
  • 00:25 Let's look at each of the columns for a minute.
  • 00:28 I'll start with the 2nd column called the sprint backlog.
  • 00:32 At the beginning of a sprint all the stories and
  • 00:35 their associated tasks are in this column.
  • 00:38 When the sprint starts each scrum team member takes the story or task that they
  • 00:42 will work on first, and moves that story or task to the work in process column.
  • 00:47 That story will stay there until the work is completed and
  • 00:50 the card then moves on to the done column.
  • 00:53 There's also a column for roadblocks,
  • 00:55 which are listed in the far right column, and worked on by the scrum master.
  • 01:00 Most organizations also use the far left column
  • 01:03 to hold story cards that were not selected for this particular sprint.
  • 01:08 As you can see, this is a very visual method of monitoring, and
  • 01:11 tracking progress in the project.
  • 01:13 The chart is initialized in the sprint planning meeting
  • 01:16 with everything being placed at that time in the sprint backlog column.
  • 01:20 The stats of each story is then clearly indicated throughout the sprint.
  • 01:25 As the work progresses, the story cards and tasks are moving from left to right.
  • 01:30 Normally, I recommend that the Scrum team works using a Kanban approach.
  • 01:34 That means,
  • 01:35 through visual scheduling, the cares only move to WIP once a resource is freed up.
  • 01:40 So the key here is that we don't start all the stories and tasks and
  • 01:44 move everything to WIP.
  • 01:46 Instead, only the stories being actively worked are in the WIP.
  • 01:50 The scrum team member finishes a task or story and moves it to done.
  • 01:54 Then they can start the next one.
  • 01:57 My rule of thumb is that no scrum team member can have more than two cards
  • 02:01 in the rip column at any one time.
  • 02:04 As I mentioned, this is the primary tool for tracking sprint progress.
  • 02:08 That's why most scrum team meetings are held in front of the scrum board.
  • 02:11 And the stories in tasks are moved while the member gives a quick status update
  • 02:16 in the meeting.
  • 02:18 The next tool is the burn-down chart.
  • 02:20 This tool tracks the remaining work left to complete
  • 02:23 all of the stories in tasks in the original sprint backlog.
  • 02:27 This chart is also initialized during the sprint planning meeting.
  • 02:31 Once all the store cards and
  • 02:32 their tasks have been estimated by the scrum team members, all of the estimates
  • 02:36 are added up to get the total estimated amount of work in the sprint.
  • 02:41 This is the initial value and is plotted on the vertical axis at the time zero.
  • 02:46 The horizontal axis is then divided into the numbers of scrum intervals
  • 02:50 in the Sprint.
  • 02:51 Usually that means the number of days until the Sprint ends.
  • 02:55 If all the estimates were perfect, on the last day the remaining work
  • 02:59 would reach zero so that is the value for the end of the last day.
  • 03:04 A straight line is then drawn connecting these two points.
  • 03:07 If the estimates are perfect, and
  • 03:09 work is done exactly according to plan, that line represents the estimated amount
  • 03:13 of work remaining in the sprint on each day of the sprint.
  • 03:18 During each scrum meeting,
  • 03:19 the scrum master asks each scrum team member to estimate the amount of work
  • 03:23 needed to complete their tasks that are in the whip column.
  • 03:27 After the meeting,
  • 03:27 the scrum master adds these values with the estimates of all the stories and
  • 03:31 tasks still in the sprint backlog column, and this is the estimated amount of work
  • 03:36 needed to complete all of the tasks from the original sprint backlog.
  • 03:40 This chart is helpful for the product owner and scrum master as they are doing
  • 03:44 release planning and early set up activities for future sprints.
  • 03:49 The third measure is velocity.
  • 03:52 This is not a measure within a sprint,
  • 03:54 rather it is a measure across many sprints.
  • 03:58 Velocity is used to estimate how much work can be accomplished in a sprint
  • 04:01 based upon the recent sprint history.
  • 04:04 This helps the product owner and scrum master manage expectations and
  • 04:08 size the scrum team.
  • 04:10 Velocity is determined by adding up the original estimated effort
  • 04:13 of all the stories conducted in a sprint.
  • 04:17 Obviously, this can't be done until each sprint completes.
  • 04:20 This value is in for a series of sprints to determine the average value and trends.
  • 04:26 Velocity is a local measure.
  • 04:28 By that I mean that it is heavily affected by who is on the scrum team,
  • 04:33 how long the sprint lasts, and the type of work done in the Sprint.
  • 04:37 There's often a great deal of volatility in these values
  • 04:41 until an organization becomes expert in Agile/Scrum.
  • 04:44 Even then different teams may have very different velocity values depending on
  • 04:48 the experience and size of the team.
  • 04:50 The Scrum board is the key project management control for
  • 04:55 the Agile/Scrum team and for managing sprints.
  • 04:59 The burn down chart and velocity measure can be of great help
  • 05:03 to both product owners and Scrum masters when planning future sprints

Lesson notes are only available for subscribers.

PMI, PMP, CAPM and PMBOK are registered marks of the Project Management Institute, Inc.

Gift this course