Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Organization and
Architecture,
Autonomy and
Accountability
Kevin Goldsmith

VP Engineering - Consumer
@kevingoldsmith
How Spotify
Builds
Products
Kevin Goldsmith

VP Engineering - Consumer
@kevingoldsmith
How Spotify
Builds Products
(Manchester Remix)
Kevin Goldsmith

VP Engineering - Consumer
@kevingoldsmith
Some
Principles
Speed of iteration beats quality of iteration -
optimizing for speed leads to faster learning,
including from failures, an...
Data >>> Opinion
DATA
VISION
EXPERIMENTSLEARNING
PRODUCT
INFORMS
GUIDES
GENERATES
DRIVES
PROVIDES
Speed without data
means you aren’t learning
Data without speed
means you aren’t learning
fast enough
Autonomous teams
go faster.
How many teams?
>100Teams
>100Teams
autonomous
Autonomous
adjective
au·ton·o·mous - ȯ-ˈtä-nə-məs
(of a country or region) having the freedom to govern itself or control ...
Full-Stack Autonomous Teams
PO
UX
iOS
Android
K&M
QA
Backend
Agile Coach
Fully empowered to fulfill their mission
Full-Stack Autonomous Teams
PO
UX
iOS
Android
K&M
QA
Backend
Agile Coach
Collective Responsibility
Full-Stack Autonomous Teams
PO
UX
iOS
Android
K&M
QA
Backend
Agile Coach
Individual Accountability
Full-Stack Autonomous Teams
PO
UX
iOS
Android
K&M
QA
Backend
Agile Coach
No Manager?
Chapter Lead
Chapter Lead
Chapter Lead
Chapter Lead
Product Owner
Agile Coach
Chapter Lead
Chapter Lead
Product Owner
Agile Coach
Chapter Lead
Chapter Lead
POCLAC
Squads
Squads
Squads
Chapter Leads
Squads
Chapters
Tribe Lead
Squads
Chapters
Tribe
Squads
Chapters
Ideal size: 40-150 people
Tribe
Squads
Chapters
Tribe
Squads
Chapters
Product Owner
Tribe
Squads
Chapters
Product Owner
User Experience
Product Area Leads
Design Leads
Trio TrioTrio
Guild
Trio TrioTrio
Alliance
Alliance
Organization Velocity=
Organization Velocity=
Organization VelocityEnables
Velocity is a core value at Spotify
Our organizational model supports ourvalues
Our organizational model supports ourvalues
Not the otherway around
Requirements
ofAutonomy
Autonomy needs communication
Autonomy needs context
Autonomy needs transparency
Autonomy needs trust
If you can’t trust the
people you hire, you are
bad at hiring people.
So
by giving teams context and trust
by giving teams context and trust
and reducing dependencies
on otherteams
by giving teams context and trust
and reducing dependencies
on otherteams
they can make decisions on their own
by giving teams context and trust
and reducing dependencies
on otherteams
they become AUTONOMOUS!
they can make decisions ...
Autonomous teams don’t have to
synchronize with otherteams as often
or get approval on decisions.
Autonomous teams don’t have to
synchronize with otherteams as often
or get approval on decisions.
They can go faster.
Changeis
constant
“Heisenberg Squads”
I'm not joking here. I can lock a tribe lead in a room and
ask them repeatedly "so what squads do you have", and
not get c...
It is better to solve the problems
created by fluidity rather than
imposing more structure.
It is better to solve the problems
created by fluidity rather than
imposing more structure.
Minimum Viable
Bureaucracy
=Autonomy
=Autonomy Chaos?
=Autonomy Chaos?
How do we prevent
the chaos?
What / Why
What / Why
What / Why
How
What / Why
How
Grow MAU
Simplify Navigation
Investment
Investment
Time
Think it Build it Ship it Tweak it
Investment
Investment
Time
Think it Build it Ship it Tweak it
Investment
Investment
Time
Think it Build it Ship it Tweak it
Investment
Investment
Time
Think it Build it Ship it Tweak it
Paper Prototypes
UI Mockups
User Testing
MVP
Employee
Testin...
That is still a lot of full-
stack teams building the
product!
Full-stack autonomous teams
Requires structuring your application in
loosely coupled parts
Microservices!
LoadBallancer
Microservices yay!
Easierto scale based on real-world bottlenecks
Microservices yay!
Easierto test
Microservices yay!
Easierto deploy
Microservices yay!
Easierto monitor
Microservices yay!
Can be versioned independently
Microservices yay!
Are less susceptible to large failures
Microservices boo!
are harderto monitor
Microservices boo!
need good documentation / discoverytools
Microservices boo!
create increased latency
Microservices @ Spotify
Microservices @ Spotify
‣ 810activeservices
Microservices @ Spotify
‣ 810activeservices
‣ ~10Systemspersquad
Microservices @ Spotify
‣ 810activeservices
‣ ~10Systemspersquad
‣ ~1.7Systemsperpersonwithaccessto
productionservers
Microservices @ Spotify
‣ 810activeservices
‣ ~10Systemspersquad
‣ ~1.7Systemsperpersonwithaccessto
productionservers
‣ ~1...
Microservices @ Spotify
Microservices @ Spotify
‣ Owned/Operatedbysquads
Microservices @ Spotify
‣ Owned/Operatedbysquads
‣ On-callusuallyownedbychapters
Microservices @ Spotify
‣ Owned/Operatedbysquads
‣ On-callusuallyownedbychapters
‣ Significanttoolingcreatedby
infrastruct...
Microservices @ Spotify
‣ Owned/Operatedbysquads
‣ On-callusuallyownedbychapters
‣ Significanttoolingcreatedby
infrastruct...
Microservices @ Spotify
‣ Owned/Operatedbysquads
‣ On-callusuallyownedbychapters
‣ Significanttoolingcreatedby
infrastruct...
Client
Server
Core Library
Platform Platform Platform Platform
Infrastructure
Server
Core Library
Platform Platform Platform Platform
Infrastructure
Server
Core Library
Platform Platform Platform Platform
Infrastructure
Server
Core Library
Platform Platform Platform Platform
Infrastructure
Server
Core Library
Platform Platform Platform Platform
Infrastructure
Server
Core Library
Platform Platform Platform Platform
Infrastructure
Challenges
Challenges
Synchronization
Challenges
Synchronization
Client UX implementation
Challenges
Synchronization
Client UX implementation depends on
Challenges
Synchronization
Client UX implementation
Core Library Implementation
depends on
Challenges
Synchronization
Client UX implementation
Core Library Implementation
depends on
depends on
Challenges
Synchronization
Client UX implementation
Core Library Implementation
depends on
depends on
Server Implementation
Challenges
Synchronization
Client UX implementation
Core Library Implementation
depends on
depends on
depends onServer Imp...
Challenges
Synchronization
Client UX implementation
Core Library Implementation
depends on
depends on
depends onServer Imp...
Server
Core Library
Platform Platform Platform Platform
Infrastructure
Shared Frameworks
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
UI ...
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
Com...
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
Com...
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release TeamUI C...
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
Int...
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
Int...
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
Sha...
Shared Frameworks
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
FeatureTeam
App Release Team
Sha...
Shipping @
speed
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6
Development Stabilization
Beta 1 Beta 2
Release
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6
Development Stabilization
Beta 1 Beta 2
Release
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6
Development Stabilization
Beta 1 Beta 2
Release
Week 3 Week 4 Week 5 Week 6
Stab...
4 Weeks
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6
Development Stabilization
Beta 1 Beta 2
Release
Week 3 Week 4 Week 5 Wee...
4 Weeks
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6
Development Stabilization
Beta 1 Beta 2
Release
Week 3 Week 4 Week 5 Wee...
Week 1 Week 2 Week 3 Week 4
Development Stabilization
Beta
Release
Week 1 Week 2 Week 3 Week 4
Development Stabilization
B...
3 Weeks 3 Weeks3 Weeks
Week 1 Week 2 Week 3 Week 4
Development Stabilization
Beta
Release
Week 1 Week 2 Week 3 Week 4
Deve...
3 Weeks 3 Weeks3 Weeks
Week 1 Week 2 Week 3 Week 4
Development Stabilization
Beta
Release
Week 1 Week 2 Week 3 Week 4
Deve...
Week 1 Week 2 Week 3
Development Stabilization
Beta
Release
Week 1 Week 2 Week 3
Development Stabilization
Beta
Release
We...
Week 1 Week 2 Week 3
Development Stabilization
Beta
Release
Week 1 Week 2 Week 3
Development Stabilization
Beta
Release
We...
Week 1 Week 2 Week 3
Development Stabilization
Beta
Release
Week 1 Week 2 Week 3
Development Stabilization
Beta
Release
We...
Week 1 Week 2 Week 3
Development Stabilization
Beta
Release
Week 1 Week 2 Week 3
Development Stabilization
Beta
Release
We...
Whatdoesn’t
workwell?
Big Projects
Big Projects
‣ Autonomousteamsmakescoordination
difficult
Big Projects
‣ Autonomousteamsmakescoordination
difficult
‣ Nofull-timeprojectmanagersin
technologyorganization
Big Projects
‣ Autonomousteamsmakescoordination
difficult
‣ Nofull-timeprojectmanagersin
technologyorganization
‣ Veryunev...
Big Projects
‣ Autonomousteamsmakescoordination
difficult
‣ Nofull-timeprojectmanagersin
technologyorganization
‣ Veryunev...
Growing Senior Leaders
Growing Senior Leaders
‣ Tribeleadshavepeoplemanagement,
strategyanddeliveryresponsibility
Growing Senior Leaders
‣ Tribeleadshavepeoplemanagement,
strategyanddeliveryresponsibility
‣ ChapterLeadshavepeople
manage...
Resource Efficiency
Resource Efficiency
‣ Autonomousteamsareresourcehungry
becausetheyneedtobeself-sufficient
Resource Efficiency
‣ Autonomousteamsareresourcehungry
becausetheyneedtobeself-sufficient
‣ Teamscangetfocusedonimproving
...
So…
So…
‣ Wewanttolearnfasterthanourcompetition
So…
‣ Wewanttolearnfasterthanourcompetition
‣ Usingdatatovalidateourideashelpsusmakegooddecisionswhilegoingfast
So…
‣ Wewanttolearnfasterthanourcompetition
‣ Usingdatatovalidateourideashelpsusmakegooddecisionswhilegoingfast
‣ Autonomo...
So…
‣ Wewanttolearnfasterthanourcompetition
‣ Usingdatatovalidateourideashelpsusmakegooddecisionswhilegoingfast
‣ Autonomo...
So…
‣ Wewanttolearnfasterthanourcompetition
‣ Usingdatatovalidateourideashelpsusmakegooddecisionswhilegoingfast
‣ Autonomo...
Questions?
twitter: @kevingoldsmith
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)
Upcoming SlideShare
Loading in …5
×

How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)

28,546 views

Published on

This was an extended version of the talk that I gave at InfoShare 2016 in GDansk. This version of the talk was presented at ao.com and Think Money in Manchester UK in May 2016. This is a remix of several earlier talks and some new content to tie Spotify's autonomy and continuous improvement culture to it's data-driven product development approach to show the complete picture. As usual, I tend to talk to slides instead of putting a lot of the content into the slides themselves, so sorry if these don't have all the info.

Published in: Leadership & Management

How Spotify Builds Products (Organization. Architecture, Autonomy, Accountability)

  1. 1. Organization and Architecture, Autonomy and Accountability Kevin Goldsmith
 VP Engineering - Consumer @kevingoldsmith
  2. 2. How Spotify Builds Products Kevin Goldsmith
 VP Engineering - Consumer @kevingoldsmith
  3. 3. How Spotify Builds Products (Manchester Remix) Kevin Goldsmith
 VP Engineering - Consumer @kevingoldsmith
  4. 4. Some Principles
  5. 5. Speed of iteration beats quality of iteration - optimizing for speed leads to faster learning, including from failures, and faster learning leads to higher quality; optimizing for quality is an obstacle to speed, which undermines learning and slows down improvements to quality. Spotify Company Belief
  6. 6. Data >>> Opinion
  7. 7. DATA VISION EXPERIMENTSLEARNING PRODUCT INFORMS GUIDES GENERATES DRIVES PROVIDES
  8. 8. Speed without data means you aren’t learning
  9. 9. Data without speed means you aren’t learning fast enough
  10. 10. Autonomous teams go faster.
  11. 11. How many teams?
  12. 12. >100Teams
  13. 13. >100Teams autonomous
  14. 14. Autonomous adjective au·ton·o·mous - ȯ-ˈtä-nə-məs (of a country or region) having the freedom to govern itself or control its own affairs. "the federation included sixteen autonomous republics" having the freedom to act independently. "school governors are legally autonomous" synonyms: self-governing, independent, sovereign, free, self-ruling, self-determining, autarchic; self-sufficient "an autonomous republic" Full-Stack Autonomous Teams (Squads) PO UX iOS Android K&M QA Backend Agile Coach
  15. 15. Full-Stack Autonomous Teams PO UX iOS Android K&M QA Backend Agile Coach Fully empowered to fulfill their mission
  16. 16. Full-Stack Autonomous Teams PO UX iOS Android K&M QA Backend Agile Coach Collective Responsibility
  17. 17. Full-Stack Autonomous Teams PO UX iOS Android K&M QA Backend Agile Coach Individual Accountability
  18. 18. Full-Stack Autonomous Teams PO UX iOS Android K&M QA Backend Agile Coach No Manager?
  19. 19. Chapter Lead
  20. 20. Chapter Lead
  21. 21. Chapter Lead
  22. 22. Chapter Lead
  23. 23. Product Owner Agile Coach Chapter Lead Chapter Lead
  24. 24. Product Owner Agile Coach Chapter Lead Chapter Lead POCLAC
  25. 25. Squads
  26. 26. Squads
  27. 27. Squads Chapter Leads
  28. 28. Squads Chapters
  29. 29. Tribe Lead Squads Chapters
  30. 30. Tribe Squads Chapters Ideal size: 40-150 people
  31. 31. Tribe Squads Chapters
  32. 32. Tribe Squads Chapters Product Owner
  33. 33. Tribe Squads Chapters Product Owner User Experience
  34. 34. Product Area Leads
  35. 35. Design Leads
  36. 36. Trio TrioTrio
  37. 37. Guild
  38. 38. Trio TrioTrio
  39. 39. Alliance
  40. 40. Alliance
  41. 41. Organization Velocity=
  42. 42. Organization Velocity=
  43. 43. Organization VelocityEnables
  44. 44. Velocity is a core value at Spotify
  45. 45. Our organizational model supports ourvalues
  46. 46. Our organizational model supports ourvalues Not the otherway around
  47. 47. Requirements ofAutonomy
  48. 48. Autonomy needs communication
  49. 49. Autonomy needs context
  50. 50. Autonomy needs transparency
  51. 51. Autonomy needs trust
  52. 52. If you can’t trust the people you hire, you are bad at hiring people.
  53. 53. So
  54. 54. by giving teams context and trust
  55. 55. by giving teams context and trust and reducing dependencies on otherteams
  56. 56. by giving teams context and trust and reducing dependencies on otherteams they can make decisions on their own
  57. 57. by giving teams context and trust and reducing dependencies on otherteams they become AUTONOMOUS! they can make decisions on their own
  58. 58. Autonomous teams don’t have to synchronize with otherteams as often or get approval on decisions.
  59. 59. Autonomous teams don’t have to synchronize with otherteams as often or get approval on decisions. They can go faster.
  60. 60. Changeis constant
  61. 61. “Heisenberg Squads”
  62. 62. I'm not joking here. I can lock a tribe lead in a room and ask them repeatedly "so what squads do you have", and not get clear answers. It isn't a case of "it's hard to collect the information and keep it up to date" – it is a case of the wave-form of org-quantas not collapsing into reality until they are observed, and sometimes not even then. It's Schrödinger's squads, where sometimes the cat escaped before going in the box and sometimes the box gets stolen before opened. Mikael Krantz, Spotify Chief Architect
  63. 63. It is better to solve the problems created by fluidity rather than imposing more structure.
  64. 64. It is better to solve the problems created by fluidity rather than imposing more structure. Minimum Viable Bureaucracy
  65. 65. =Autonomy
  66. 66. =Autonomy Chaos?
  67. 67. =Autonomy Chaos?
  68. 68. How do we prevent the chaos?
  69. 69. What / Why
  70. 70. What / Why
  71. 71. What / Why How
  72. 72. What / Why How
  73. 73. Grow MAU Simplify Navigation
  74. 74. Investment Investment Time Think it Build it Ship it Tweak it
  75. 75. Investment Investment Time Think it Build it Ship it Tweak it
  76. 76. Investment Investment Time Think it Build it Ship it Tweak it
  77. 77. Investment Investment Time Think it Build it Ship it Tweak it Paper Prototypes UI Mockups User Testing MVP Employee Testing Gradual Rollout A/B Testing User Testing Analytics Validation A/B Testing User Testing Analytics ValidationBeta
 Testing
  78. 78. That is still a lot of full- stack teams building the product!
  79. 79. Full-stack autonomous teams Requires structuring your application in loosely coupled parts
  80. 80. Microservices!
  81. 81. LoadBallancer
  82. 82. Microservices yay! Easierto scale based on real-world bottlenecks
  83. 83. Microservices yay! Easierto test
  84. 84. Microservices yay! Easierto deploy
  85. 85. Microservices yay! Easierto monitor
  86. 86. Microservices yay! Can be versioned independently
  87. 87. Microservices yay! Are less susceptible to large failures
  88. 88. Microservices boo! are harderto monitor
  89. 89. Microservices boo! need good documentation / discoverytools
  90. 90. Microservices boo! create increased latency
  91. 91. Microservices @ Spotify
  92. 92. Microservices @ Spotify ‣ 810activeservices
  93. 93. Microservices @ Spotify ‣ 810activeservices ‣ ~10Systemspersquad
  94. 94. Microservices @ Spotify ‣ 810activeservices ‣ ~10Systemspersquad ‣ ~1.7Systemsperpersonwithaccessto productionservers
  95. 95. Microservices @ Spotify ‣ 810activeservices ‣ ~10Systemspersquad ‣ ~1.7Systemsperpersonwithaccessto productionservers ‣ ~1.15Systemspermemberof Technology
  96. 96. Microservices @ Spotify
  97. 97. Microservices @ Spotify ‣ Owned/Operatedbysquads
  98. 98. Microservices @ Spotify ‣ Owned/Operatedbysquads ‣ On-callusuallyownedbychapters
  99. 99. Microservices @ Spotify ‣ Owned/Operatedbysquads ‣ On-callusuallyownedbychapters ‣ Significanttoolingcreatedby infrastructuretosimplifybuilding/ supporting
  100. 100. Microservices @ Spotify ‣ Owned/Operatedbysquads ‣ On-callusuallyownedbychapters ‣ Significanttoolingcreatedby infrastructuretosimplifybuilding/ supporting ‣ ArchitectureReviewsencouraged
  101. 101. Microservices @ Spotify ‣ Owned/Operatedbysquads ‣ On-callusuallyownedbychapters ‣ Significanttoolingcreatedby infrastructuretosimplifybuilding/ supporting ‣ ArchitectureReviewsencouraged ‣ SecurityReviewsrequired
  102. 102. Client
  103. 103. Server Core Library Platform Platform Platform Platform Infrastructure
  104. 104. Server Core Library Platform Platform Platform Platform Infrastructure
  105. 105. Server Core Library Platform Platform Platform Platform Infrastructure
  106. 106. Server Core Library Platform Platform Platform Platform Infrastructure
  107. 107. Server Core Library Platform Platform Platform Platform Infrastructure
  108. 108. Server Core Library Platform Platform Platform Platform Infrastructure
  109. 109. Challenges
  110. 110. Challenges Synchronization
  111. 111. Challenges Synchronization Client UX implementation
  112. 112. Challenges Synchronization Client UX implementation depends on
  113. 113. Challenges Synchronization Client UX implementation Core Library Implementation depends on
  114. 114. Challenges Synchronization Client UX implementation Core Library Implementation depends on depends on
  115. 115. Challenges Synchronization Client UX implementation Core Library Implementation depends on depends on Server Implementation
  116. 116. Challenges Synchronization Client UX implementation Core Library Implementation depends on depends on depends onServer Implementation
  117. 117. Challenges Synchronization Client UX implementation Core Library Implementation depends on depends on depends onServer Implementation Infrastructure Implementation
  118. 118. Server Core Library Platform Platform Platform Platform Infrastructure
  119. 119. Shared Frameworks
  120. 120. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam
  121. 121. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team
  122. 122. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team
  123. 123. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team
  124. 124. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team UI Interface Guidelines
  125. 125. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team Common UI Components UI Interface Guidelines
  126. 126. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team Common UI Components UI Interface Guidelines SharedTesting Frameworks
  127. 127. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team
  128. 128. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team
  129. 129. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release TeamUI Consistency Validation
  130. 130. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team IntegrationTesting UI Consistency Validation
  131. 131. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team IntegrationTesting App Submittal UI Consistency Validation
  132. 132. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team
  133. 133. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team Shared DevelopmentTree
  134. 134. Shared Frameworks FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam FeatureTeam App Release Team Shared DevelopmentTree Best Practice Sharing
  135. 135. Shipping @ speed
  136. 136. Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Development Stabilization Beta 1 Beta 2 Release
  137. 137. Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Development Stabilization Beta 1 Beta 2 Release
  138. 138. Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Development Stabilization Beta 1 Beta 2 Release Week 3 Week 4 Week 5 Week 6 Stabilization Beta 1 Beta 2 Release Week 1 Week 2 Week 3 Week 4 We Development Sta Beta 1 Bet
  139. 139. 4 Weeks Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Development Stabilization Beta 1 Beta 2 Release Week 3 Week 4 Week 5 Week 6 Stabilization Beta 1 Beta 2 Release Week 1 Week 2 Week 3 Week 4 We Development Sta Beta 1 Bet
  140. 140. 4 Weeks Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Development Stabilization Beta 1 Beta 2 Release Week 3 Week 4 Week 5 Week 6 Stabilization Beta 1 Beta 2 Release Week 1 Week 2 Week 3 Week 4 We Development Sta Beta 1 Bet 12 releases / year
  141. 141. Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Wee Development Week 4 Stabilization Release
  142. 142. 3 Weeks 3 Weeks3 Weeks Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Wee Development Week 4 Stabilization Release
  143. 143. 3 Weeks 3 Weeks3 Weeks Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Week 2 Week 3 Week 4 Development Stabilization Beta Release Week 1 Wee Development Week 4 Stabilization Release 17 releases / year
  144. 144. Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 We Development St Be
  145. 145. Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 We Development St Be 2 Weeks 2 Weeks 2 Weeks 2 Weeks 2 Weeks
  146. 146. Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 We Development St Be 2 Weeks 2 Weeks 2 Weeks 2 Weeks 2 Weeks
  147. 147. Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 Week 3 Development Stabilization Beta Release Week 1 Week 2 We Development St Be 2 Weeks 2 Weeks 2 Weeks 2 Weeks 2 Weeks 26 releases / year
  148. 148. Whatdoesn’t workwell?
  149. 149. Big Projects
  150. 150. Big Projects ‣ Autonomousteamsmakescoordination difficult
  151. 151. Big Projects ‣ Autonomousteamsmakescoordination difficult ‣ Nofull-timeprojectmanagersin technologyorganization
  152. 152. Big Projects ‣ Autonomousteamsmakescoordination difficult ‣ Nofull-timeprojectmanagersin technologyorganization ‣ Veryunevenexecutionrecord
  153. 153. Big Projects ‣ Autonomousteamsmakescoordination difficult ‣ Nofull-timeprojectmanagersin technologyorganization ‣ Veryunevenexecutionrecord ‣ Gotintosomebadanti-patterns
  154. 154. Growing Senior Leaders
  155. 155. Growing Senior Leaders ‣ Tribeleadshavepeoplemanagement, strategyanddeliveryresponsibility
  156. 156. Growing Senior Leaders ‣ Tribeleadshavepeoplemanagement, strategyanddeliveryresponsibility ‣ ChapterLeadshavepeople managementresponsibilityandoperate inhighlyconsensus-driventeams
  157. 157. Resource Efficiency
  158. 158. Resource Efficiency ‣ Autonomousteamsareresourcehungry becausetheyneedtobeself-sufficient
  159. 159. Resource Efficiency ‣ Autonomousteamsareresourcehungry becausetheyneedtobeself-sufficient ‣ Teamscangetfocusedonimproving thingswithintheirsphereofcontrol, ignoringlargerissues
  160. 160. So…
  161. 161. So… ‣ Wewanttolearnfasterthanourcompetition
  162. 162. So… ‣ Wewanttolearnfasterthanourcompetition ‣ Usingdatatovalidateourideashelpsusmakegooddecisionswhilegoingfast
  163. 163. So… ‣ Wewanttolearnfasterthanourcompetition ‣ Usingdatatovalidateourideashelpsusmakegooddecisionswhilegoingfast ‣ Autonomousteamshelpusgofaster
  164. 164. So… ‣ Wewanttolearnfasterthanourcompetition ‣ Usingdatatovalidateourideashelpsusmakegooddecisionswhilegoingfast ‣ Autonomousteamshelpusgofaster ‣ Looselycoupledarchitectureshelpautonomousteamsworkwithoutcoordination bottlenecks
  165. 165. So… ‣ Wewanttolearnfasterthanourcompetition ‣ Usingdatatovalidateourideashelpsusmakegooddecisionswhilegoingfast ‣ Autonomousteamshelpusgofaster ‣ Looselycoupledarchitectureshelpautonomousteamsworkwithoutcoordination bottlenecks ‣ Reducingtimebetweenreleasesincreaseslearningopportunities
  166. 166. Questions? twitter: @kevingoldsmith

×