Cobbler's Children Syndrome
The stovepipe enterprise S tovepipes are “systems procured and developed to solve a specific problem, characterized by a limited focus and functionality, and containing data that cannot be easily shared with other systems.” (DOE 1999) DOE. Committee to Assess the Policies and Practices of the Department of Energy, Improving Project Management in the Department of Energy, National Academy Press, Washington, D.C., 1999, page 133.
Mic drop development
40 offices in 14 countries
Dev Ops Team Project Team Vendor Team Dev Project Team Vendor DBA Team Dev Team Project Team
Conway’s Law "Any organization that designs a system (defined more broadly here than just information systems) will inevitably produce a design whose structure is a copy of the organization's communication structure." [Conway, Melvin E. “How Do Committees Invent?” Datamation April (1968) . Print]
Fermat's principle of least time “the path taken between two points by a ray of light is the path that can be traversed in the least time”
Least Time + Conway = Monoliths “the development team chosen to implement a feature is the development team that can implement it in the least time”
Back to our core Agile principles “XP teams are self-organizing and cross-functional. This has two important consequences: first, they're responsible for their own success. Second, XP teams include all the expertise necessary to do so.” [http://www.jamesshore.com/Agile-Book/the_xp_team.ht ml]
responsible for their own success include all the expertise necessary to do so
Microservices was my ‘boss’
Inverse Conway Maneuver Sales Staffing People Support Support Support Vendor Vendor Vendor management management management Stakeholder Stakeholder Stakeholder management management management Change Change Change management management management Infrastructure Infrastructure Infrastructure
Focus on capabilities Staffing People Sales Monolith Teams Leave Leave Rates Rates
Refactor Staffing People Sales Big App Leave Rates Teams
“Make it up fatigue” People Basic auth/SSL n+1 Staffing Sales API Key Pair OAuth 2.0
waste
Infra is rarely touched 1 Microservice 4 commits out of 1000 3 to add environment variables 1 to change log format
Avoiding horizontal centralisation Enforcement Partnership (policing role) Consultancy
/dəˈɡɛrəˌtaɪp, -roʊ-, -riə-, -rioʊ-/ "Susanna Celeste Castelli, DensityDesign Research Lab" .
Control over Ownership “All teams will henceforth expose their data and functionality through service interfaces.”
Return to Conway Staffing Sales People APIs, Web, Widgets, APIs, Web, Mobile, APIs, Web, Mobile Chat Bot Reports Capability tech Capability tech Ruby, ElasticBeanStalk, Solr, Capability tech SFDC, node.js, mondrian, Hangouts, React neo4j, PhoneGap Lambda, Clojure, Angular, iOS Fabric tech Cloud, Data, Monitoring, Analytics, API management, Build, Source, Security, Synthetic monitoring
Cross functional + microservices Fabric Services Product owner Specialists Delivery (PM, QA, Dev) Stakeholder management Vendor management Support
Platform of services Infrastructure Build Identity Logging Monitoring (servers, storage etc.) Notifications and Synthetic Source APIs DNS/SSL escalation monitoring Automated Security Authz/Authn User analytics Resilience security checks monitoring M&A Identity Social IoT Mobile testing Data Infradel No home
Mature towards services Solution Library Patterns Service specific / framework Continuous Build server CruiseControl Snap/Jenkins Integration Capability tech Fabric Tech Genesis Custom build Product Platform / commodity
Autonomy over Standardization Capability Capability platform platform vs Capability tech Fabric tech Fabric tech
http://www.flickr.com/photos/bortescristian/2326692011/
Remove the Yak! Preserve Autonomy by preserving control (responsible for own success) Provide specialisms via microservices (all the expertise necessary)
Recommend
More recommend
