Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace: • 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 • how_should_we_initially_track_sprint_progress • what_are_the_steps_to_establish_a_development_manager • how_do_we_use_story_point_estimates_to_forecast • how_do_we_work_with_non-functional_requirements_nfrs • how_do_we_split_user_stories
how_should_we_initially_track_sprint_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_sprint_progress [2015/11/23 09:00] – created hpsamioshow_should_we_initially_track_sprint_progress [2020/06/04 08:13] (current) – Removed LINKBACK hans
Line 1: Line 1:
 ====== How Should We Initially Track Sprint Progress? ====== ====== How Should We Initially Track Sprint Progress? ======
- 
-====== Premise ====== 
  
 In general the best approach to tracking Sprint progress when you get started is through a manual big visible chart showing tasks moving through "To Do", "In Progress", and "Done" steps, and a chart showing the Sprint Burn-down, also manual. The reason we do this is so that teams can learn and understand how a Sprint 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 Sprint progress when you get started is through a manual big visible chart showing tasks moving through "To Do", "In Progress", and "Done" steps, and a chart showing the Sprint Burn-down, also manual. The reason we do this is so that teams can learn and understand how a Sprint is supposed to work without having to also learn the nuances (and potential changes in behavior) required by a tool.
Line 19: Line 17:
   * Idea of tracking where interuptions come from for a team is useful when getting started (note - if you do not have this problem, don't bother entering information in the related tab)   * Idea of tracking where interuptions come from for a team is useful when getting started (note - if you do not have this problem, don't bother entering information in the related tab)
  
-To use the spreadsheet+====== Sample Output ======
  
-====== Template ======+===== Burn-down Chart =====
  
 +{{:sample_burn-down.jpg?400|}} 
  
 +===== Disruptive Work Chart =====
 +
 +{{:sample_disruptive_work_chart.jpg?400|}}
 +
 +====== Template ======
 +
 +Basic instructions are included in the spreadsheet on the "Instructions" tab. {{:simple_sprint_backlog_and_burn-down.xlsx|}}
  
 {{tag>Consultant Tools SprintBurndown Interruptions FirstSprint FAQ}} {{tag>Consultant Tools SprintBurndown Interruptions FirstSprint FAQ}}
 +
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/how_should_we_initially_track_sprint_progress.1448298025.txt.gz · Last modified: 2020/06/02 14:27 (external edit)