Overview

The purpose of the Agile Planning Sprint is to dedicate some time to solidifying the proposed solution backlog and to translate that vision into actionable work items and “Definition of Done” or acceptance Criteria, the goals of which include:

Understanding stakeholders’ business needs to determine the solution purpose
Developing a roadmap that includes a vision of the desired outcome, a solution concept that describes the solution, and a release strategy for delivering the solution to the stakeholders
Defining application and technology architecture
Creating the initial solution backlog and identifying, defining, prioritizing, and estimating epics and user stories
Allocating stories to releases (though not locked)
Confirming roadmap and solution backlog contents with stakeholders
Ensuring skillset and capacity exists within teams

Inputs to Planning Sprint

Solution Path Filter
Stakeholders List
Vision 2030 Mapping

High-Level Business Scope & Objectives
High Level Technical Requirements
Project Charter

Outputs from Planning Sprint

Target Users (Prioritized)
Solution Vision Statement
Solution Themes/Goals
Solution/Product Backlog (Prioritized)
Vision Board
User Stories (Prioritized & Sized)
Release Plan

Sprint Plan
Architecture & Technology Approach
Testing Approach
Traceability Approach
Security Tiering
User Personas/User Journeys