at the Program Level Chris Waggoner CSC Keep Austin Agile 2015 CoCreator Jeff LopezStuit Program Challenges Complex Environment Program Challenges Many people to collaborate with Program Challenges Working together on one product ID: 313109
Download Presentation The PPT/PDF document "Exploiting Core Scrum Practices" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Exploiting Core Scrum Practices
at the Program Level
Chris Waggoner, CSC - Keep Austin Agile 2015
Co-Creator:
Jeff Lopez-StuitSlide2
Program Challenges : Complex Environment Slide3
Program Challenges : Many people to collaborate withSlide4
Program Challenges : Working together on one productSlide5
Program Challenges : Lack of big picture “real time” visibilitySlide6
Program Challenges : Lack of a simple means to discuss and clear impediments between teams Slide7
Program Challenges : Lack of means for continuous improvementSlide8
Potential Problems in Programs
Lack
of visibility of impediments • Late arriving issues can impede or kill the program • If you don’t know it, you can’t solve it -> transparency & visibility is needed
• Project boards don’t want to hear problems• Teams or PM hide impedimentsSlide9
Potential Problems in Programs
Lack of team interaction
• Dependencies between teams are not clear • What teams are blocking each other now or in future? Lack of incentive for teams to collaborate
• What is the tangible benefit for cross-team cooperation? • A whole lot of teams means too many meetings? Lack of continuous improvement across program • No inspect & adapt on program level Slide10
Traditional Agile Approaches to Program Complexity
Traditional ApproachSimple Visual Controls
Light Weight Face-to-Face CommunicationsProgram Level ImprovementImpact of Non-Program Teams
Supports Agile Principles?Scrum-of-ScrumsNoneYes
NoneMaybeF2F
Burn chartsYes
Can drive conversationNoneNone
Radiates StatusDashboardsComplex
Can
drive the wrong conversations
None
None
Metrics Driven
Mis
-Behavior
SAFe
and
other
Agile@Scale
Big Picture Road Map
Can drown in complex organizational change
None
Yes
Prescriptive
Attempt at ForecastingSlide11
Scrum Practices on a Program Level
Stand-up
Retrospective
Visible Radiators
Impediment Board
Control by Flow, WIP and Policies
Face-to-Face CommunicationSlide12
The Program Stand-up/Impediment Board Combination
Program Stand-up
Impediment Board
The
Program Stand-up:
Promote visibility, clear impediments and collaboration across the program with 4 questions:
1. What has our team done since last time we met?
2. What will our team do before next time we
meet
?
3. Has another team put something in our way?
4. Are we about to put something in another teams way?
Program Impediment board:
Visible teams dependencies
Simple
visual controls across many teams.
What
teams are blocking each other now? Or in future?
Impediments
(blocked), potential impediments (risks), Action items (task for managers to unblock teams)
Harness the power of F2F communication, visible radiators, and the standup at the program level
Requires a strong facilitator maintaining proper standup protocolsSlide13
Program Impediment board – Simple Sample
Resulted from dependencies conversation between services team and
eCommerce Web teamsVisibility
into impediments required the addition of Operations, Enterprise Architecture, Testing, Security, etc.As visibility improved more groups wanted to help resolve cross-team impediments
Independent Teams
Dependencies and Blocked
The program stand-up should take no longer than 15 minutes or 1 minute per
teamSlide14
Program Impediment board – Complex SampleIndependent Teams
Dependencies and Blocked
20 plus
teams
Meeting lasted 20 minutes or less dailyFirst
on-time at budget project in yearsSuccess credited to visual cues of the impediment board
Blocked
WIP
Backlog
This team used Gizmo avatars for potential impediments
and Gremlins avatars
for impediments
Created later in the release
process
Program
manager was major agile
skeptic
To
force visibility the Program manager declared all WIP as potential
impediments
The
teams represented were not
agile
Fewer
bugs than any release
previous
Used similar board for defect triageSlide15
Standup at Program Impediment BoardIndependent Teams
Dependencies and Blocked
Web
VP
PM
Integration
Program
Manger
Legacy
Services
LegacySlide16
Agile Game: Master Chef
Goal
: Clear impediments and promote collaboration between teams with the
program stand-up and program impediment board Slide17
Program Impediment board – Round 1
Teams
Team vegetables
Team seafoodTeam meat
Team roux
Team gumbo
Team Jambalaya
Team PO boysTeam Plating
Team Dishwashing
Team red beans rice
Ingredients
End-Products
Delivery
Fundamental layer
Teams
Team vegetables
Team seafood
Team meat
Team roux
Team gumbo
Team Jambalaya
Team PO boys
Team Plating
Team Dishwashing
Team red beans rice
Impediments
Old chopping knives
No Bass
Not enough trinity (from veggie)
No beef
No PO boys
Potential impediments
Prepare beans is additional work
Too many meetings to deliver roux?
Not enough roux
Not enough jambalaya
Not enough Red beans & rice
Low morale
Actions
New chopping knives
Remove bass from menu
Order more meat
Make chicken PO boys
Push selling chicken PO boys
Teams
Team
vegetables
Team
seafood
Team
meat
Team roux
Team
gumbo
Team
Jambalaya
Team PO boys
Team Plating
Team Dishwashing
Team red beans rice
IngredientsEnd-ProductsDeliveryFundamental layer
Teams & Dependencies
Impediment BoardSlide18
Program Impediment board – Round 2
Teams
Team vegetables
Team seafood
Team meat
Team roux
Team gumbo
Team Jambalaya
Team PO boys
Team Plating
Team Dishwashing
Team red beans rice
Impediments
Slimy okra
Crawfish delivered too late
Blocking:
No Okra from vegie team
No Crawfish from seafood team
No Crawfish from seafood team
Blocking: no gumbo
No jambalaya,
no red beans/rice
no dishes
quit
Veggie team need to work harder
Potential impediments
Unused beef
Too many meetings to deliver roux?
Actions
Use shrimp from yesterday in stead of crawfish
The meetings are needed to improve quality of roux
Use okra spice powder in stead of fresh okra
Red beans & rice team do the dishwashing
And use the compostable plates
Make red beans & rice every day otherwise we outsource you to India
Slide19
Kanban or Impediment board?
Visualize flow across an entire product development cycle
?
Working impediments
Measuring
cycle
timeCaution: Use only after teams have perfected impediment boardSlide20
Don’t underestimate the power of visibility and F2F conversation
Core Agile Principles do Scale to Program Levels – Be Creative!
Pain Snake
Ad-hoc VisibilitySlide21
Q&A – How else could you use Core Scrum practices like F2F, Ceremonies, and Big Visible Radiators to bring agile value to the Program Level? Retrospective? Release planning? . . .
Stand-up
Retrospective
Visible Radiators
Impediment Board
Control by Flow, WIP and Policies
Face-to-Face Communication