Scaling Alignment: How to grow and still being agile

Scaling
Alignment
How to grow and still being agile
Andreia Kumpera | 2017

Andreia Kumpera
Iteration Manager @elabor8
andreia.kumpera@elabor8.com.au
@akumpera (twitter)
@andreiakumpera (linkedin)

1995 2006 2008
MY STORY
1999
Data
Process
AMS
oPlaneta.com
MedMundo.com
1997 2001 2005
Com
puterScience
ge
Scrum
M
aster
Scrum
M
aster
Coach
/Product
O
w
ner
globo cloud
Delivery
M
anager
Entrepreneur...
2016
I.M
.
Business
School
Developer
Formal Education Companies

+1Tbps
Oneofthelargest
contentdelivery
servicesinBrazil
+1Million
1 Mbps per user
simultaneous users
+10,000 servers capacity
DC Globo
+360employees (IT)
~40 agile teams

+32.5MillionHomepage MAU
+44.9MillionG1 (news)
+26.7Million
GE (sports)
+35.3Million
Gshow (entertainment)
+16.8MillionTechTudo (technology)
+13.7MillionVideos

Andreia Kumpera | 2017Andreia Kumpera | 2017
Wtf???
@#
&%?!
Hey!!!
Huh?
This doesn’t scale
Piece of cakeStill not so hard, right?What's the problem here?

Misalignment
#@?!&
%#@ˆ%!
How can we cross the river?How can we cross the river?

Misalignment
WTF! You guys
are building a
TUNNEL?????
WTF! You guys
are building a
Bridge?????

BOSS
a new
To ﬁx it what we need is…

Do what
I said!
Do
whatever
Alignment Autonomy
False Dichotomy
Alignment & Autonomy

Scaling Alignment Recipe
Share Purpose
Ingredients:

What you are working on, and why?
We
are working on X
because Y said it's
important
We're
done when Y is OK
with it
We
are working on X
because we feel
like it
We're done
when we don't feel
like it anymore
We're working on X
because we think it's
going to impact Y, which
matter to the company
because of Z
We're done
when the metrics
have move
What's the purpose, here?
What's the direction?
We understand how success looks!

The 3 types of Alignment
We're working on
the same product
We're
working for the
same company!
We're
working on the
same feature
•Team
•Department
•Company

Chain of purpose … so that we make life
easier for everyone!
… so that we can connect
the two village
… so that people can cross
the river
We need ﬁnd a permanent way to cross the river!
… so that we can
build a bridge
We're
gathering wood
We're
creating a
foundation

Share Propose
Transparency
Scaling Alignment recipe
Ingredients:

Spotify Strategy Framework Company
beliefs
North Star
2y goal
Company Bet
Beliefs
Insights
Data
• X active users
• World class employer
• Hire a bunch of mobile devs
• Train a bunch of our desktop
devs into mobile devs
• WTF were optimized for the
wrong thing!
• For a long term survival, we
need to became mobile-ﬁrst
• Mobile is overtaking desktop as
primary music gadget!
• We have few mobile devs
compared to desktop
25
50
Desktop Mobile
How people listen
to music
How we’re staffed
Dev Mobile
Dev Desktop

Data Insights Beliefs Bets
Data: Qualitative or
quantitative information
that informs a perspective.
This should not be
interpretation
Insights: What is your
interpretation of the data?
What have you learned?
Beliefs: Based on the
interpretation, which
beliefs have you formed
about the problem space
you are working on?
Bets: Based on your
beliefs, what are the bets
you believe we should
make?
Metrics: What does success look like?

Spotify Company Bets Board
Visible to
everyone

How early can you notice this
happening?
WTF! You guys
are building a
TUNNEL?????
WTF! You guys
are building a
Bridge?????

Dependency Board
Early detection of dependency problems
A centralized
view to enable
decentralized
behavior
Who need
what from
whon & when?

Squad dependencies
With multiple squads there will always be dependencies. Dependencies are not necessarily bad - squads
sometimes need to work together to build something truly awesome. Nevertheless, our goal is to have
squads be as autonomous as possible, especially minimizing dependencies that are blocking or slowing a
squad down.
To aid in this, we regularly ask all our squads which other squads they depend on, and to what extent those
dependencies are blocking or slowing the squad down. Here’s an example:
We then discuss ways to eliminate the problematic dependencies, especially blocking and cross-tribe
dependencies. This often leads to reprioritization, reorganization, architectural changes or technical
solutions.
6/14
Squad dependencies

Share Propose
Transparency
Feedback Loops
Ingredients:

Agile = homing missile
Assumptions:
•The customer discovery what he wants
•The developers discovery how to build it
•Things change along the way

Single team feedback loops

Multi-team feedback loops

Team Boards
Paper
Prototype
Policies, DoD,
DoR and Goal
Current Sprint
Story and
Tasks
Retrospective
Action Plan

Pattern: Continuous Integration
Report A3 (fortnightly)BIG Review! (quarterly)Teams
Increments
Review

Pattern: Plan on cadence, release on demand
Planning
event
Planning
event
Planning
event
Release Candidates Release Candidates
Release 1.0 Release 1.1 Release 1.2 Release 2.0
Release 1.2.1

Share Propose
Transparency
Feedback Loops
Clear priorities
Ingredients:

So much to do…

High-Medium-Low =
a broken way of prioritizing
High
Medium
Low
Launch in
Country A
Build new
product
capability B
Build
infrastructure
for D

All Bets are stack ranked

Stack-ranked bets make it easier to
decide what to work on

Squads are(still) responsible for ﬁguring
out how to make best use of their time

Team breakout: Pulling from the program backlog

Management review / Problem Solving

Share Propose
Transparency
Feedback Loops
Organizational Learning
Clear priorities
Ingredients:

Everything can improve

Are you too busy to improve?
Need more slack in your system!

Where slack comes from

HackDay

Lunch'n'Learn - Coding Dojo

/* Tech Talk */

Don’t overload with stable teams

But Wait!!!
something
is
missing…

Sometimes we like to pretend we have no leaders

Leaderphobia(n)
• Irrational fear of leaders
and leadership
• The mistaken belief that all
leaders are evil and all
leadership is bad
?

Poster Childs of self-organisation

… but who ENABLED this self-organization?

Leader, Who, ME???
Ricardo Semler Gabe Newell Tony Hsieh

Leader’s job in aligned autonomy

Leader’s doesn’t have to be a single person

Share Propose
Transparency
Feedback Loops
Organizational Learning
Clear priorities
Scaling Alignment recipe
Ingredients:

References
https://www.slideshare.net/InfoQ/growing-up-spotify
https://www.kennorton.com/newsletter/2016-04-06-bringing-the-donuts.html
https://www.yumpu.com/en/document/view/55817031/spotify-rhythm/19
http://dius.com.au/2015/06/22/spotify-agile-model/
https://techcrunch.com/2012/11/17/heres-how-spotify-scales-up-and-stays-agile-it-runs-squads-like-
lean-startups/
https://guntherverheyen.com/2015/11/04/sprint-cadence-at-scale/
https://www.kennorton.com/newsletter/2016-04-06-bringing-the-donuts.html
https://www.linkedin.com/pulse/how-spotify-solved-paradox-choice-john-mcdermott
https://hbr.org/2017/02/how-spotify-balances-employee-autonomy-and-accountability
http://futureofcio.blogspot.com.au/2015/12/alignment-and-autonomy-in-agile.html
https://medium.com/@pdelboca/alignment-vs-autonomy-eb2194c3b9c6
https://highﬁve.com/blog/how-spotify-built-one-of-the-best-engineering-cultures/
https://www.linkedin.com/pulse/leadership-moment-alignment-autonomy-jeff-kays
http://blog.crisp.se/wp-content/uploads/2016/03/Agile-@-Lego.pdf
http://blog.crisp.se/wp-content/uploads/2015/10/Scaling-Agile-@-Lego-LeanTribe-Henrik.pdf
https://crisp.se/wp-content/uploads/2016/12/Agile@Lego.pdf
https://hbr.org/1989/09/managing-without-managers
http://www.bbc.com/news/technology-24205497

Scaling Alignment: How to grow and still being agile

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Scaling Alignment: How to grow and still being agile

Semelhante a Scaling Alignment: How to grow and still being agile (20)

Último

Último (12)

Scaling Alignment: How to grow and still being agile