Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace: • how_do_we_assign_business_value_to_pi_objectives • why_should_we_start_without_doing_a_complete_analysis • how_can_the_development_manager_be_effective • how_should_we_initially_track_multiple_teams_progress • what_can_we_do_to_improve_our_point_based_estimates
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:27] – [Notes] 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.
  
-====== Notes ======+====== Sample Output ======
  
 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&400|}}+{{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+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.
  
 Its also shows velocity trend over time: Its also shows velocity trend over time:
  
-{{:velocity_trend_over_time.png?direct&400|}}+{{:velocity_trend_over_time.png?direct&600|}}
  
 In addition the spreadsheet shows:  In addition the spreadsheet shows:
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&200|}}+{{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.1474824432.txt.gz · Last modified: 2020/06/02 14:30 (external edit)