2015 10 How to Structure Multi-Team Organizations

1. How to Structure Multi-Team Organizations Ken Furlong

2. The evolution of an organizational structure

3. In the Beginning…

4. In the Beginning… Single Person

8. In the Beginning… Single Person Single Team

14. Expansion happens… Single Person Single Team

66. Expansion happens… Single Person Single Team Mob

67. How do we evolve? Single Person Single Team Mob ?

70. How do we evolve? Single Person Single Team Mob ?Functional Teams

71. How do we evolve? Single Person Single Team Mob Functional Teams

72. How do we evolve? Single Person Single Team Mob Functional Teams

73. How do we evolve? Single Person Single Team Mob Functional Teams </>

77. How do we evolve? Single Person Single Team Mob Functional Teams </> 

86. How do we evolve? Single Person Single Team Mob Functional Teams </>  Component Teams

87. How do we evolve? Single Person Single Team Mob Functional Teams  Component Teams

91. How do we evolve? Single Person Single Team Mob Functional Teams Component Teams

94. How do we evolve? Single Person Single Team Mob Functional Teams Web Component Teams

99. Dependencies Web

101. Dependencies Web 2

106. Dependencies Web 6 100%

107. Dependencies Web 6 100% 80%

108. Dependencies Web 6 100% 80% 60%

109. Dependencies Web 6 100% 80% 60% 40%

110. Dependencies Web 6 100% 80% 60% 40% 20%

111. Dependencies Web 6 100% 80% 60% 40% 20% 0%

112. Dependencies Web 6 Value Add 100% 80% 60% 40% 20% 0%

113. Dependencies Web 6 Value Add Waste 100% 80% 60% 40% 20% 0%

123. Dependencies Web Value Add Waste 100% 80% 60% 40% 20% 0%

141. “Feature” Teams Single Person Single Team Mob Functional Teams Web Component Teams

142. “Feature” Teams Single Person Single Team Mob Functional Teams Component Teams

149. “Feature” Teams Single Person Single Team Mob Functional Teams Component Teams Feature Teams

150. “Feature” Teams Single Person Single Team Mob Functional Teams Component Teams Feature Teams </> 

151. “Feature” Teams Single Person Single Team Mob Functional Teams Component Teams Feature Teams </>  </> 

152. “Feature” Teams Single Person Single Team Mob Functional Teams Component Teams Feature Teams </>  </>  </> 

153. “Feature” Teams Single Person Single Team Mob Functional Teams Component Teams Feature Teams </>  </>  </>  </> 

154. “Feature” Teams Single Person Single Team Mob Functional Teams Component Teams Feature Teams </>  </>  </>  </>  </> 

155. “Feature” Teams Single Person Single Team Mob Functional Teams Component Teams Feature Teams </>  </>  </>  </>  </>  </> 

162. Encapsulation </> 

172. Encapsulation </>  9 10 11 12 1 2 3 4

176. T-Shaped Skills

187. T-Shaped Skills Web

223. T-Shaped Skills Web Web Web

224. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams </>  </>  </>  </>  </>  </> 

225. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams </>  </>  </>  </>  </> 

226. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams </>  </>  Search </>  </>  </> 

227. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams </>  </>  Search </>  </> 

228. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams </>  </>  Search Digital Content </>  </> 

229. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams </>  Search Digital Content </>  </> 

230. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart </>  Search Digital Content </>  </> 

231. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Search Digital Content </>  </> 

232. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content </>  </> 

233. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content </> 

234. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations </> 

235. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations

236. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console

252. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Cart Pay- ments Search Digital Content Recommendations Admin Console

253. Instincts Get in the Way… Single Person Single Team Mob Functional Teams Component Teams Cart Pay- ments Search Digital Content Recommendations Admin Console Categorized Feature Teams

254. Where did we go wrong? Single Person Single Team Mob Functional Teams Component Teams Categorized Feature Teams

255. Where did we go wrong? Single Person Single Team Mob Functional Teams Component Teams Categorized Feature Teams

256. Let’s take a trip…

257. Let’s take a trip… We need some groceries.

258. We need some groceries… Check out

267. Evolution Path Single Person Single Team Mob

272. Evolution Path Single Person Single Team Mob Functional Teams

273. Let’s try Functional Teams… Check out

274. Let’s try Functional Teams… Checkout Bagging

294. Evolution Path Single Person Single Team Mob Functional Teams Component Teams

295. Let’s try Component Teams…

296. Let’s try Component Teams… Dry Goods

297. Let’s try Component Teams… Frozen Dry Goods

298. Let’s try Component Teams… Perishable Frozen Dry Goods

299. Let’s try Component Teams… Perishable Frozen Dry Goods Other

307. Let’s try Component Teams… Perishable Frozen Dry Goods Other ?

308. Let’s try Component Teams… Perishable Frozen Dry Goods Other ? ?

309. Let’s try Component Teams… Perishable Frozen Dry Goods Other ? ? ?

310. Let’s try Component Teams… Perishable Frozen Dry Goods Other ? ? ? ?

311. Let’s try Component Teams… Perishable Frozen Dry Goods Other ? ? ? ? ?

312. Let’s try Component Teams… Perishable Frozen Dry Goods Other ? ? ? ? ? ?

313. Let’s try Component Teams… Perishable Frozen Dry Goods Other ? ? ? ? ? ? ?

316. Let’s try Component Teams… Perishable Frozen Dry Goods Other RequirementsGathering ? ? ? ? ? ? ?

317. Let’s try Component Teams… Perishable Frozen Dry Goods Other RequirementsGathering ProgramManagement ? ? ? ? ? ? ?

318. Let’s try Component Teams… Perishable Frozen Dry Goods Other RequirementsGathering ProgramManagement ? ? ? ? ? ? ?

319. Let’s try Component Teams… Perishable Frozen Dry Goods Other RequirementsGathering ProgramManagement ? ? ? ? ? ? ? “We need a framework, or industry standard, or best practices!”

320. Let’s try Component Teams… Perishable Frozen Dry Goods Other RequirementsGathering ProgramManagement ? ? ? ? ? ? ? “We need a framework, or industry standard, or best practices!”

321. Let’s try Component Teams… Grains Dairy Meats Produce RequirementsGathering ProgramManagement

325. Evolution Path Single Person Single Team Mob Functional Teams Component Teams Meal Teams

326. People want whole meals! Grains Dairy Meats Produce RequirementsGathering ProgramManagement

327. People want whole meals! Grains Dairy Meats Produce RequirementsGathering ProgramManagement Breakfast

328. People want whole meals! Grains Dairy Meats Produce RequirementsGathering ProgramManagement Breakfast Lunch

329. People want whole meals! Grains Dairy Meats Produce RequirementsGathering ProgramManagement Breakfast Lunch Dinner

330. People want whole meals! Grains Dairy Meats Produce RequirementsGathering ProgramManagement Breakfast Lunch Dinner Snacks

331. What’s the answer? Single Person Single Team Mob Functional Teams Component Teams Meal Teams

333. What’s the answer?

335. What’s the answer? What do we want?Single Person Single Team Mob Functional Teams Component Teams Meal Teams

336. What’s the answer? What do we want? • A “one-stop shop” – a single Point of Service – for our customers. Single Person Single Team Mob Functional Teams Component Teams Meal Teams

337. What’s the answer? What do we want? • A “one-stop shop” – a single Point of Service – for our customers. • Each customer’s wait in queue to be minimal Single Person Single Team Mob Functional Teams Component Teams Meal Teams

338. What’s the answer? What do we want? • A “one-stop shop” – a single Point of Service – for our customers. • Each customer’s wait in queue to be minimal • Each customer to be serviced as quickly as possible when they get to the head of the line. Single Person Single Team Mob Functional Teams Component Teams Meal Teams

339. What’s the answer? What do we want? • A “one-stop shop” – a single Point of Service – for our customers. • Each customer’s wait in queue to be minimal • Each customer to be serviced as quickly as possible when they get to the head of the line. Single Person Single Team Mob Functional Teams Component Teams Meal Teams

340. What’s the answer? What do we want? • A “one-stop shop” – a single Point of Service – for our customers. • Each customer’s wait in queue to be minimal • Each customer to be serviced as quickly as possible when they get to the head of the line. Single Person Single Team Mob Functional Teams Component Teams Meal Teams Multiple, Equivalent Teams

341. Let’s try this again…

342. Let’s try this again… Check out

351. Let’s try this again… Check out Check out

352. Let’s try this again… Check out Check out Check out

353. Let’s try this again… Check out Check out Check out • Providing a one- stop Point of Service, we’ve minimized the processing time to provide the service.

354. Let’s try this again… Check out Check out Check out • Providing a one- stop Point of Service, we’ve minimized the processing time to provide the service.

355. Let’s try this again… Check out Check out Check out • Providing a one- stop Point of Service, we’ve minimized the processing time to provide the service. • Scaling by providing multiple, equivalent POSs

356. But… Check out Check out Check out

368. But… Check out Check out Check out ! ! ! !

369. But… Check out Check out Check out • We still need to minimize the amount of time spent in queue. ! ! ! !

370. But… Check out Check out Check out • We still need to minimize the amount of time spent in queue. • Customers bear the risk of getting in the wrong queue. ! ! ! !

371. But… Check out Check out Check out • We still need to minimize the amount of time spent in queue. • Customers bear the risk of getting in the wrong queue. • Each POS does not require its own queue. ! ! ! !

372. We can do better… Check out Check out Check out

385. We can do better… Check out Check out Check out • By having a single queue, we ensure that every customer gets handled by the next available point of service – thus minimizing average time in queue.

386. We can do better… Check out Check out Check out • By having a single queue, we ensure that every customer gets handled by the next available point of service – thus minimizing average time in queue.

387. Hang on a minute…! Check out Check out Check Out

388. Hang on a minute…! Check out Check out Check Out

389. Hang on a minute…! Check out Check out Check Out< 10 Items

390. Hang on a minute…! Check out Check out Check Out • The Points of Service are still equivalent. < 10 Items

391. Hang on a minute…! Check out Check out Check Out • The Points of Service are still equivalent. • We’ve made a business decision about certain classes of customers or requests. < 10 Items

392. Hang on a minute…! Check out Check out Check Out • The Points of Service are still equivalent. • We’ve made a business decision about certain classes of customers or requests. • Classes of Service are a Prioritization mechanism. < 10 Items

393. Hang on a minute…! Check out Check out Check Out • The Points of Service are still equivalent. • We’ve made a business decision about certain classes of customers or requests. • Classes of Service are a Prioritization mechanism. • Teams can be re-allocated extremely easily between Classes of Service. < 10 Items

394. Back to Software!

395. What have we learned?

396. 1. Dependencies are evil; eliminate as many as possible. What have we learned?

397. 1. Dependencies are evil; eliminate as many as possible. 2. Encapsulate the rest into a single Point of Service – forming a “one-stop shop” for the customer. What have we learned?

398. 1. Dependencies are evil; eliminate as many as possible. 2. Encapsulate the rest into a single Point of Service – forming a “one-stop shop” for the customer. 3. Scale by replicating equivalent Points of Service. What have we learned?

399. 1. Dependencies are evil; eliminate as many as possible. 2. Encapsulate the rest into a single Point of Service – forming a “one-stop shop” for the customer. 3. Scale by replicating equivalent Points of Service. 4. Minimize customers’ risk of delay by having a single Queue for the multiple Points of Service. What have we learned?

400. 1. Dependencies are evil; eliminate as many as possible. 2. Encapsulate the rest into a single Point of Service – forming a “one-stop shop” for the customer. 3. Scale by replicating equivalent Points of Service. 4. Minimize customers’ risk of delay by having a single Queue for the multiple Points of Service. 5. Classes of Service are OK – in fact, they’re great. What have we learned?

401. But What Does it Look Like?

402. One-Stop Teams Web </> 

403. Multiple, Equivalent Teams </>  Team A </>  Team B </>  Team C </>  Team D

404. Single Product Backlog </>  Team A </>  Team B </>  Team C </>  Team D Product Backlog 1. User Story 1 2. User Story 2 3. User Story 3 4. User Story 4 5. User Story 5 6. User Story 6 7. User Story 7 8. User Story 8 9. User Story 9 10.User Story 10 11.User Story 11 12.User Story 12 13.Epic A …

405. Classes of Service </>  Team A </>  Team B </>  Team C </>  Team D Product Backlog --Urgent-- 1. User Story 1 2. User Story 2 --Standard-- 3. User Story 3 4. User Story 4 5. User Story 5 6. User Story 6 7. User Story 7 8. User Story 8 9. User Story 9 10.User Story 10 11.User Story 11 12.User Story 12 13.Epic A …

406. Yeah, but…

407. • “This will be chaos!” Yeah, but…

408. • “This will be chaos!” • You’ll almost never be in a situation to have every single skill set on every single team. Yeah, but…

409. • “This will be chaos!” • You’ll almost never be in a situation to have every single skill set on every single team. • How do the multiple teams coordinate? Yeah, but…

410. • “This will be chaos!” • You’ll almost never be in a situation to have every single skill set on every single team. • How do the multiple teams coordinate? • Who grooms? Yeah, but…

411. • “This will be chaos!” • You’ll almost never be in a situation to have every single skill set on every single team. • How do the multiple teams coordinate? • Who grooms? • Who sizes? Yeah, but…

412. • “This will be chaos!” • You’ll almost never be in a situation to have every single skill set on every single team. • How do the multiple teams coordinate? • Who grooms? • Who sizes? • How do we inspect and adapt? Yeah, but…

413. “This will be chaos!”

414. “This will be chaos!” Branching

417. “This will be chaos!” Technical Debt Branching

420. “This will be chaos!” </>  Team A </>  Team B </>  Team C </>  Team D

451. “This will be chaos!” </>  Team A </>  Team B </>  Team C </>  Team D Database Community of Practice

452. “This will be chaos!” </>  Team A </>  Team B </>  Team C </>  Team D </>  System / Function Guardians Distinct from the teams

453. “This will be chaos!” </>  Team A </>  Team B </>  Team C </>  Team D </>  System / Function Guardians embedded on the teams

455. Skill Sets for Every Team… </>  Team A </>  Team B </>  Team C </>  Team D </>  Travelers aka Internal Consultants

456. Skill Sets for Every Team… </>  Team A </>  Team B </>  Team C </>  Team D </>  Travelers aka Internal Consultants 100% dedicated to a team

457. Skill Sets for Every Team… </>  Team A </>  Team B </>  Team C </>  Team D </>  Travelers aka Internal Consultants 100% dedicated to a team temporarily

458. Coordination

459. Coordination OverallBacklogRefinement Team Reps Team Reps Team Reps PO

460. Coordination

461. Coordination

462. Coordination

463. Coordination

464. Coordination Backlog Refinement BacklogRefinement Team Team Team

465. Coordination

466. Coordination

467. Coordination

468. Coordination

469. Coordination SprintPlanning1 Team Reps Team Reps Team Reps PO

470. Coordination

471. Coordination

472. Coordination

473. Coordination

474. Coordination Sprint PlanningII SprintPlanningII Team Team Team

475. Coordination

476. Coordination

477. Coordination

478. Coordination

479. Coordination Sprint Team Sprint Team Sprint Team

480. Coordination

481. Coordination

482. Coordination

483. Coordination

484. Coordination Retro Team Retro Team Retro Team

485. Coordination

486. Coordination

487. Coordination

488. Coordination

489. Coordination OverallRetro Team Reps Team Reps Team Reps PO

490. Coordination OverallBacklogRefinement Team Reps Team Reps Team Reps PO OverallRetro Team Reps Team Reps Team Reps PO

494. Coordination Backlog Refinement BacklogRefinement Team Team Team OverallBacklogRefinement Team Reps Team Reps Team Reps PO OverallRetro Team Reps Team Reps Team Reps PO

498. Coordination Backlog Refinement BacklogRefinement Team Team Team SprintPlanning1 Team Reps Team Reps Team Reps PO OverallBacklogRefinement Team Reps Team Reps Team Reps PO OverallRetro Team Reps Team Reps Team Reps PO

502. Coordination Backlog Refinement BacklogRefinement Team Team Team SprintPlanning1 Team Reps Team Reps Team Reps PO OverallBacklogRefinement Team Reps Team Reps Team Reps PO Sprint PlanningII SprintPlanningII Team Team Team OverallRetro Team Reps Team Reps Team Reps PO

506. Coordination Backlog Refinement BacklogRefinement Team Team Team SprintPlanning1 Team Reps Team Reps Team Reps PO OverallBacklogRefinement Team Reps Team Reps Team Reps PO Sprint PlanningII SprintPlanningII Team Team Team OverallRetro Team Reps Team Reps Team Reps PO Sprint Team Sprint Team Sprint Team

510. Coordination Backlog Refinement BacklogRefinement Team Team Team SprintPlanning1 Team Reps Team Reps Team Reps PO OverallBacklogRefinement Team Reps Team Reps Team Reps PO Sprint PlanningII SprintPlanningII Team Team Team OverallRetro Team Reps Team Reps Team Reps PO Retro Team Retro Team Retro Team Sprint Team Sprint Team Sprint Team

518. Let’s Wrap Up…

519. Multi-Team Organizations

520. • One-Stop teams with T-shaped skills Multi-Team Organizations

521. • One-Stop teams with T-shaped skills • Multiple, equivalent Points of Service Multi-Team Organizations

522. • One-Stop teams with T-shaped skills • Multiple, equivalent Points of Service • Single Queue Multi-Team Organizations

523. • One-Stop teams with T-shaped skills • Multiple, equivalent Points of Service • Single Queue • DevOps Multi-Team Organizations

524. • One-Stop teams with T-shaped skills • Multiple, equivalent Points of Service • Single Queue • DevOps • Communities of Practice, System Guardians, Travelers Multi-Team Organizations

525. • One-Stop teams with T-shaped skills • Multiple, equivalent Points of Service • Single Queue • DevOps • Communities of Practice, System Guardians, Travelers • Lightweight Coordination Multi-Team Organizations

526. Principles of Product Development Flow by Don Reinertsen Scaling Lean & Agile Development by Craig Larman and Bos Vodde Essential Scrum by Ken Rubin Resources

527. ken.furlong@excella.com http://www.excella.com http://www.linkedin.com/in/kenfurlong Ken Furlong

528. Thank You!

2015 10 How to Structure Multi-Team Organizations

Recommended

Recommended

More Related Content

Recently uploaded

Recently uploaded (20)

Featured

Featured (20)

2015 10 How to Structure Multi-Team Organizations