Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace:
how_should_we_initially_track_multiple_teams_progress

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
how_should_we_initially_track_multiple_teams_progress [2016/09/25 10:30] – hpsamioshow_should_we_initially_track_multiple_teams_progress [2020/06/04 07:53] (current) – Killed LINKBACK hans
Line 1: Line 1:
 ====== How Should We Initially Track Multiple Team's Progress? ====== ====== How Should We Initially Track Multiple Team's Progress? ======
  
-Sometimes you quick off a couple of teams at the same time, and want to see how the team's are doing over time. I've found {{:wiki:planned_committed_vs_actual_velocity.xlsx|this spreadsheet}} will help in those situations.+Sometimes you kick off a couple of teams at the same time, and want to see how the team's are doing over time. I've found {{planned_committed_vs_actual_velocity.xlsx|this spreadsheet}} will help in those situations.
  
 ====== Sample Output ====== ====== Sample Output ======
Line 7: Line 7:
 The spreadsheet shows a team by team view with a chart showing committed versus actual velocity over time, including an "acceptable range" band: The spreadsheet shows a team by team view with a chart showing committed versus actual velocity over time, including an "acceptable range" band:
  
-{{:wiki:committed_vs_actual_velocity.png?direct&600|}}+{{committed_vs_actual_velocity.png?direct&600|}}
  
 The idea is that you don't want the team to always hit the commitment (that just leads to "sand-bagging") but rather want to encourage teams to take risks and not feel too bad when it doesn't work out, but also isn't way off. I've used plus / minus 16% as the acceptable range (based on reading) and found that to work well. The idea is that you don't want the team to always hit the commitment (that just leads to "sand-bagging") but rather want to encourage teams to take risks and not feel too bad when it doesn't work out, but also isn't way off. I've used plus / minus 16% as the acceptable range (based on reading) and found that to work well.
Line 21: Line 21:
   * "Velocity Variation" is the comparison between early sprints and later sprints in terms of velocity. The idea is to discuss whether we are getting better. Please note that this is a very bad public benchmark as it can be easily gamed.   * "Velocity Variation" is the comparison between early sprints and later sprints in terms of velocity. The idea is to discuss whether we are getting better. Please note that this is a very bad public benchmark as it can be easily gamed.
  
-{{:wiki:table_of_team_indicators.png?direct&600|}}+{{table_of_team_indicators.png?direct&600|}}
  
 ====== Files ====== ====== Files ======
  
-{{:wiki:planned_committed_vs_actual_velocity.xlsx|Planned (committed) vs Actual Velocity.xlsx}}+{{planned_committed_vs_actual_velocity.xlsx|Planned (committed) vs Actual Velocity.xlsx}}
  
 {{tag>Consultant Tools Velocity Trends FirstSprint FAQ}} {{tag>Consultant Tools Velocity Trends FirstSprint FAQ}}
  
-~~LINKBACK~~ 
-~~DISCUSSION~~ 
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/how_should_we_initially_track_multiple_teams_progress.1474824641.txt.gz · Last modified: 2020/06/02 14:24 (external edit)