Topic #2 Burn-down. User Story: As a Scrum Master or Member of an Agile team I want to understand velocity and burn down So that I can use them to maximize.

Slides:



Advertisements
Similar presentations
Iteration Planning.
Advertisements

Team Development with Microsoft Scrum 1.0 Doncho Angelov Developer Evangelist Microsoft Bulgaria.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Agenda −Scrum with TFS 2010 using MSF for Agile 5.0 −Planning the Project −How do you plan the project? −Project planning in TFS 2010 −Planning a Sprint.
IAgile – iNetFrame’s framework for agile development Features Get to see a working product early Development shadows evolving requirements Pair programming.
ECE44x SCRUM Overview slides adapted from Marty Stepp
Agile Project Management with Scrum
SCRUM © University of LiverpoolCOMP 319slide 1. SCRUM history In 1986, Hirotaka Takeuchi and Ikujiro Nonaka More an observation of good practise in manufacturing.
An Introduction to Agile SCRUM Methodology
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Scrum CS These slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
© Timothy Korson Page 1 Scrum by Dr. Korson For CPTR 209 Software Engineering Version
Scrum 1.
Agile-SCRUM. Introduction to SCRUM Sanil Xavier What is Scrum?
Managing a Project Using an Agile Approach and the PMBOK® Guide
Topic #3 Burn-down Patterns. User Story: As a Scrum Master or Member of an Agile team I want to understand burn-down patterns So that I can identify,
, TargetProcesswww.targetprocess.com1 TargetProcess:Suite Agile Project Management System Powers iterative development Focuses on Project Planning,
Agile Training Camp e-Learning Module Introduction -
1 Waterfall/Scrum You might want to take notes, because specific aspects of the processes will be on the exam. Combining – A scrum with water…
How Agile Are You? Larry Apke Agile Expert
© 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Deeper Dive Into: User Stories.
What is Scrum Process? Where is it used? How is it better?
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Project Workflow. How do you do it? -Discussion-
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
SCRU M Scrum Overview - Commonly Used Terms Ali Qureshi, parorrey.com – 31 st Aug, 2015 PI Media parorrey.com.
Process is continuously improving Have Definition of Done (DoD) DoD achievable within each iteration Team respects DoD The bottom line Delivering working,
THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Scrum Santhosh Srinivasan. Outline What is Scrum What is Scrum Why Scrum Why Scrum Scrum Practices Scrum Practices Why Scrum works Why Scrum works Pros.
Het einde van het beroep van tester - Wat Agile, DevOps en Scrum betekenen voor het testvak -
Agile Training Camp e-Learning Module Introduction -
Agile Metrics It’s Not All That Complicated. © 2011 VersionOne 2 Welcome – About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach.
School Improvement Specialist Meeting April 4, 2012.
SCRUM.
Using Scrum to Improve Teamwork, Communication, Quality and Speed
Topic #1 Velocity. User Story: As a Scrum Master or Member of an Agile team I want to understand velocity and burn down So that I can use them to maximize.
SCRUM © University of LiverpoolCOMP 319slide 1. SCRUM history In 1986, Hirotaka Takeuchi and Ikujiro Nonaka More an observation of good practise in manufacturing.
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Scuola Politecnica Dipartimento DITEN Università degli Studi di Genova An Introduction to Scrum and XP Prof. Riccardo Berta.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum.
Scrum and TargetProcess
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Scrum Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Mike Cohn - Agile Estimating and Planning
By: By: Agile Scrum Master Online Training.
SCRUMS Agile Education.
Creating User Documentation in an Agile World
Chapter 3: The Project Management Process Groups: A Case Study
Burn Down charts for Project Management
Scrum MODULE 3 – Part 3.
Burn Down charts for Project Management
Johanna Rothman Agile Team Measurements Chapter 12
Summarizing Our Models to Date
Johanna Rothman Report Your Project State Chapter 14
Scrum - Plan a Sprint Great Video (but added release /sprint layer)
© University of Liverpool
Sprint Planning April 2018.
Introduction to Agile Blue Ocean Workshops.
Adjective: Able to move quickly and easily. Principles and Values
Scrum in Action.
Agile Development.
Agile product development
Presentation transcript:

Topic #2 Burn-down

User Story: As a Scrum Master or Member of an Agile team I want to understand velocity and burn down So that I can use them to maximize my team’s chances for success.

Q: What is Burn-down? A: An empirical measure of progress Burn-down measures the task completion rate during an iteration Its units are hours – the estimated number of hours that still remain to complete the tasks It is calculated daily and graphed Burn-down = Hours remaining For All Tasks Within an Iteration

Iteration 1 – Burn-down table showing hours remaining for tasks in 2 week iteration The burn-down for Day 1 (the remaining work for the tasks in this iteration) is = 36 hours User Story TasksDay 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Story 1Task Story 1Task Story 1Task Story 2Task The burn-down for Day 5 is = 15 hours

Iteration 1 – Burn-down chart Unlike velocity, burn-down is unaffected by incomplete tasks Because burn-down is based on estimated hours remaining, the numbers may fluctuate up or down.

Now you try it! Using the following table, calculate burn-down for day 1 User Story TasksDay 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Story 1Task Story 1Task Story 1Task Story 2Task The burn-down for day 1 is = 36 hours What is the burn down for day 1? Press the space bar to view the answer.

Now you try it! Using the following table, calculate burn-down for day 6 User Story TasksDay 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Story 1Task Story 1Task Story 1Task Story 2Task The burn-down for day 6 is = 11 hours What is the burn down for day 6? Press the space bar to view the answer.

Now you try it! Using the following table, calculate burn-down for day 10 User Story TasksDay 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Story 1Task Story 1Task Story 1Task Story 2Task The burn-down for day 10 is = 2 hours What is the burn down for day 10? Press the space bar to view the answer.

Ponder: Take 15 minutes to reflect on the following questions and statements What factors can affect a team’s burn-down? Brainstorm some answers, then rank them in order of decreasing effect (causing the most influence on burn-down to the least influence on burn- down). Which of these factors are likely to occur within your team? What can you do to minimize their influence?

Other factors that can influence burn-down are … Changes in a team’s capacity (the amount of time a team has to perform feature work within an iteration) Team members multi-tasking Team members’ time being taken up with non-feature work Changes in team membership Losing experienced team members Obstacles or impediments during the iteration

Interesting and useful facts about burn-down … Burn-down measures actual progress during an iteration, so it gives the team an idea of whether or not they will meet their iteration goals Because tasks are estimated in ideal hours, burn-down is calculated in hours Burn-down and velocity are used together on an Agile project: Velocity is used to determine how many user stories can fit within a typical iteration Burn-down shows completion of the tasks that make up the user stories and is used to determine progress

Digging Deeper: Comparing Burn-down and Velocity Why does burn-down measure hours remaining and not the number of completed tasks? (Whereas velocity only counts completed user stories.) Once you have come up with your own answer, press the space bar to see our answer. Velocity is really for the customer who only sees benefit once a user story is fully complete. Burn-down is for the development team to give them insight into their progress so they can gauge how much effort they must still expend to fully complete their tasks.

Research: Find examples of burn-down charts, then review them for patterns and trends. Employ one or more of the following methods to obtain examples of how others have used burn-down. Ask other Agile project managers or scrum masters if they use burn-down, and if so, ask them to show you their charts for several iterations. Search the company intranet using the terms “burn-down,” “burn down,” or “burndown.” Search the internet using the terms “burn-down,” “burn down,” or “burndown Attend an Agile Support Group meeting and ask the attendees for examples.

Take a Quiz Click on the following link to take a quiz on burn-down. Burn-down Quiz