Ad
related to: scrum burndown chart example
Search results
Results From The WOW.Com Content Network
A sample burndown chart for a completed iteration. It will show the remaining effort and tasks for each of the 21 work days of the 1-month iteration. A burndown chart or burn-down chart is a graphical representation of work left to do versus time. [1] The outstanding work (or backlog) is often on the vertical axis, with time along the horizontal.
English: A sample burndown chart as used in Agile software development methodologies, for example Scrum. This is a scalable version of File:SampleBurndownChart.png This is a scalable version of File:SampleBurndownChart.png
Often used in scrum, a burndown chart is a publicly displayed chart showing remaining work. [36] It provides quick visualizations for reference. The horizontal axis of the burndown chart shows the days remaining, while the vertical axis shows the amount of work remaining each day. During sprint planning, the ideal burndown chart is plotted.
A burn down chart tracks work remaining over time while burn up charts like the CFD track the growth (or shrinkage) of work in certain states over time. In agile software development, when teams use kanban methodology, the cumulative flow diagram shows the number of active items in each column on a kanban board.
I like having this as a separate page - it would be nice to see an image of an example burn down chart however. Tobyberesford 12:05, 14 April 2009 (UTC) It's not about "burn down charts" having applicability outside scrum; it's about whether "burn down charts" constitutes an independent, encyclopedic subject.
move to sidebar hide. From Wikipedia, the free encyclopedia
The daily commitments allow participants to know about potential challenges as well as to coordinate efforts to resolve difficult or time-consuming issues. The stand-up has particular value in agile software development processes, [3] [4] such as scrum or Kanban, but can be utilized in context of any software-development methodology.
The INVEST mnemonic for Agile software development projects was created by Bill Wake [1] as a reminder of the characteristics of a good quality Product Backlog Item (commonly written in user story format, but not required to be) or PBI for short.