Differences

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

--- how_should_we_initially_track_release_progress [2016/05/12 19:30] – created hpsamios
+++ how_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? ======
-====== 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.
@@ Line 35: / Line 33: @@
 Basic instructions are included in the spreadsheet on the "Instructions" tab.
 {{:simple_product_backlog_and_burn-up.xlsx|}}
 {{tag>Consultant Tools ReleaseBurnup FirstSprint FAQ}}
-~~LINKBACK~~
-~~DISCUSSION~~