Our Pipeline is Broken! Salah Elleithy (@selleithy) / George Dinwiddie (@gdinwiddie) Business
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Our Pipeline is Broken! Salah Elleithy (@selleithy) / George Dinwiddie (@gdinwiddie)
Business
What is the Business Pipeline?
Business Delivery - limited view
Request Development Operations
Delivery Pipeline Requirements
A system is never the sum
of its parts, it’s the
product of their
interactions. -Dr. Russell Ackoff
Seattle Municipal Archives
Business Delivery - holistic view
Request Development Operations
Business Pipeline
Theory of Constraints &
Drum / Buffer / Rope
Video to illustrate TOC https://www.youtube.com/watch?v=3s2VdtYw-g0
Where is the Bottleneck?
Crea%ve Co
mmon
s by Nicolas Sere, Paul H
amilton
& Geo
rge Dinw
iddie
The Constraint Set the Drumbeat
Buffer the Inputs to the Constraint
❖ Pull based on need ❖ Don’t starve the
constraint ❖ Adjust just-in-
time to maintain flow
Challenges with the Business Pipeline
Where do requests come from?
Request Source Examples
Planned Work Unplanned Work
Marketing Department Customer Service
Accounting Department Operations
Business Managers Security Group
Customer Research Dependency changes
MVP Tests Analysis of log files
Legal Requirements
Breadth of inputs
End User
Help Desk
Development
President
Dept. Manager
Legal Dept.
Software Architect
Test
Long Chains
End User
Help Desk Triage
Future Story
Bug Fix
Discard
Complex Programs
Multiple sources Competing interests
And
y B
eecr
oft
“Big Picture” Not Visible ❏ Information lost
or modified in the pipeline
❏ Information trickles out a little at a time
lars
juh
Old Backlog
★ Obsolete information
★ Stale & fuzzy understanding
★ Doesn’t reflect recent learning and decisions
Jenn
a W
orkm
an (j
maw
ork)
Complicated Environments
★ Multiple sources of requirements ★ Product management team structure ★ Conflict between stakeholders with no
consensus or resolution ★ Poorly communicated shifting priorities
Value Stream Mapping
Request Source1
Request Source2
Request Source3
Process Process
Process Process
Develop
User Test
Deploy
Process
Backlog
𝝉
𝝉
𝝉
𝝉
𝝉
High-Paid Executive
Ideas on Fixing the Business Pipeline
John
Vac
hon,
U.S
. Far
m S
ecur
ity A
dmin
istra
tion
Common Pitfalls
● Multiple input queues to development o Pushes the priority
decisions from business to development ● Top Executives bypass process
o Prioritizes by HIPPO
© S
alah
Elle
ithy
Agree on a process that works Single input to development
Common Pitfalls ● Business changes their mind
about selection of stories after development has started
● Business changes the acceptance criteria of stories after selection for iteration
● Both of these pull the rug out from under the feet of delivery team
© S
alah
Elle
ithy
Remedies ● Decide priority order before development ● Define scenarios to illustrate acceptance
criteria prior to development ● Manage interruptions and impediments
Progressive Elaboration
● Plan at different time horizons ● Just-in-time story refinement ● Avoid large, stale backlog of small stories ● Split stories as needed ● “Boulders to Rocks to Pebbles”
Collaborate Across Handoffs Three Amigos
• Business people • Programmers • Testers • … and other viewpoints
as needed working together to produce the best possible outcome
http
://w
ww
.pic
tofig
o.co
m/
Explicitly Plumb Your Pipeline Business Initiative Develop
User Test
Deploy
Product Owner
Requirements Analysis 𝝉
Backlog 𝝉
?
3 Amigos
Enhancement Request
Emergency Changes
Defects
Steering Committee
𝝉
Tweet This! Plumb your business pipeline, remove clogs, repeat! #businesspipeline #agile2015
-- @selleithy @gdinwiddie
Related Documents
