scrum 4 program draft
TRANSCRIPT
Scrum Program Managementtowards Enterprise Scrum
working document
Big Picture
scrum team
scrum team
scrum team
scrum team
scrum team
scrum program
Levels of Protections
scrum team
scrum team
scrum team
scrum team
scrum team
scrum program
Scrum Program protects team initiatives from Management decisions to ensure a permanent flow of coherent value
Program Vision
Team Goal
Team Goal
Team Goal
Team Goal
Team Goal
Team Goal
capability
capability
capability
capability
capability
capability
feature
feature
feature
feature
feature
feature
story
story
story
story
story
story
self organised teams
3 Mont
hs R
elea
se a
s Sa
fe-
to-f
ail co
ntai
ner
How to structure Program Backlog?
Program Vision
Team Goal
Team Goal
Team Goal
Team Goal
Team Goal
Team Goal
capability
capability
capability
capability
capability
capability
feature
feature
feature
feature
feature
feature
story
story
story
story
story
story
self organised teams
3 Mont
hs R
elea
se a
s Sa
fe-
to-f
ail co
ntai
ner
How to structure Program Backlog?
defined by each team
Program cadence
The Program cadence is set on a pace of 3 months:
over 3 months you increase the risks of stop-and-gos from Management
under 3 months, the change is too important to ensure both value generation and business agility (response to business, customer or user oriented requests)
Framework (naming convention)
Team also known as Scrum team is a group of 7 +/- 2 people including Product Owner, Scrum Master and at least one developer and one tester. A team is stable, this mean that a team member is fully dedicated to its team.
Floaters are people working for several teams, they are floating.
Crowd is the ensemble of all the teams working in a program organisation. Like for birds, the crowd is swarming in a same direction.
Basic Framework
Release Backlog
Release Update
Release Update
Release
2 weeks 2 weeks 2 weeks 2 weeks 2 weeks 2 weeks
1 month 1 month 1 month
Release Scope
change change
Change here is related to “strategical” change lead by management. Business change is managed at team level and managed by the POs at sprint end or planning. Emerging change from development is managed within the sprint like traditional scrum.
How to start
Program Vision
Team Goal
Team Goal
Team Goal
Team Goal
Team Goal
The Chief Product Owner shares the strategical roadmap with the crowd.
Program Vision is the answer to “what means done in 3 months?”
The strategical roadmap is shared with the teams and they design their “goal” or “team vision” on what part of the Program they are able to develop.
During Program Planning workshop, team’s goals are put together for alignment and dependencies are made visible and countermeasures taken.
How to manage itonce a week the POs are gathering into a Scrum-of-scrums and ask to 4 questions:
what have you done since last time we met? does something impeding your progress? what do you plan next? are you putting something in someone’s shoes?
objective of the meeting is replanning due to emerging changes and alignment of the efforts
that’s not a status meeting
usually, the POs are giving feedback in front of the Release Plan.
Release UpdateFacilitated by Chief Product Owner
This is a Program Review in front of the crowd and program stakeholders
It’s the Inspect-and-Adapt of the Release Roadmap
New changes can be added into the Program Backlog and items from same size or value are removed.
Removed items are taken into account for the next release or totally removed if no longer necessary.
Roles(CPO) Chief Product Owner: responsible and accountable for the Program Backlog. CPO activity is mostly alignment and coordination of team efforts. The CPO is protecting the crowd from unplanned strategical requests. He or She is responsible for the time-to-market and the return of investment.
(SC) Scrum Coach (not an authority): he or she is supporting the crowd and the CPO by shielding the program from interferences due to impediments, risks and distractions. The SC is facilitating the dynamic of the crowd with the support of the team’s scrum masters. He or she is leading the change for the program and its stakeholders.
appendix
Principleset up
program vision
what mean release done?
each work stream defines its own vision for the next 3
months
all visions are consolidated into a program vision and challenged
dependencies are evaluated and are constraints to prioritisation
collective validation of the release of the next 3 months
incl. goals
3 months fixed scope
1 single consolidate
d vision
sort from low to high dependency
collective engagement
and organisatio
n
Release supportive organisationNext 3 months
Next 6 months
Go liveProgram Roadmap
• Design a high level architecture supporting the roadmap.
• Architecture should be improved at each release milestone.
• Self-Reorg: Based on that roadmap, ask team members which team they want to support during the next 3 months release
Architecture Update Architecture Update Architecture Update
Rel
ease
Rev
iew
R
oadm
ap U
pdat
e R
etro
spec
tive
Rel
ease
Rev
iew
R
oadm
ap U
pdat
e R
etro
spec
tive
Rel
ease
Rev
iew
R
oadm
ap U
pdat
e R
etro
spec
tive
1 day workshoprelease release release
Self - reorg Self - reorg Self - reorg
Tracking Progress
Go-
live
Rel
ease
Rel
ease
Pro
gram
Bac
klog
= s
um o
f all
Bac
klog
s
Change request and updates drop-outs
Nex
t Go
Live
Pro
gr. B
ackl
og
Treasury
ICO
Ex.Control
Royalties
R2R
Controlling
• Progress tracked bottom up
• Sprints are aligned: starting and ending at the same time
• Program velocity is the sum of all team´s velocities
• At Sprint end, Release roadmap is updated according to each sprint outcomes
Scrum Program MeetingsScrum level Scrum Program levelDaily standups Weekly Scrum-of-scrumsSprint Planning Release PlanningSprint Review Release Review
Monthly Roadmap updateSprint Retrospective Roadmap Retrospective
Recommendation: Release Planing, Release Review
and Roadmap Retrospective should be handled during a one
day collaborative workshop
option 1
Program LevelDAILY MEETINGS
• DAILY STAND UP • Attendees: Scrum Team (Development Team, Scrum Master, Product Owner) • Moderation: Scrum Team (self organised) • Purpose: status meeting, highlight impediments • Duration: 15 minutes • When: each day, same time, same location WEEKLY MEETINGS
• REFINEMENT MEETINGS • Attendees: Scrum Team (Development Team, Scrum Master, Product Owner) + people to respond on team issues • Moderation: Scrum Master • Purpose: grooming both Sprint and Product Backlog in Development perspective, Planning Poker (effort estimation),
collaborative solution focused meeting • Duration: 45 minutes • When: once a week
• SCRUM-OF-SCRUMS • Attendees: Product Owners, Management (passive) & Customers (passive) • Moderation: Chief Product Owner • Purpose: status meeting on development, identify and respond on overlaps and hints • Duration: 45 minutes • When: once a week, same day, same place
• GROOMING • Attendees: Product Owners,& Customers (passive) • Moderation: Product Owner • Purpose: user stories and product backlog grooming, set up business values on user stories • Duration: 45 minutes • When: once a week, same day, same place
BI-WEEKLY MEETINGS • SPRINT PLANNING
• Attendees: Management & Customers (on-demand), Scrum Team • Moderation: Product Owner • Purpose: defining Sprint Objective and Sprint Backlog • Duration: 45 minutes • When: at Sprint start
• SPRINT REVIEW • Attendees: Management & Customers (active), Scrum Team • Moderation: Product Owner • Purpose: show and tell of sprint outcomes, inspect/adapt from the stakeholders • Duration: 45 minutes • When: at the end of the Sprint
• SPRINT RETROSPECTIVE • Attendees: Scrum Team • Moderation: Scrum Master • Purpose: inspect/adapt from the development process, • Duration: 45 minutes • When: after Sprint Review
• ROADMAP UPDATE • Attendees: Management, Customer, RUN (HB Operations), Users • Moderation: Chief Product Owner • Purpose: Update the roadmap according to Sprint outcomes • Duration: 45 minutes • When: after Sprint Review MONTHLY MEETINGS
• RELEASE MEETING • Attendees: Management & Customers (active), PO Team • Moderation: Chief Product Owner • Purpose: show and tell of sprint outcomes, inspect/adapt from the stakeholders • Duration: 45 minutes • When: at the end of the Release
option 2
