Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Designing Autonomous Teams and Services
Similar to Designing Autonomous Teams and Services (20)
More from Nick Tune
More from Nick Tune (9)
Recently uploaded
Recently uploaded (20)
Designing Autonomous Teams and Services
- 2. ntcoding Nick! You disappoint me! Credit: jaxenter.de
- 3. ntcoding
- 5. ntcoding ā Consistently the best source of new ideas are the developers!ā¦ āØ Good teams ensure their engineers contribute to make the product better ā Marty Cagan (@cagan) svpg.com/good-product-team-bad-product-team/
- 6. ntcoding
- 7. ntcoding TOP SOURCES OF PRODUCT IDEAS DIRECT CUSTOMER FEEDBACK 80 % TEAM BRAINSTORMING 64 % SALES TEAM 53 % EXECUTIVE ORDER 51 % * % respondents who agreed. Source: Alpha UX Product Management Insights 2017
- 8. ntcoding CONTINUOUS DISCOVERY & DELIVERY Discovery Track Delivery TrackCross-functional Product Team
- 9. ntcoding ā ā [company] regularly send their developers to work on farms with their customers [farmers] Melissa Perri CEO Produx Labs @lissijean The Build Trap: www.ustream.tv/recorded/102860435
- 10. ntcoding
- 11. ntcoding Credit: Twitter/Corby Policy
- 14. ntcoding Domain-Driven Design will enable the next big leap in creating high performance organisations
- 15. #1 GIVING BOUNDED CONTEXTS A LITTLE MAKEOVER
- 16. ntcoding BOUNDED CONTEXTS & DDD Problem domains can be broken down into cohesive contexts that encapsulate things that change together for business reasons.
- 17. ntcoding BOUNDED CONTEXTS = AUTONOMY Align teams with bounded contexts, and teams will have the autonomy to continuously discover and deliver.
- 19. ntcoding We bought a rules engine to replace the slow programmers!
- 21. ntcoding BOUNDED CONTEXT HEURISTICS ā¢ Linguistic patterns ā¢ Domain expert localisation ā¢ Data cohesion
- 24. ntcoding Bounded contexts are an organisation design tool! Autonomous contexts!!!!
- 25. ntcoding Bounded contexts are too low level. We need to understand types of BC & how they interact.
- 27. ntcoding Understanding relationships between contexts helps us to design autonomous teams and services
- 28. ntcoding Sociotechnical patterns indicate which teams need to be more closely aligned & with common goals
- 29. ntcoding Sociotechnical patterns indicate which implementations patterns may be appropriate
- 30. ntcoding STABLE SEQUENTIAL PROCESS Review Resubmit Renegotiate
- 31. ntcoding ORGANISATIONAL IMPLICATIONS ā¢ Teams will likely be long-lived ā¢ Expect low coordination across teams ā¢ Optimise for autonomy and productivity of individual teams ā¢ Caveat: some work will span teams
- 32. ntcoding TECHNICAL IMPLICATIONS ā¢ Consider allowing more freedom to use different technologies ā¢ Prefer commands over events ā¢ Pair program with upstream/downstream teams to spread domain knowledge
- 34. ntcoding ORGANISATIONAL IMPLICATIONS ā¢ Optimise for speed of discovery ā¢ Discovery team will be short-lived ā¢ Combine people from different teams ā¢ New teams may need to be formed
- 35. ntcoding TECHNICAL IMPLICATIONS ā¢ Discovery service(s) likely to be broken up and distributed between contexts ā¢ Service boundaries may change ā¢ Services may grow ā¢ May need to build temporary integrations
- 37. ntcoding ORGANISATIONAL IMPLICATIONS ā¢ Higher coordination between partners ā¢ Try to avoid competing initiatives ā¢ Prepare for team volatility ā¢ Consider a temporary shared backlog
- 38. ntcoding TECHNICAL IMPLICATIONS ā¢ May want to standardise on tech choices ā¢ Possibly shared DB or components ā¢ Encourage cross-team pairing to improve chances of new insights
- 40. ntcoding ORGANISATIONAL IMPLICATIONS ā¢ Octopus team may need a relationship with many teams - slow progress ā¢ Changes may need to be coordinated across many teams ā¢ It could get political!
- 41. ntcoding TECHNICAL IMPLICATIONS ā¢ Consider isolating integration complexity within the octopus ā¢ Consider process-manager, and scatter gather integration patterns
- 42. #4 CHOOSING PATTERNS THAT MAXIMISE FLOW
- 43. ntcoding The domain alone does not tell us everything. We must analyse the system of work to find the best model.
- 44. ntcoding THEORY OF CONSTRAINTS The performance of an organisation is limited by constraints. Remove constraints to improve performance of the organisation.
- 46. ntcoding
- 47. ntcoding Prefer models that eliminate the biggest bottlenecks
- 48. ntcoding But we canāt eliminate all bottlenecks - how do we know which are the constraints?
- 49. ntcoding ā ā The CORE DOMAIN is where the most value should be added in your system.
- 50. ntcoding WHAT IS CORE CAN CHANGEā¦ Slack started life as an internal chat system. It is now the core domain worth $5bn. techcrunch.com/2017/07/26/slack-is-raising-a-250-million- round-at-5-billion-valuation/
- 51. ntcoding SITUATIONAL AWARENESS Use different sociotechnical architecture patterns at different stages of the product innovation lifecycle
- 54. ntcoding The DDD community has an opportunity to step forward and become pioneers of modern organisation design
- 55. ntcoding CONTINUOUS DISCOVERY We need to understand how modern organisations practice continuous discovery & delivery, and show how bounded contexts enable it
- 56. ntcoding SOCIOTECHNICAL PATTERNS We need to start exploring and documenting sociotechnical architecture patterns
- 57. ntcoding I DARE YOU ā¢ Study the sociotechnical patterns in your organisation ā¢ Note the organisational and technical implications ā¢ Write a blog post describing the pattern and itās implications