Transcription
TeamTopologiesat Parts UnlimitedManuel Pais&Matthew Skelton24 Jan 2020TeamTopologies.com@TeamTopologies
Team TopologiesOrganizing business andtechnology teams for fast flowMatthew Skelton & Manuel PaisIT Revolution Pressteamtopologies.com/book2
Team-First ApproachStreams & PlatformsEnablementOrg Dynamics3
Team-First Approach4
Concerns about current team organization1. not always clear what team is working on2. lack of focus, pulled in many directions3. biz/tech expectations mismatch4. Slack / comms overflow5
Team size 9 ** possibly 156
COGNITIVE LOAD:The total amount ofmental effort being usedin the working memory- John Sweller7
Software that is ‘too big forour heads’ works againstorganizational agility8
9
Each service must be fullyowned by a team withsufficient cognitive capacityto build and operate it.10
Recommendations1. assess teams’ cognitive load2. detect gaps in capabilities(“enablement” section)3. identify how platform can help(“streams & platforms” section)11
Streams & Platforms14
15
Current business streams1. manufacturing2. in-store sales3. ecommerce sales4. engine sensor5. parts delivery16
Current platform servicesCI/CD : UnikettelData APIs : Narwhal(Project Shamu)17
Concerns about platform viability1. unclear platform onboarding2. which teams are responsible for platform3. how to scale18
“A digital platform is a foundation ofself-service APIs, tools, services,knowledge and support which arearranged as a compelling internalproduct.”– Evan Bottcher, 201819
Platformtreat the platform as aproduct (reliable, usable, fitfor purpose) for internalcustomers20
Platform as a Productstrong collaboration withstream-aligned teams forany new service or evolution21
Platform as a Producton-call supportservice status pagessuitable comms channelsresponse time for incidentsdowntime planned & announced& good product management22
23
Recommendations1. define & fund platform teams & group2. pilot services for monitoring & telemetryin collaboration with Promotions team3. stabilize & document Unikettel / SaaS24
25
Enablement31
32
Concerns about cross functional teams1. large skill set required2. reliant on hiring new engineers3. guilds don’t target teams’ needs33
Enabling Purposeteam of experts to helpbridge capability gaps(technical or product mgmt)34
Enabling Purposereduce dependencies onexperts by teaching ratherthan doing the work35
Enabling Behaviorsfacilitate knowledge via training, workshops tool/framework selection pairing on examples guidance on good practices36
The success of enablingteams is the success ofstream-aligned teams39
Recommended Domains for Enabling TeamsContinuous DeliveryAutomated TestingProduct DevelopmentBusiness & system monitoringDesign/UXSecurity40
Org Dynamics41
42
Source: 13918925344
The Org ChartSource: “Team of Teams”, McChrystal, 201545
The Org ChartSource: “Team of Teams”, McChrystal, 201546
Rapid flow of change47
Co-design of org andsystem architecture48
“Any organization that designs asystem (defined broadly) willproduce a design whose structure isa copy of the organization'scommunication structure.”– Mel Conway, 196849
“if the architecture of the system andthe architecture of the organizationare at odds, the architecture of theorganization wins”– Ruth Malan, 200850
ReverseConwayImage from Max Pixel51
Rapid feedback fromsystems & customers52
53
ReverseConwayImage Source: rn-project/54
Thank you!teamtopologies.comMatthew Skelton, Conflux@matthewpskeltonManuel Pais, Independent@manupaisableCopyright Conflux Digital Ltd 2018-2019. All rights reserved.Registered in England and Wales, number 10890964Icons made by Freepick from www.flaticon.com - used under license55
Team Topologies at Parts Unlimited Manuel Pais & Matthew Skelton 24 Jan 2020. Team Topologies 2 . 3. ecommerce sales 4. engine sensor 5. parts delivery. 17 Current platform services CI/CD : Unikettel . produce a design whose structure is a copy of the organization's
