Downloaded 11 times
Uploaded byExcella
How to Structure Multi Team Organizations
The document discusses the evolution of organizational structures, starting from single-person teams to complex multi-team setups, highlighting the need for functional and component teams. It emphasizes the challenges and dependencies faced during this evolution, along with the importance of t-shaped skills and effective team dynamics. The text also touches on instincts that can hinder progress and the necessity for adaptability in organizational design.
More Related Content
How to Structure Multi Team Organizations
- 1. How to Structure Multi-TeamOrganizations Ken Furlong
- 2. The evolution ofan organizational structure
- 3.
- 4. In the Beginning… SinglePerson
- 5. In the Beginning… SinglePerson
- 6. In the Beginning… SinglePerson
- 7. In the Beginning… SinglePerson
- 8. In the Beginning… SinglePerson Single Team
- 9. In the Beginning… SinglePerson Single Team
- 10. In the Beginning… SinglePerson Single Team
- 11. In the Beginning… SinglePerson Single Team
- 12. In the Beginning… SinglePerson Single Team
- 13. In the Beginning… SinglePerson Single Team
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65.
- 66.
- 67. How do weevolve? Single Person Single Team Mob ?
- 68. How do weevolve? Single Person Single Team Mob ?
- 69. How do weevolve? Single Person Single Team Mob ?
- 70. How do weevolve? Single Person Single Team Mob ?Functional Teams
- 71. How do weevolve? Single Person Single Team Mob Functional Teams
- 72. How do weevolve? Single Person Single Team Mob Functional Teams
- 73. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 74. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 75. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 76. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 77. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 78. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 79. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 80. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 81. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 82. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 83. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 84. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 85. How do weevolve? Single Person Single Team Mob Functional Teams </>
- 86. How do weevolve? Single Person Single Team Mob Functional Teams </> Component Teams
- 87. How do weevolve? Single Person Single Team Mob Functional Teams Component Teams
- 88. How do weevolve? Single Person Single Team Mob Functional Teams Component Teams
- 89. How do weevolve? Single Person Single Team Mob Functional Teams Component Teams
- 90. How do weevolve? Single Person Single Team Mob Functional Teams Component Teams
- 91. How do weevolve? Single Person Single Team Mob Functional Teams Component Teams
- 92. How do weevolve? Single Person Single Team Mob Functional Teams Component Teams
- 93. How do weevolve? Single Person Single Team Mob Functional Teams Component Teams
- 94. How do weevolve? Single Person Single Team Mob Functional Teams Web Component Teams
- 95. How do weevolve? Single Person Single Team Mob Functional Teams Web Component Teams
- 96. How do weevolve? Single Person Single Team Mob Functional Teams Web Component Teams
- 97. How do weevolve? Single Person Single Team Mob Functional Teams Web Component Teams
- 98. How do weevolve? Single Person Single Team Mob Functional Teams Web Component Teams
- 99.
- 100.
- 101.
- 102.
- 103.
- 104.
- 105.
- 106.
- 107.
- 108.
- 109.
- 110.
- 111.
- 112.
- 113.
- 114.
- 115.
- 116.
- 117.
- 118.
- 119.
- 120.
- 121.
- 122.
- 123.
- 124.
- 125.
- 126.
- 127.
- 128.
- 129.
- 130.
- 131.
- 132.
- 133.
- 134.
- 135.
- 136.
- 137.
- 138.
- 139.
- 140.
- 141. “Feature” Teams Single Person SingleTeam Mob Functional Teams Web Component Teams
- 142. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams
- 143. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams
- 144. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams
- 145. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams
- 146. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams
- 147. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams
- 148. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams
- 149. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams
- 150. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams </>
- 151. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams </> </>
- 152. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams </> </> </>
- 153. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams </> </> </> </>
- 154. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams </> </> </> </> </>
- 155. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams </> </> </> </> </> </>
- 156. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams </> </> </> </> </> </>
- 157. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams </> </> </> </> </> </>
- 158. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams </> </> </> </> </> </>
- 159. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams </> </> </> </> </> </>
- 160. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams </> </> </> </> </> </>
- 161. “Feature” Teams Single Person SingleTeam Mob Functional Teams Component Teams Feature Teams </> </> </> </> </> </>
- 162.
- 163.
- 164.
- 165.
- 166.
- 167.
- 168.
- 169.
- 170.
- 171.
- 172. Encapsulation </> 9 1011 12 1 2 3 4
- 173.
- 174.
- 175.
- 176.
- 177.
- 178.
- 179.
- 180.
- 181.
- 182.
- 183.
- 184.
- 185.
- 186.
- 187.
- 188.
- 189.
- 190.
- 191.
- 192.
- 193.
- 194.
- 195.
- 196.
- 197.
- 198.
- 199.
- 200.
- 201.
- 202.
- 203.
- 204.
- 205.
- 206.
- 207.
- 208.
- 209.
- 210.
- 211.
- 212.
- 213.
- 214.
- 215.
- 216.
- 217.
- 218.
- 219.
- 220.
- 221.
- 222.
- 223.
- 224. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams </> </> </> </> </> </>
- 225. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams </> </> </> </> </>
- 226. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams </> </> Search </> </> </>
- 227. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams </> </> Search </> </>
- 228. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams </> </> Search Digital Content </> </>
- 229. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams </> Search Digital Content </> </>
- 230. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart </> Search Digital Content </> </>
- 231. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Search Digital Content </> </>
- 232. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content </> </>
- 233. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content </>
- 234. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations </>
- 235. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations
- 236. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 237. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 238. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 239. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 240. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 241. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 242. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 243. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 244. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 245. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 246. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 247. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 248. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 249. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 250. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 251. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Feature Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 252. Instincts Get inthe Way… Single Person Single Team Mob Functional Teams Component Teams Cart Pay- ments Search Digital Content Recommendations Admin Console
- 253. Instincts Get inthe 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 wego wrong? Single Person Single Team Mob Functional Teams Component Teams Categorized Feature Teams
- 255. Where did wego wrong? Single Person Single Team Mob Functional Teams Component Teams Categorized Feature Teams
- 256. Let’s take atrip…
- 257. Let’s take atrip… We need some groceries.
- 258. We need somegroceries… Check out
- 259. We need somegroceries… Check out
- 260. We need somegroceries… Check out
- 261. We need somegroceries… Check out
- 262. We need somegroceries… Check out
- 263. We need somegroceries… Check out
- 264. We need somegroceries… Check out
- 265. We need somegroceries… Check out
- 266. We need somegroceries… Check out
- 267.
- 268.
- 269.
- 270.
- 271.
- 272. Evolution Path Single Person SingleTeam Mob Functional Teams
- 273. Let’s try FunctionalTeams… Check out
- 274. Let’s try FunctionalTeams… Checkout Bagging
- 275. Let’s try FunctionalTeams… Checkout Bagging
- 276. Let’s try FunctionalTeams… Checkout Bagging
- 277. Let’s try FunctionalTeams… Checkout Bagging
- 278. Let’s try FunctionalTeams… Checkout Bagging
- 279. Let’s try FunctionalTeams… Checkout Bagging
- 280. Let’s try FunctionalTeams… Checkout Bagging
- 281. Let’s try FunctionalTeams… Checkout Bagging
- 282. Let’s try FunctionalTeams… Checkout Bagging
- 283. Let’s try FunctionalTeams… Checkout Bagging
- 284. Let’s try FunctionalTeams… Checkout Bagging
- 285. Let’s try FunctionalTeams… Checkout Bagging
- 286. Let’s try FunctionalTeams… Checkout Bagging
- 287. Let’s try FunctionalTeams… Checkout Bagging
- 288. Let’s try FunctionalTeams… Checkout Bagging
- 289. Let’s try FunctionalTeams… Checkout Bagging
- 290. Let’s try FunctionalTeams… Checkout Bagging
- 291. Evolution Path Single Person SingleTeam Mob Functional Teams
- 292. Evolution Path Single Person SingleTeam Mob Functional Teams
- 293. Evolution Path Single Person SingleTeam Mob Functional Teams
- 294. Evolution Path Single Person SingleTeam Mob Functional Teams Component Teams
- 295. Let’s try ComponentTeams…
- 296. Let’s try ComponentTeams… Dry Goods
- 297. Let’s try ComponentTeams… Frozen Dry Goods
- 298. Let’s try ComponentTeams… Perishable Frozen Dry Goods
- 299. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other
- 300. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other
- 301. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other
- 302. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other
- 303. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other
- 304. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other
- 305. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other
- 306. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other
- 307. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other ?
- 308. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other ? ?
- 309. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other ? ? ?
- 310. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other ? ? ? ?
- 311. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other ? ? ? ? ?
- 312. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other ? ? ? ? ? ?
- 313. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other ? ? ? ? ? ? ?
- 314. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other ? ? ? ? ? ? ?
- 315. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other ? ? ? ? ? ? ?
- 316. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other RequirementsGathering ? ? ? ? ? ? ?
- 317. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other RequirementsGathering ProgramManagement ? ? ? ? ? ? ?
- 318. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other RequirementsGathering ProgramManagement ? ? ? ? ? ? ?
- 319. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other RequirementsGathering ProgramManagement ? ? ? ? ? ? ? “We need a framework, or industry standard, or best practices!”
- 320. Let’s try ComponentTeams… Perishable Frozen Dry Goods Other RequirementsGathering ProgramManagement ? ? ? ? ? ? ? “We need a framework, or industry standard, or best practices!”
- 321. Let’s try ComponentTeams… Grains Dairy Meats Produce RequirementsGathering ProgramManagement
- 322. Evolution Path Single Person SingleTeam Mob Functional Teams Component Teams
- 323. Evolution Path Single Person SingleTeam Mob Functional Teams Component Teams
- 324. Evolution Path Single Person SingleTeam Mob Functional Teams Component Teams
- 325. Evolution Path Single Person SingleTeam Mob Functional Teams Component Teams Meal Teams
- 326. People want wholemeals! Grains Dairy Meats Produce RequirementsGathering ProgramManagement
- 327. People want wholemeals! Grains Dairy Meats Produce RequirementsGathering ProgramManagement Breakfast
- 328. People want wholemeals! Grains Dairy Meats Produce RequirementsGathering ProgramManagement Breakfast Lunch
- 329. People want wholemeals! Grains Dairy Meats Produce RequirementsGathering ProgramManagement Breakfast Lunch Dinner
- 330. People want wholemeals! Grains Dairy Meats Produce RequirementsGathering ProgramManagement Breakfast Lunch Dinner Snacks
- 331. What’s the answer? SinglePerson Single Team Mob Functional Teams Component Teams Meal Teams
- 332. What’s the answer? SinglePerson Single Team Mob Functional Teams Component Teams Meal Teams
- 333.
- 334. What’s the answer? SinglePerson Single Team Mob Functional Teams Component Teams Meal Teams
- 335. What’s the answer? Whatdo we want?Single Person Single Team Mob Functional Teams Component Teams Meal Teams
- 336. What’s the answer? Whatdo 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? Whatdo 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? Whatdo 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? Whatdo 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? Whatdo 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 thisagain…
- 342. Let’s try thisagain… Check out
- 343. Let’s try thisagain… Check out
- 344. Let’s try thisagain… Check out
- 345. Let’s try thisagain… Check out
- 346. Let’s try thisagain… Check out
- 347. Let’s try thisagain… Check out
- 348. Let’s try thisagain… Check out
- 349. Let’s try thisagain… Check out
- 350. Let’s try thisagain… Check out
- 351. Let’s try thisagain… Check out Check out
- 352. Let’s try thisagain… Check out Check out Check out
- 353. Let’s try thisagain… 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 thisagain… 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 thisagain… 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.
- 357.
- 358.
- 359.
- 360.
- 361.
- 362.
- 363.
- 364.
- 365.
- 366.
- 367.
- 368. But… Check out Check out Checkout ! ! ! !
- 369. But… Check out Check out Checkout • We still need to minimize the amount of time spent in queue. ! ! ! !
- 370. But… Check out Check out Checkout • 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 Checkout • 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 dobetter… Check out Check out Check out
- 373. We can dobetter… Check out Check out Check out
- 374. We can dobetter… Check out Check out Check out
- 375. We can dobetter… Check out Check out Check out
- 376. We can dobetter… Check out Check out Check out
- 377. We can dobetter… Check out Check out Check out
- 378. We can dobetter… Check out Check out Check out
- 379. We can dobetter… Check out Check out Check out
- 380. We can dobetter… Check out Check out Check out
- 381. We can dobetter… Check out Check out Check out
- 382. We can dobetter… Check out Check out Check out
- 383. We can dobetter… Check out Check out Check out
- 384. We can dobetter… Check out Check out Check out
- 385. We can dobetter… 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 dobetter… 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 aminute…! Check out Check out Check Out
- 388. Hang on aminute…! Check out Check out Check Out
- 389. Hang on aminute…! Check out Check out Check Out< 10 Items
- 390. Hang on aminute…! Check out Check out Check Out • The Points of Service are still equivalent. < 10 Items
- 391. Hang on aminute…! 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 aminute…! 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 aminute…! 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.
- 395. What have welearned?
- 396. 1. Dependencies areevil; eliminate as many as possible. What have we learned?
- 397. 1. Dependencies areevil; 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 areevil; 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 areevil; 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 areevil; 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 Doesit Look Like?
- 402.
- 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.
- 407. • “This willbe chaos!” Yeah, but…
- 408. • “This willbe chaos!” • You’ll almost never be in a situation to have every single skill set on every single team. Yeah, but…
- 409. • “This willbe 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 willbe 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 willbe 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 willbe 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 bechaos!”
- 414. “This will bechaos!” Branching
- 415. “This will bechaos!” Branching
- 416. “This will bechaos!” Branching
- 417. “This will bechaos!” Technical Debt Branching
- 418. “This will bechaos!” Technical Debt Branching
- 419. “This will bechaos!” Technical Debt Branching
- 420. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 421. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 422. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 423. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 424. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 425. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 426. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 427. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 428. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 429. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 430. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 431. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 432. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 433. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 434. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 435. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 436. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 437. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 438. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 439. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 440. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 441. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 442. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 443. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 444. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 445. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 446. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 447. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 448. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 449. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 450. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 451. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D Database Community of Practice
- 452. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D </> System / Function Guardians Distinct from the teams
- 453. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D </> System / Function Guardians embedded on the teams
- 454. “This will bechaos!” </> Team A </> Team B </> Team C </> Team D
- 455. Skill Sets forEvery Team… </> Team A </> Team B </> Team C </> Team D </> Travelers aka Internal Consultants
- 456. Skill Sets forEvery Team… </> Team A </> Team B </> Team C </> Team D </> Travelers aka Internal Consultants 100% dedicated to a team
- 457. Skill Sets forEvery Team… </> Team A </> Team B </> Team C </> Team D </> Travelers aka Internal Consultants 100% dedicated to a team temporarily
- 458.
- 459.
- 460.
- 461.
- 462.
- 463.
- 464.
- 465.
- 466.
- 467.
- 468.
- 469.
- 470.
- 471.
- 472.
- 473.
- 474.
- 475.
- 476.
- 477.
- 478.
- 479.
- 480.
- 481.
- 482.
- 483.
- 484.
- 485.
- 486.
- 487.
- 488.
- 489.
- 490.
- 491.
- 492.
- 493.
- 494.
- 495.
- 496.
- 497.
- 498.
- 499.
- 500.
- 501.
- 502.
- 503.
- 504.
- 505.
- 506.
- 507.
- 508.
- 509.
- 510.
- 511.
- 512.
- 513.
- 514.
- 515.
- 516.
- 517.
- 518.
- 519.
- 520. • One-Stop teamswith T-shaped skills Multi-Team Organizations
- 521. • One-Stop teamswith T-shaped skills • Multiple, equivalent Points of Service Multi-Team Organizations
- 522. • One-Stop teamswith T-shaped skills • Multiple, equivalent Points of Service • Single Queue Multi-Team Organizations
- 523. • One-Stop teamswith T-shaped skills • Multiple, equivalent Points of Service • Single Queue • DevOps Multi-Team Organizations
- 524. • One-Stop teamswith T-shaped skills • Multiple, equivalent Points of Service • Single Queue • DevOps • Communities of Practice, System Guardians, Travelers Multi-Team Organizations
- 525. • One-Stop teamswith 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 ProductDevelopment Flow by Don Reinertsen Scaling Lean & Agile Development by Craig Larman and Bos Vodde Essential Scrum by Ken Rubin Resources
- 527.
- 528.