Burn D own charts for Project Management

Burn Down charts for Project Management

Team 4Fangyi ShiMiroslav JaneskiMohsen MehrafrouzSuleyman Yildirim

/ name of department 22-04-2023

Assignment Definition

• Prepare a presentation of 10-15 minutes on the use of Burn Down charts for Project Management and provide a practical example.

PAGE 2

/ name of department 22-04-2023

Content

• Overview• Backlogs• Chart Types• Benefits• Example

PAGE 3

/ name of department 22-04-2023

Overview

• Project tracking used in  agile software development methodologies (e.g.: SCRUM)

• Used for management documentation • Displays remaining effort for a given period of time• Work remaining is the Y axis and time is the X axis.• The work remaining should jig up and down and

eventually trend downward

PAGE 4

/ name of department 22-04-2023

Overview

PAGE 5

/ name of department 22-04-2023

Backlogs

PAGE 6

22-04-2023

Backlogs

• Product backlog• Ordered list of requirements • List of things needed to be done• Team velocity = work completed/days to complete

• Release backlog• Prioritized requirements for an upcoming release

• Sprint backlog• Basic unit of development in Scrum• Last between one week and one month• During each sprint, the team creates finished portions

of a product and shows it to the customer

/ name of department PAGE 7

/ name of department 22-04-2023

Chart types

• Product Burn Down Chart • In Scrum, the product burn down chart is a "big

picture" view of a project's progress. It shows how much work was left to do at the beginning of each sprint. The scope of this chart spans releases; however, a release burn down chart is limited to a single release.

• http://www.sw-engineering-candies.com/blog-1/howtouseproduct-burndown-chartsandsprint-burndown-chartsnotonlyinscrumprojects

PAGE 8

/ name of department 22-04-2023

Product Burn Down Chart

Chart Corresponding Data

PAGE 9

22-04-2023

Chart types

• Release Burn Down Chart • The release burn down chart is a "big picture" view of a

release's progress. It shows how much work was left to do at the beginning of each sprint comprising a single release. The scope of this chart is a single release; however, a product burn down chart spans all releases

• http://www.mountaingoatsoftware.com/scrum/release-burndown/

/ name of department PAGE 10

22-04-2023

Release Burn Down Chart

/ name of department PAGE 11

/ name of department 22-04-2023

Sprint Burn Down Chart

• A Sprint-Burndown-Chart shows all remaining work of the so called the sprint backlog. This sprint backlog contains all work for the current sprint as committed by the team. Usually it is displayed as remaining work in ideal hours for each work day. The Sprint-Burndown-Chart is updated on a daily basis by the team - often before the stand-up meeting of the next work day

• http://msdn.microsoft.com/en-us/library/ff731588.aspx

PAGE 12

/ name of department 22-04-2023

Sprint Burn Down Chart

PAGE 13

/ name of department 22-04-2023

Benefits

• Track the development process• Assess the productivity of team• Estimation of number of hours to be worked

PAGE 14

/ name of department 22-04-2023

Real-life example

• http://msdn.microsoft.com/en-us/vs11trainingcourse_agileprojmanagement_topic2.aspx

• http://joel.inpointform.net/software-development/burn-down-charts-tutorial-simple-agile-project-tracking/

• http://growingventuresolutions.com/blog/example-sprint-burn-down-chart-excel-google-spreadsheet-openoffice-org.html

• http://epf.eclipse.org/wikis/scrum/Scrum/guidances/templates/burndown_chart_D182CF23.html

• http://lookforwardconsulting.com/2010/10/30/using-a-sprint-burndown-chart/

PAGE 15