dleeapho / sandbox Goto Github PK

• Requirements drawn and checked with customer
• Implementation design (enough to start Dev/Test)
• Work breakdown; either bullet points within the issue as tasks or new, finer-grained user-stories created. If the later then those new user-stories are in the Design - Done lane.

• There isn't a Document Done swimlane because the last swimlane never has one, once it is 'done' it moves to closed.
• To capture metrics we might need to have a "Delivered in Sprint" swimlane so we can capture what was delivered in a sprint, get time-to-delivery metrics etc.

• The product has been rolled out to staging (if applicable), then to production
• Rollout issues resolved (small 'adjustment' bugs resolved)
• We could include the Document swimlane here as a 'Done Defintion'

• This is where all issues sit that are not prioritized during the planning phase (ie sprint start).

• User-stories that have deemed as the ones we prioritize for the current sprint. No need to balance capacity but any n-1 sprint user-stories have to be questioned in the next planning phase (ie sprint).

To capture metrics we might need to have a "Delivered in Sprint" swimlane so we can capture what was delivered in a sprint, get time-to-delivery metrics etc.

• Implemented
• Self-tested
• PR merged - I'm wondering about adding this as a swimlane since for some types of work the "In PR" process is quite long.