Professional Documents
Culture Documents
Program Pattern 1 2 3 4 5 6
Doing
Team 1
(Delivery Section) PULL The
1 2 3 4 5 6 Work
Operational Team 2 Right
PULL
Pattern 1 2 3 4 5 6
Strategy
Idea Discover Deliver
A
E B Deliver
Deliver
Deliver
Deliver Iteratively
• Idea D C
• Strategic Initiative
• New Requirement
• Enhancement Understand Governance/ Iteratively build, test
& Funding And deliver
• Problem Gates
• Opportunity Strategize
Build/Test
Mobilize Explore/Strate Manage/
Understand /
gize Evolve
Implement
Explore
Mobilize Understand P
/Strategize
• Scope
Idea Propose
Problem
Desired
Cost/Benefit
Outcome
Plan
DISCOVERY Blockers
Collaborate Iterate
to till
Elaborate Estimate Epics Done
Solution
Strategy
-100%
Optional
At start of At end of
iteration iteration
xyz
xyz
Large
xyz xyz
Small
P P P P PP P
P P P P P
P P P P
P P P P P PPP P P
P
P P
P
P
P P P P
P P P
P P P P P P P
P
P P P P
P P
P
Deliver R3
Deliver R2
Discover 1 Discover 2 Deliver R1 Operate
Optional
IM
CM
PM
Program Program
Story 1 Story 2
Task
• Steering committee
Governance • PMO
PM
• Key Stakeholders
Extended • External experts
• Enterprise Architect
IM
• Business SME (Customer)
• Analysts
• Developers
Core • Testers
• Solution Architect
5 - 9 people
The Team
The Product Owner
The Iteration Manager
The Project Manager
Change Manager
These are the committed parties, the people responsible for the success
of the project and product
There will be other involved parties, but they won’t be responsible for the
success of the project or product
SC
Steering
SP
PGM
CM
PM
SH Extended
EXP
PO
IM
SME Core
TM
PM
IM IM
SH PO SH PO
TM SME TM SME
Core
Ext
EXP EXP
Team 1
Team 2
Agile Project 1
© 2014 IBM Corporation
…And shared ownership of customer/user outcomes by teams
Self organization
Making commitments
Meeting commitments
Management of the team – every team member is responsible for this
Respecting other members of the team
IM IM CM
Change Management
TEAM 1 TEAM 2 CM TEAM
SC
Executive SP
PGM
PM
SH PO SH PO
TM SME TM SME
Core
Ext
EXP EXP
Team 1
Team 2
Agile Project 1
– Chaired by Sponsor
Steering committee – Senior Execs from the BU
executing the project/program
– Senior impacted BU
SP
executives – (Customers)
– Senior execs of partners or
PGM key suppliers
Agile Program – Risk and Compliance
PM (optional)
IM IM
SH PO SH PO
Ext
• Inspire
EXP EXP
• Challenge
•
Team 1
Team 2
Serve
Agile Project 1
SP
Decision 24-48 hour
Work SLA
PGM
Groups
Agile Program
PM
Also called
Product Owner Forum
IM IM
Agile Project 1
Benefits identification?
Benefits estimation?
Benefits scoping? Product Owner
Ensuring the solution can deliver
the benefits expected?
Benefits tracking? Product Owner
Benefits harvesting? Sponsor
31
1. Small
2. X-functional
3. Core and X-tended
4. Dedicated and committed team members
5. Single outcome that is shared and clearly understood by
all team members
6. Very supportive and do whatever is needed to help reach
the outcomes
7. Structured with a PM, IM, SME and Product Owner.
8. Clear decision making responsibilities
9. All team members collaborate and contribute
continuously and effectively
Strategy
Idea Discover Deliver
A
E B Deliver
Deliver
Deliver
Deliver Iteratively
• Idea D C
• Strategic Initiative
• New Requirement
• Enhancement Understand Governance/ Iteratively build, test
& Funding And deliver
• Problem Gates
• Opportunity Strategize
Build/Test
Mobilize Explore/Strate Manage/
Understand /
gize Evolve
Implement
Explore
Mobilize Understand P
/Strategize
• Scope
Objectives Benefits
Better
Business Case Designs
Cost/ Benefit? Better
Products
Prioritise &
manage the Happier
funnel people
Explore Highly
options productive
teams
Discovery Brief
Name Name of the initiative. This can be a large program, project or just an idea.
Summary Quick Summary
Initiator Name of the staff member who is the owner of this brief and is responsible for
driving it through to the next stage.
Problem statement A statement of the business problem that this initiative is trying to solve.
If No! Implications of *Not* implementing the initiative. The pain of ‘do nothing’
1-2 hour max!
Constraints Any constraints on the initiative, resourcing, cost, timescales, technology
Wish Date
Filled in by the initiator
When would you like to have this done by
Benefit estimate Rough estimate of total business benefits this could generate
Cost appetite How much maximum would you be willing to spend on this project
Initiative size Small (<50d) / Medium (50-200d) / Large (200-500d) / X-Large (500d+)
Key stakeholders A list of the key stakeholders that should be included in the inception phase for
this initiative. These are the key people that will be impacted by the change.
Name and Date Name of the person writing the brief and the date its written on
Problem
Pain impact Benefit estimate
Statement
WHO
• Initiator
• Key Stakeholders
• Key Experts
WHEN
• As soon as all the key people are
available
HOW LONG
• Run in a facilitated workshop setting
• Can be multiple workshops with breaks in
between
• Not spread over more than 3-4 weeks
• Workshop time should be in the region of 1-5
days or as necessary
Impact Analysis
(So What?)
Stakeholder mapping
INFLUENCE
© 2014 IBM Corporation
Other examples of Stakeholder Analysis
Business Outcomes
Explore
Mobilize Understand P
/Strategize
• Scope
O1
O2
You
Are
Here
IN OUT
???
Those big pieces of work that need to be done to achieve the desired outcome!
Epic 1
Epic 5
MVP1
Feature
Feature Feature Use:
Epic1 Feature Design thinking
Process maps
Brainstorming
Feature Feature
Feature
Epic2 Feature Feature
Feature
HIGH
High
impact
High prob.
High
impact
High prob.
IMPACT
LOW
PROBABILITY HIGH
© 2014 IBM Corporation
Dependencies
Program
Internal External
Technology
People
Process
Design Thinking
‘DETERMINE THE
REAL PROBLEM…
CONSIDER A
WIDE RANGE OF
POTENTIAL
SOLUTIONS…
CONVERGE ON A
PROPOSAL.’
Option 1 ++ + -
Option 2 ++ + ++
Option 3 + ++ ++
Explore
Mobilize Understand P
/Strategize
• Scope
Program
Project
Stream
Team
Optional
BENEFITS
Best Case
COSTS
Base Case
PICS + PPT
-100%
xyz
xyz
Large
xyz xyz
Small
• The work
• Approved project scope
At start of At end of
iteration iteration
Program Program
Story 1 Story 2
Task
Elaboration
• Identification • Build
• Story writing • Acceptance • Test
criteria • Deploy
• Size
• Test cases
Elicitation Execution
Feature breakdown
Personas
Design Thinking Practices
Business Canvas
Process
Value Stream Mapping (as-is and to-be)
Brain storming
Outcomes
User/customer interviews
Who Personas
What Process
Why Outcomes
As a ___________________________________
I want ________________________________
So that _____________________________
Elaboration
• Identification • Build
• Story writing • Acceptance • Test
criteria • Deploy
• Size
• Test cases
Elicitation Execution
Less
Always Sometimes
often
Technical
ID Narrative
design
78
Acceptance Test
Test Case
79
Elaboration
• Identification • Build
• Story writing • Acceptance • Test
criteria • Deploy
• Test cases
Elicitation Execution
3. Social contract
Elaboration
• Identification • Build
• Story writing • Acceptance • Test
criteria • Deploy
• Size
• Test cases
Elicitation Execution
84
As the team we need a release plan so that Estimate features Map iterations to
we can set ourselves targets & milestones and and stories time
socialise delivery projections with our
stakeholders
…. gave us our Product Backlog (on the wall and in a tool)
MVP
MOSCOW / H – M – L / 1,2,3…
1,2,3,5,8,13,2, infinity
© 2014 IBM Corporation
Our pseudo Fibonacci
sequence
In Agile/Scrum, many use a pseudo
Fibonacci sequence to assign story
points to stories
Large estimates are less accurate;
larger gaps between larger estimates
help us avoid splitting hairs
unnecessarily
92
© 2014 IBM Corporation
Estimate size; derive duration
93
© 2014 IBM Corporation
Story spliting
• A
• B
• C
• D
• E
I1 I2 I3 I4
Velocity = bucket size
Iteration Buckets
© 2014 IBM Corporation
Release Plan
I1 I2
Release wall
In
Planned Progress Testing Done
Iteration wall
Optional
At start of At end of
iteration iteration
• 1:1
• Deep dives
• Take time to understand
the real issues
• Listen
• Socialise
• Praise
• Talk to stakeholders
• Get more than one
opinion
• Move boulders
• Carry water
• Work closely with the PM
and PO
Continuous Buddy
monitoring Builds
Continuous Continuous
deployment Integration
Automated
testing
“A retrospective is a gathering of a
community at regular intervals throughout
a delivery to review the events and learn
from the experience.”
(Issues)
Burn-up Struggle
I1 I2 Street
Release wall
Risks
In
Planned Progress Testing Done
Iteration wall
Architecture
wall
110
Original Revised
planned prognoses
completion date completion date
15 March 2011 15 April 2011
Original scope in Story points
Scope cut needed
Story points
to meet Original
targets
Satisfy Involve
Influence
Keep
Monitor
Informed
Impact
Watch
Monitor
closely
Impact
Identify
• Scope creep
• Hangover stories
Done Elaborate • Changes during the
iteration
• Bugs found
• Wrong estimates
• Epics not stories
Test Build • Unavailable SME
• BAU
118