Skip to Content

Changes for page Agile and Data

Last modified by chrisby on 2024/01/13 17:13
From version 11.12
edited by chrisby
on 2024/01/13 17:13
Change comment: There is no comment for this version
To version 11.9
edited by chrisby
on 2023/12/19 15:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,7 +16,7 @@
16 16  **![[burndown-chart_white_v2.svg|burndown-chart_white_v2.svg]]**
17 17  
18 18  * x-axis: same as in velocity-time chart
19 -* y-axis: Points Remaining = sum of points from unfinished stories
19 +* y-axis: Points remaining = sum of points from unfinished stories
20 20  * The first point starts at the very beginning of the project and is therefore at x = 0, just above the y-axis. It is the sum of the effort estimates of all stories. The second data point is generated after the first story implementation iteration.
21 21  * The linear approximation function of the data points has a negative slope. The deck of stories is completed over time, so the graph "burns down" over time, hence the name.
22 22  
... ... @@ -33,7 +33,7 @@
33 33  
34 34  ### Declining Velocity
35 35  
36 -Ideally, velocity remains constant and the team makes steady progress. But if it drops, the most likely reason is poor code quality due to lack of refactoring and testing. Don't hide it, don't artificially inflate the velocity (see "[[Golden Story|doc:Software Engineering.Agile.Extreme Programming.Planning Game.Effort Estimation.WebHome]]"), just invest more time in refactoring and testing to improve code quality.
36 +The most likely reason for declining velocity is poor code quality due to lack of refactoring and testing. Don't hide it, don't artificially inflate the velocity (see "[[Golden Story|doc:Software Engineering.Agile.Extreme Programming.Planning Game.Effort Estimation.WebHome]]"), just invest more time in refactoring and testing to improve code quality.
37 37  
38 38  ### How to Handle Delays?
39 39