Scaling Scrum 1.00.01 bnd Tomek Włodarek © 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution– NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
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
Scaling Scrum
1.00.01 bnd
Tomek Włodarek
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
Scaling Scrum Tomek Włodarek
If a problem cannot be solved, enlarge it. –Dwight D. Eisenhower
”
“ © 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
how long have you been doing Scrum?
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
more than 5 years
more than 3 years
more than a year
failed or not interested
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
stam·pede /stʌmˈpiːd/
1. (masowy pęd) A sudden frenzied rush of panic–stricken animals.
2. (uciekać w popłochu) To flee in a headlong rush.
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
scale·pede /skʌlˈpiːd/
1. (masowy pęd) A sudden frenzied rush of panic–stricken companies to scale Scrum because they need more software, now.
2. (uciekać w popłochu) To flee in a headlong rush to prescribed methods intellectual fads because scaling Scrum is difficult.
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
what is scaling Scrum?
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
organizational transformation towards Scrum?
single team working on several projects?
multiple teams working on unrelated products?
multiple teams working on a single product?
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
any implementation of Scrum where multiple Scrum teams build one product in one or more Sprints
any implementation of Scrum where multiple Scrum teams build a product suite (multiple related products) in one or more Sprints
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
how many people have you involved?
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
more than a 1000? (OMFG)
500 to 1000?
250 to 500?
150 to 250?
50 to 150?
less than 50? (lucky bastards)
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
why to scale Scrum?
promising results with 1–3 teams
desire to gain similar benefits from larger groups
to have more work done, faster
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
(when it is assumed that a phenomenon functions linearly, overlooking important factors that may produce non-linearity)
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
linear fallacy
what are the two biggest hurdles when scaling Scrum?
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
communication
dependencies
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
what causes most scaling efforts fail?
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
communication
dependencies
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶
”
“ It's a cognitive challenge to keep track of more (than 150) people.
–Robin Dunbar https://www.youtube.com/watch?v=ppLFce5uZ3I
https://stevelekson.files.wordpress.com/2011/08/dunbar-neocortex-size-and-group-size.pdf
🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶 🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶🚶
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd). ”
“ It's a cognitive challenge to keep track of more [than 150] people.
–Robin Dunbar https://www.youtube.com/watch?v=ppLFce5uZ3I
https://stevelekson.files.wordpress.com/2011/08/dunbar-neocortex-size-and-group-size.pdf
Any organization that designs a system will inevitably produce a design whose structure is a
copy of the organization's communication structure.
–Melvin Conway http://www.melconway.com/research/committees.html
http://hbswk.hbs.edu/item/5894.html
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd). ”
“
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
(opposite is also true: teams structure tends to lean towards current system architecture)
dependencies: internal, external, business domains, product lines, PBIs, someone’s presence (or absence), relationships, process, workflow, priviledges, access rights, specialities, competencies, knowledge, source code quality and ownership, versions merging, real or perceived modules boundaries, frameworks, layers, components, systems, DBs, tools, …
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
Dependencies are fucking evil. *
s c r u m v i v a l . c o m / 2 0 1 3 0 6 2 0
so, how to scale Scrum?
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
don’t
”
“ Scaling Agile methods is the last thing you should do. A better approach is to try to scale down your
project. –Martin Fowler
http://martinfowler.com/bliki/LargeAgileProjects.html
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
problems scale (much) easier than solutions
(don’t scale up if you struggle with professional Scrum at a team level; you will end up with even bigger mess)
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
think of alternatives
”
“ Before every action ask yourself. Will this bring more monkeys on my back? Will the result of my
action be a blessing or a heavy burden? –Alfred Armand Montapert
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
do better Scrum at a team level
build up current teams’ capabilities (skills, motivation, relationships, tools)
focus on value, produce less software
…
…
(meh… gimme real solution!)
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
Nexus
6±3 Scrum Teams
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
(additive framework; Scrum foundations, principles and values; opens communication; widens and deepens inspect and adapt mechanisms; fosters continued transparency; relies on bottom-up intelligence)
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
überscrum
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
1 Product = 1 Backlog (and possibly 1 Product Owner to run them all)
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
software is invisible (thank goodness outcomes of running software are visible)
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
enable integration (think beyond technical e.g. communication, relationships,
cultural, environmental)
integrate work across all levels often
build and inspect integrated increments often
identify and remove dependencies early and often
strive for technical excellence (practices, architecture, quality)
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
Dependencies are fucking evil. *
s c r u m v i v a l . c o m / 2 0 1 3 0 6 2 0
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
don’t share PBIs (refine, reframe, regroup)
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
Nexus+
6±3 Nexuses
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
o’rly?
© 2015 Tomek Włodarek. This work is licensed under a Creative Commons Attribution–NonCommercial–NoDerivs 3.0 Unported License (by-nc-nd).
thank you! questions?
[email protected] twitter: @poddrzewem http://www.linkedin.com/in/wlodarek http://www.poddrzewem.pl https://www.scrum.org/Resources/What-is-Scaled-Scrum http://www.scrumvival.com
Related Documents
