Upload
alexey-krivitsky
View
1.247
Download
0
Embed Size (px)
Citation preview
Alexey krivitsky
Scrum trainer Agile coach
Coach for ScrumMasters Software developer
Free-ride skier
fun
profi
t
The earliest large-scale software-intensive product development
… was the Semi-Automatic Ground Environment (SAGE) system. Created in the 1950s, it involved hundreds of people. One of the directors of SAGE was discussing why the programming had gotten out of hand. He was asked: “If you had it to do all over again, what would you do differently?” His answer was to “find the ten best people and write the entire thing themselves.”
large: don’t multisite: don’t offshore: don’t
“After many years working in large, multisite, & offshore development, our key advice?”
“After many years working in large, multisite, & offshore development, our key advice?”
“OK. You’re still gonna do it, so we wrote these books…”
ideal scrum team
in vacuum
Teamresponsibility
Highinteresttowardsresults
Peeraccountability
Decentralizeddecisionmaking
Productthinking
Constanteffortsonminimizingcostofchange
Highprocessandprogresstransparency
HighengagementinproductideaBon
And More complexity • More roles • More meetings • More management • More coordination • More people
And More complexity • More roles • More meetings • More management • More coordination • More people • More focus on workers (instead of work) • More complex solutions • More complex dev process
And More complexity • More roles • More meetings • More management • More coordination • More people • More focus on workers • More complex solutions • More complex dev process • More levels of indirection
Motivation is all about … Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose Purpose
Our Intentions • Developers have sharp focus • Сode changes are under control • Architecture is kept clean • Developers have time for frameworks • …
Tech org It is a complex system with technical focus. You need to have a good engineering background to comprehend and manage it.
⇒ We hire managers with engineering background.
⇒ They create more complex solutions.
More more more More complexity • More roles • More meetings • More management • More coordination • More people • More focus on workers • More complex solutions • More complex dev process • More levels of indirection • Less business focus • Less learning
Self-organize into teams Use your color cards.
Good teams are: • 4-6 people • Good mixture of different colors • Equal number of cold and warm colors
Much better • Less roles • Less incoordination • Less indirection • More transparency • More cross-site collaboration • More decentralization • More business-focus
But…
How does your organizational dynamics look like?
What are the structural factors
that affect decision-making?
Org structure optimized for value delivery
product managers
managers
users
product teams collocated, multi-site