The presentation covers the areas that needs to be looked into for Agile transitions in the team and the role of product management in the deliverable and releases

1. Product Management perspective of Agile
Planning Process
by Dr.Pooja Radhakrishna
Copyright@2018 Dr.Pooja

2. Agenda
 Overview
 Roles Involved
 Scrum Team Structure
 PI Readiness
 PI Phases & Outcomes expected
-Pre PI planning
-PI planning
-Post PI planning
Copyright@2018 Dr.Pooja

3. Overview
Copyright@2018 Dr.Pooja
P
R
E
P
I
Step 1 Step 2 Step 3 Step 4 Step 5
Executive
Vision
Director
Business Goals
for the Quarter
Director & PM
Top PI Objectives
PO group
PI Backlog (Features
+ Defect Bucket)
PM->PO
User Stories in the
required tool
(collab with Ux +
Services
KS sessions
PO(s)<->Engineering DOR
PM, PO, Architects, Team
Leads, SM, SMEs,
RM(*Tool readiness –
RM/Program Manager)
Sign-offs from
Stakeholders Backlog
Refined & Ready
3 weeks
PI
P
L
A
N
N
I
N
G
2 - 3 Days
Day 1 Day 2 Day 3
P
O
S
T
P
I
6 Sprints

4. Roles Involved
Copyright@2018 Dr.Pooja
Product
Management
Engineering
Release
Management Or
Program
Management
Build Management
/Interop teams
UX
team
Scrum
Master

5. Scrum Teams
Copyright@2018 Dr.Pooja
Names
for each
scrum
team
Management
and Support
teams shared
4 Developers
2 Testing
1 PO
1 SM*

6. PI : Program Increment
 PI planning forms the “core” of SAFe practices
 Earlier it was termed as PSI (Potentially Shippable
Increment) planning
 The success depends on the preparation, readiness and
its execution
 Organization Readiness
 Facility Readiness
 Content Readiness
Copyright@2018 Dr.Pooja

7. PI Readiness
 Organization Readiness:
Copyright@2018 Dr.Pooja
Planning Scope &
Goals
Business Alignment
Agile teams
Identification

8. PI Readiness
 Facility Readiness:
Copyright@2018 Dr.Pooja
Space
Boards & Stationaries
Tech support &
Communication Channels

9. PI Readiness
 Content Readiness:
Copyright@2018 Dr.Pooja
Executive or Leadership
Briefing for the Quarter &
PI
1
Product Vision
2
Architect / Engineering
Vision
3
Release Management /
Program management
4
Participation

10. Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Sprint 1
2 weeks
I
P
S
P
R
I
N
T
PI - 1 PI - 2
PI 1 planning PI 2 planning
PI Planning Cycle
Copyright@2018 Dr.Pooja

11. PI Planning Phases
 Pre- PI
 PI
 Post-PI
Copyright@2018 Dr.Pooja

12.  Executive / Leadership  Product Management
Pre-PI Planning
 Architect / Engineering
Copyright@2018 Dr.Pooja
- Business
Context
- Goals
- Vision
- Customer
feedbacks
PI / Quarter
Decisions
Q1
Q2
Q3
Q4
PM
Top 5 - 10
Priorities
PO group
Discussions
Backlog
Creation &
add in tool
Dependencies
or alignments
with Other teams
PO KS with
Engineering
teams
Requirement
Understanding
&
Inputs/feedback
Discuss
Technology
NFRsEnablers
PI backlog refined for Review & Sign offs
DOR for User stories in the tool & scrum teams ready for
allocations
Release
Strategies

13. PI Backlog Structure
Copyright@2018 Dr.Pooja
Theme / Epic
Initiatives /
Capabilities
Features
User Stories
Tasks

14. PI Planning
Copyright@2018 Dr.Pooja
Day 1
• Kick Off Meeting – Leadership Briefing & Release Manager presentation
• Planning Starts – Scrum Master drives & PO guides (All Scrum teams participate)
• Activities plan per Sprint - Estimations, Velocity, Load, Confidence vote, Mark Cross
team dependencies, Digitization (story wise in the tool) & ROAM factors
• Day 1 Report Out by Scrum Master to the Stakeholders (Sprint wise in the tool / Team)
Day2
• Scrum Teams Continue Planning – Incorporation of Day 1 report out Inputs
• Modifications in the tool as per the feedback
• Review of the plan for all the sprints
• Day 2 Report Out by Scrum Master to the Stakeholders (Sprint wise in the tool / Team)
Day 3*
• Replan & Shuffle the stories only if any changes identified
• Final Report out of the Plan and reach an Agreement of all the participants
Outcomes of PI plan
Clarity on each Scrum Team PI
Objectives & commitments
Aligning the product vision
with market needs and the
development processes
Early identification of
dependencies/ requirements
and initiating collaboration
with cross functional teams
Tracking deliverables into the
market and taking early
feedbacks from our customers

15. Feature #
User story #
Short Description of the
story title
Estimated Story
Points
PI Planning Board
Load, Velocity,
Confidence
ROAM
Iteration or
Sprint
Copyright@2018 Dr.Pooja

16. Post – PI planning
Copyright@2018 Dr.Pooja
PI Retro
DOD, US Acceptance,
Sprint Review (demo)
Spill over
Sprint retro
Sprint planning Release Planned – Milestones check for
the stories, Code Freeze, Code merge &
build, Formal V&V (testing), Packaging &
Deployment, Stage testing in prod.
Feature Acceptance Check, Release
Documentation readiness