Burn Down charts for Project Management Team 4

Burn Down charts for Project Management Team 4 Fangyi Shi Miroslav Janeski Mohsen Mehrafrouz Suleyman Yildirim

Assignment Definition • Prepare a presentation of 10 -15 minutes on the use of Burn Down charts for Project Management and provide a practical example. / name of department 31 -10 -2020 PAGE 1

Content • • • Overview Backlogs Chart Types Benefits Example / name of department 31 -10 -2020 PAGE 2

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 / name of department 31 -10 -2020 PAGE 3

Overview / name of department 31 -10 -2020 PAGE 4

Backlogs / name of department 31 -10 -2020 PAGE 5

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 31 -10 -2020 PAGE 6

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-chartsandsprintburndown-chartsnotonlyinscrumprojects / name of department 31 -10 -2020 PAGE 7

Product Burn Down Chart / name of department Corresponding Data 31 -10 -2020 PAGE 8

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/releaseburndown/ / name of department 31 -10 -2020 PAGE 9

Release Burn Down Chart / name of department 31 -10 -2020 PAGE 10

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/enus/library/ff 731588. aspx / name of department 31 -10 -2020 PAGE 11

Sprint Burn Down Chart / name of department 31 -10 -2020 PAGE 12

Benefits • Track the development process • Assess the productivity of team • Estimation of number of hours to be worked / name of department 31 -10 -2020 PAGE 13

Real-life example • http: //msdn. microsoft. com/enus/vs 11 trainingcourse_agileprojmanagement_topic 2. aspx • http: //joel. inpointform. net/software-development/burn-down-chartstutorial-simple-agile-project-tracking/ • http: //growingventuresolutions. com/blog/example-sprint-burn-downchart-excel-google-spreadsheet-openoffice-org. html • http: //epf. eclipse. org/wikis/scrum/Scrum/guidances/templates/burndo wn_chart_D 182 CF 23. html • http: //lookforwardconsulting. com/2010/10/30/using-a-sprint-burndownchart/ / name of department 31 -10 -2020 PAGE 14