My field notes from the 2016 Regional Scrum Gathering Tokyo.
Talk : Cisco’s Agile Journey
Continuous Delivery – Large Scale Enterprise-wise Delivery Transformation
100% Waterfall –> Agile Practice
71,000 people
How to convey from LEGACY –> Agile?
(2.5 years in 2016, and they’re not done)
The Cisco DS60/80 Machine was used in the movie The Martian
blurb
accelerate time to capacity
small and mighty teams
active stakeholders
iterative approach
improve software quality
testing and automation
embed SMEs
fail fast/recover fast
optimise cost of delivery
dedicated teams
adaptive infrastructure
self-service tools
Culture –> Mindset –> Perception
Product Roadmap is Continuously Changing.
interesting.
interface waterfall with Agile Teams
Chaos.
Continuous Delivery As A Service
hmm.
Change in waves.
Pioneer (Wave 1) – Ambassador Network
Business Critical (Wave 2) – Scalable Value, Risks
All Others – Finish the job, concrete, everyone gets to go
Ambassadors grew from 30 to 100 people
Talk: Economically Sensible Scrum
Focus on idle work, not on idle workers.
Ken Rubin
Watch The baton, not the runners.
Understand the cost of change
Predictive (guesswork) VS Adaptive (chaos)
Queue Size == Cost of Delay
Have small and frequent releases
Be Agile but not BE AGILE
Optimise on the Product Level
A Team of developers is NOT a complete Scrum Team
Know the different between a Component VS a Feature Team
Component Team
- owns an asset area/ code base
- single component (GUI, Routing, API)
Feature Team
- builds a valuable feature to a customer
- cross-functional
A FEATURE for a Component Team is a TASK for a Feature Team
*click*
Hello, I am D. 