An exploration of several common patterns in organizational design, their failure modes, an alternative approach, and several mechanics to enable success
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
237. 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
238. 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
239. 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
240. 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
241. 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
242. 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
243. 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
244. 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
245. 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
246. 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
247. 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
248. 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
249. 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
250. 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
251. 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
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!”
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
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
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
373. We can do better…
Check out
Check out
Check out
374. We can do better…
Check out
Check out
Check out
375. We can do better…
Check out
Check out
Check out
376. We can do better…
Check out
Check out
Check out
377. We can do better…
Check out
Check out
Check out
378. We can do better…
Check out
Check out
Check out
379. We can do better…
Check out
Check out
Check out
380. We can do better…
Check out
Check out
Check out
381. We can do better…
Check out
Check out
Check out
382. We can do better…
Check out
Check out
Check out
383. We can do better…
Check out
Check out
Check out
384. 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
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?
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
…
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…
420. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
421. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
422. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
423. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
424. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
425. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
426. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
427. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
428. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
429. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
430. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
431. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
432. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
433. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
434. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
435. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
436. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
437. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
438. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
439. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
440. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
441. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
442. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
443. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
444. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
445. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
446. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
447. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
448. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
449. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
450. “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
454. “This will be chaos!”
</>
Team A
</>
Team B
</>
Team C
</>
Team D
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
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