Skip to Content

Changes for page Agile and Data

Last modified by chrisby on 2024/01/13 17:13
From version 3.2
edited by chrisby
on 2023/11/18 14:11
Change comment: There is no comment for this version
To version 3.4
edited by chrisby
on 2023/11/26 18:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,9 +7,9 @@
7 7  ![[velocity-time-chart_white.svg|velocity-time-chart_white.svg]]
8 8  
9 9  * x-axis: Time in iterations or dates (the last day of each iteration)
10 -* y-axis: Velocity = points of completed stories within an iteration
10 +* y-axis: Velocity = points of completed stories within one iteration
11 11  * The first data point is generated after the first story implementation iteration.
12 -* After a few iterations, the average velocity should be about constant for the rest of the project.
12 +* After a few iterations, the average velocity should be roughly constant for the rest of the project.
13 13  
14 14  **2. Burndown Chart**
15 15  
... ... @@ -41,6 +41,6 @@
41 41  
42 42  * **Schedule Adaption**: It's sometimes possible to postpone the deadline, although this is often not an acceptable option for management.
43 43  * **Personnel Increase**: Will result in a short-term drop in productivity, as the new team members require the attention of the original team members (explanations, answering questions, joint familiarization with the project, etc.), which distracts them from their actual work. After this period, productivity will rise above the original productivity as desired.
44 -* **Scope Adaption**: Stakeholders prioritize features with the highest business value and remove low-value features from the project scope.
44 +* **Scope Adaption**: Stakeholders prioritize features with the highest return of investment (RoI) and remove features with lower RoI from the project scope.
45 45  
46 46  Decreasing code quality by omitting testing or refactoring is not an option, as it actually slows development and adds to technical debt.