![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](https://image.slidesharecdn.com/designing-autonomous-teams-and-services-together-171020205541/85/Designing-Autonomous-Teams-and-Services-9-320.jpg)
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.
- 18. ntcoding Website Website Website Digital Enterprise IT Business APIs Data APIs DATA Back Office Apps
- 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