peakshift/playbook

Utilise Story Maps to define User / System Flows

Opened this issue · 0 comments

johnsBeharry commented

Steps

  1. Background / Objective
  2. Steps (Epics)
  3. User Stories
  4. Segment iterations by Sprint / Release Versions

This process is useful to fill a product backlog for development teams and can also be utilised within a Design Sprint.

TIPS

  1. When using Jira to record story maps, each flow should have it's own "Board"