Differences

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

--- how_do_we_build_and_maintain_context_when_all_we_have_is_a_backlog_list [2018/12/20 07:53] – [Need to Know More] Added video link hpsamios
+++ how_do_we_build_and_maintain_context_when_all_we_have_is_a_backlog_list [2018/12/20 07:57] – Created new link for picture hpsamios
@@ Line 13: / Line 13: @@
 What you end up with is a matrix with activities / stories on the horizontal axis (user does this, then does that, then does that) and priority in the vertical axis (this is the most important function to provide, this is the second, etc. Swim lanes identify potential delivery timescales. In other words, a visual workflow and plan combined in one. Here is an example for an online shopping type experience:
-[[http://storiesonboard.com/img/OnlineShopRelease1.png|Online Shopping Example]]
+[[https://3.bp.blogspot.com/-wIoM9yRwGDI/V753rscPUVI/AAAAAAAAApk/qc8xKgB0-VMKrShG0xqXPAUsU6w7c_Y_ACLcB/s1600/Story%2BMapping%2BExample.png|Email Example]]
-In this picture you can see yellow user activities, the with stories required to support that activity in yellow underneath (in white). You can see they have said “this is what will happen in Release 1” by creating swim lanes. These time horizons can be whatever makes sense in your situation. Perhaps a sprint by sprint view, perhaps a "Program Increment" view if working in a SAFe environment.
+In this picture you can see blue user activities, the with stories required to support that activity in yellow underneath. You can see they have said “this is what will happen in the first increment” by creating swim lanes. These time horizons can be whatever makes sense in your situation. Perhaps a sprint by sprint view, perhaps a "Program Increment" view if working in a SAFe environment.
 A couple of notes: