Skip to content

Utilise Story Maps to define User / System Flows #8

@johnsBeharry

Description

@johnsBeharry

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"

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationUsed to supplement someones' understandingplanningProject planning tools

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions