Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace: • tim_ottinger_-_agile_productivity • middle_management_struggling_with_the_change_anti-pattern • simulating_wip_effects_with_balls_and_a_banana • i_am_going_to_wait_for_the_training_anti-pattern • how_should_we_initially_track_release_progress • what_is_the_purpose_of_estimation • what_are_the_steps_to_establish_a_development_manager • how_do_we_use_story_point_estimates_to_forecast • how_should_we_initially_track_sprint_progress
how_should_we_initially_track_release_progress

Differences

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

Link to this comparison view

Next revision		Previous revision
how_should_we_initially_track_release_progress [2016/05/12 19:30] – created hpsamioshow_should_we_initially_track_release_progress [2020/06/04 09:25] (current) – Removed LINKBACK hans
Line 1: Line 1:
 ====== How Should We Initially Track Release Progress? ====== ====== How Should We Initially Track Release Progress? ======
- 
-====== Premise ====== 
  
 In general the best approach to tracking Release progress when you get started is through a manual big visible chart showing stories moving from a backlog through "To Do", "In Progress", and "Done" steps, and a chart showing the Release Burn-up, also manual. The reason we do this is so that teams can learn and understand how a Release is supposed to work without having to also learn the nuances (and potential changes in behavior) required by a tool. In general the best approach to tracking Release progress when you get started is through a manual big visible chart showing stories moving from a backlog through "To Do", "In Progress", and "Done" steps, and a chart showing the Release Burn-up, also manual. The reason we do this is so that teams can learn and understand how a Release is supposed to work without having to also learn the nuances (and potential changes in behavior) required by a tool.
Line 35: Line 33:
 Basic instructions are included in the spreadsheet on the "Instructions" tab.  Basic instructions are included in the spreadsheet on the "Instructions" tab. 
 {{:simple_product_backlog_and_burn-up.xlsx|}} {{:simple_product_backlog_and_burn-up.xlsx|}}
- 
  
 {{tag>Consultant Tools ReleaseBurnup FirstSprint FAQ}} {{tag>Consultant Tools ReleaseBurnup FirstSprint FAQ}}
  
  
-~~LINKBACK~~ 
-~~DISCUSSION~~ 
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/how_should_we_initially_track_release_progress.1463106637.txt.gz · Last modified: 2020/06/02 14:31 (external edit)