Presentation given at 2016 Talk'n'roll conference.
For last two years, seems like every company tries to SCALE their Scrum. It all started with SAFe, followed by LeSS and Nexus. I’ll quickly walk you through those frameworks history and differences between them. We’ll also try to answer question: Do we really need this all scaling or it’s yet another way for consultants to get some of your money?
Object-Oriented Programming, Systems, Languages & Applications '95
Empiricial
Meant for complex product and environments
Meant for development at the EDGE of chaos
Meant for big teams
Scrum is not methodology – it’s a framework:
Lightweight
Simple
Not easy
Dictionary.com
http://www.dictionary.com/browse/scaling
Need to scale scrum?
What about even first case od IDX?
Notable implementations – 1996 IDX Systems – now GE Healthcare.
240% measured productivity gain. Incredible story.
http://www.scruminc.com/wp-content/uploads/2015/06/IDX-Case-Study-The-First-Scaled-Scrum.pdf
Dean Leffingwell
Chief Methodologist at Scaled Agile
It has concepts from: Lean, Agile, XP.
Four level:
Team
Program – 5-10 teams
Portfolio
Value Stream
It has it all. It has all the answers. It’s impressive.
In 1997 Dean Leffingwell – his company RequisitePro was introduced.
Chief Methodologist at Scaled Agile.
By Craig Larman
Empirical process
Focus on whole procduct
Structure –
LeSS Product
LeSS Sprint
One Sprint
Informal
There is no SoS meeting – informal communication
Big Room Planning
http://less.works/less/framework/why-less.html
Nexus is a framework that drives to the heart of scaling: cross-team dependencies and integration issues.
Not a solution!
Integration issues at the heart.
Nexus integration team – from other members
Integrated increment
Response to SAFe gaining market.
Planning
Lip service, earlier date picked by management
Strolling
Done on my machine
Mostly Done
We really mean it’s done
Stabilization
Testers see the product
Hidden agenda backlog
Rapid descoping phase
Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiation
Responding to change over following a plan
First learn how to apply Scrum on one collocated team level.
Then start looking at implementing it for bigger ammount of teams, then introduce second location and try to get addditional benefit.
The job of management is to do anything to help them do so, not suffocate them with SAFe.
Ken Schwaber
https://kenschwaber.wordpress.com/2013/08/06/unsafe-at-any-speed/
Don’t let Agile become Cargo Cult, don’t mimic practices.
The job of management is to do anything to help them do so, not suffocate them with SAFe.
Ken Schwaber
https://kenschwaber.wordpress.com/2013/08/06/unsafe-at-any-speed/