Understanding the scrum burndown chart. dusan kocurek, scrumdesk, www.scrumdesk.com being a startup is a great period in the company’s lifetime. developing a product in which you believe with a small and highly motivated team is remarkable experience that you hope will stay forever.. The y-axis of the release burndown chart is hours or story points, whereas the x-axis of the chart is time (spanning over the duration of a release). upon analysis of a release burndown chart, you can answer these questions:. The product burndown chart is used to manage the features and functional requirements of a product, which are described as user points. these are represented in a bar chart (unlike the usual line burndown chart), where the y axis is the number of points left for completing the product, and the x axis represents the number of sprints / stories in the products’ lifecycle..
Progress on a scrum project can be tracked by means of a release burndown chart. the scrummaster should update the release burndown chart at the end of each sprint. the horizontal axis of the sprint burndown chart shows the sprints; the vertical axis shows the amount of work remaining at the start of each sprint.. A release burndown chart helps the stakeholders to get a very good view of the release progress by determining the amount of the remaining work (x-axis = no of sprints, y-axis – the remaining effort).. A burndown chart graphically represents the total effort required to complete a sprint in term of hours, if you read along y-axis. you can also see the number of days required for the estimated effort by reading along x-axis..
No comments:
Post a Comment