Transitioning from Timeboxes to Continuous Product Delivery (by Steve Stolt and Steven Younge)
58
Think Outside the (Time) Box Transitioning from Timeboxes to Continuous Product Delivery
-
Upload
andre-faria-gomes -
Category
Business
-
view
810 -
download
0
description
Agile continuous flow (Kanban) methods aren’t only for Operations and Support anymore -- Product Development teams now use them for strategic, date-sensitive initiatives to achieve faster time to market. Proceed with caution! Simply throwing away timeboxes can be dangerous. We took the journey from a timeboxed to a continuous flow software delivery model. We brought along a large tribe of developers, testers, product owners, dev-ops people, UX designers, and stakeholders. We got lost a few times on the way, but we did find our destination.
Transcript of Transitioning from Timeboxes to Continuous Product Delivery (by Steve Stolt and Steven Younge)
Think Outside the(Time) Box
Transitioning from Timeboxesto Continuous Product Delivery
Intro
Stephen Younge works here Steve Stolt works here
“Continuous Product Delivery?”
Feature Inventory
Continuous delivery? Easy! Just change everything.
(Well, maybe it isn’t that easy)
Tuesday, August 6 • 3:45pm - 5:00pm • Canal B
Steve Stolt and Steve Neely
Learning Objectives
After today's session, you'll be able to:● decide if continuous product delivery is right
for your team● create a transition plan based on our
learnings● deal with the reality of dates● apply kanban principles to higher levels of
planning and tracking● engage with stakeholders during the journey
About you
● Kanban or Scrum?
Agenda
● Where we started from● Why we changed● What we changed● Challenges● Inspect and Adapt● Advantages● Q&A
Agenda
● Where we started from● Why we changed● What we changed● Challenges● Inspect and Adapt● Advantages● Q&A
Starting Point
May 2010In business 9+ years Agile and Scrum from day 12 Scrum teams2 week sprints8 week releases
Stakeholders
● Published roadmap
● Release planning every 8 weeks
● Publish major features
● Everyone plans to those dates
● Monthly product council meeting
RoadmapQ1 Q2 Q3 Q4
Initiative
Feature
Initiative
Feature
Initiative
Feature
Initiative
Feature
InitiativeFeature
Initiative
Feature
Initiative
Feature
Initiative
Feature
Feature
Feature
RELEASE RELEASE RELEASE RELEASE RELEASE RELEASE
Agenda
● Where we started from● Why we changed● What we changed● Challenges● Inspect and Adapt● Advantages● Q&A
Timeboxes - good and bad
● Stakeholder expectations
● Feature finished week 2
● Feature "close" week 7-8
● Feature isn't included in a release
Intellectual curiosity
● Intellectual curiosity around kanban and Lean
● Value Stream Mapping
● A3
● Donald Reinertsen
● Desire to inspect and adapt
Agreement
Continuous deployment for engineering
Continuous flow for the business (in-part kanban)
Agenda
● Where we started from● Why we changed● What we changed● Challenges● Inspect and Adapt● Advantages● Q&A
We love change - we move fast
Canceled meetingsTraining on kanban and leanSet up kanban boardsThis felt great.............................AT FIRST!
Tooling Changes
Tooling Changes
Delivery team process
Kanban● manage work in process (WIP) limits● track story/defect throughput
Moving away from dates...
Agenda
● Where we started from● Why we changed● What we changed● Challenges● Inspect and Adapt● Advantages● Q&A
Role confusion
Scrum Masters?
Product Owners?
Lost Routines
Iteration Planning
Release Planning
Retros
Estimation
Still needed?
Do we still need to estimate stories?
Do we need to estimate tasks?
Interruptions
No timebox
It is always a good time
How about now?
Stakeholders
“Where are our dates?”
Agenda
● Where we started from● Why we changed● What we changed● Challenges● Inspect and Adapt● Advantages● Q&A
Role Changes
Scrum Masters - Full-time Coaches
Removal of roadblocks - Product Owners
New team routines
Weekly time booked● replenish ready queue - if needed● plan upcoming work - if needed● retrospectives - always
Delivery team features
Features● planned end dates● check-ins
Feature toggles
Are awesome!
Give you control● staged rollouts● A/B testing● rollback● market release● incremental feedback!
Feature kanban● transparency● self-serve
Feature-level Status Reporting
How to Align ‘Above’ Features?
Objectives
Check-ins with Stakeholders
Are we on track?Do we need to make adjustments?
Objectives - delivery team
Objectives● co-authored by the product and delivery team● a guidepost for the delivery team● delivery team - stakeholder alignment
Objectives - A few walls help
Alignment between Stakeholders and Team
Stakeholders
Team
ObjectivesFeatures
Initiatives Business Goals
Shield and
Check-ins
Stories and Defects
RoadmapPrevious Quarter
Feature
Initiative
Feature
Initiative
Feature
Feature
InitiativeFeature
Initiative
InitiativeInitiative
Feature
Feature
Feature
RecentlyDelivered
Current Quarter
NextQuarter Beyond
FEATURES
In Progress Prep Ideas
Everybody Bought In
Team● more efficient and
responsive with continuous delivery
● focus on WIP and cycle time
Stakeholders● features out faster● transparency● engaged
Alignment on a single set of business objectives and medium grained features
Our New Reality
Agenda
● Where we started from● Why we changed● What we changed● Challenges● Inspect and Adapt● Advantages● Q&A
Engineering efficiency
Small, frequent releases
Less to debug, if needed - goodNot free - bad
No More Branches
No More Patches
The last 5%
If we need another week we can get it
Requires discipline
Delivery Teamsprefer continuous delivery(at least ours seem to)
Rapid Response for new features
We plan to have space to respond
Smaller releases = smaller feedback (focused)
Less to respond to - if needed
ASAP
We have come far...... but we’re not done
Agenda
● Where we started from● Why we changed● What we changed● Challenges● Inspect and Adapt● Advantages● Q&A
QUESTIONS?
Stephen [email protected]@stephen_younge
Steve [email protected]@stevestolt
or stop by our booth or our reception on Tuesday at 7p
end
