Page Comparison

...

• The overview page serves as a dashboard for the map and provides a quick summary of important information. It includes:

  • Map name

  • Purpose

  • Business Owner

  • Unsolved Probelms Problems and Objectives

  • WHOs

  • Backbone activities

...

A frame clearly articulates the necessity for change by outlining the problem, objectives, and anticipated benefits and define the PURPOSE (WHY). It includes the high-level scope of the change (WHAT) and impacted entities (WHO)

• Problems

• Objectives

• Benefits

Map

...

Story Map set up

• Creating a Story Map

• Connecting and Disconnecting from the hierarchy

  • Story Map Hierarchy

  • Tagging the top of the global Hierarchy

...

Creating the WHO map

• Adding a WHO to a Story Map

Creating the Story Backbone

...

.

For more, please see Frame Guide

Map

Map are where you establish your Activity map and WHO map, by:

• Creating a new Map

• Creating the WHO maps

• Creating the first level of Activities (Backbone)

• Breaking Activities into Sub-Activities

  https://storyd.atlassian.net/wiki/spaces/STORYDDOC/pages/17498113/Adding+a+Activity+to+a+Story+Map#Creating-a-Skeleton-Activity

  (Skeleton)

For more, please see Map Guide

Plan & Explore

Plan

...

• Creating Releases

• https://storyd.atlassian.net/wiki/spaces/STORYDDOC/pages/18186264/Adding+and+removing+Activities+from+a+Release#Adding-Activities

• Adding Explore information

...

Plan Epics

• Creating Epics

• Exploring an Epic

• Jira integration - Exporting Epic data using field mapping

• Jira integration - Creating integration links without exporting data

Roadmap

• Roadmap Build and view mode

• Creating releases from the roadmap

• Adding an Epic from the roadmap

• Roadmap Moving Epics

History

...

& Explore, guides the planning of releases that encompasses an approach that begins with detailing the activities involved in the release. It then delves into exploring and analyzing related information about each activity, providing insights and context crucial for strategic planning. Building on this analysis, the capability proceeds to create epics, which are broad, high-level requirements that encapsulate the purpose, objectives and expectations derived from the analyzed information. These epics serve as foundational elements that guide the development teams in understanding the scope and scale of the work ahead, ensuring that every release is aligned with the initiative’s objectives and stakeholder needs.

For more, please see Plan & Explore Guide

Roadmap

The Roadmap capability provides a comprehensive view of upcoming changes across multiple releases, offering the flexibility to view the plan from either a release or an activity perspective. Additionally, it enables users to construct new releases directly within the roadmap interface.

For more, please see Roadmap Guide