Slide 1

Slide 1 text

# p r d c d e l i v e r | O c t . 1 1 , 2 0 1 7 THE SERVICE-DELIVERY REVIEW The Missing Agile Feedback Loop

Slide 2

Slide 2 text

@mattphilip #prdcdeliver A TALE OF TWO CITIES Legendary 
 Hockey Families Water Clarity Motto Winnipeg St. Louis “Gateway to the West” Hull + 
 Steen Muddy French Language Bastardized by English Bastardized by Germans Bobby Thomas Brett Alexander

Slide 3

Slide 3 text

@mattphilip #prdcdeliver WHAT’S YOUR FAVORITE PART?

Slide 4

Slide 4 text

@mattphilip #prdcdeliver WHAT’S YOUR FAVORITE PART?

Slide 5

Slide 5 text

WHAT'S THE PROBLEM?

Slide 6

Slide 6 text

@mattphilip #prdcdeliver HOW WOULD YOU ANSWER?

Slide 7

Slide 7 text

@mattphilip #prdcdeliver IS THIS SATISFACTORY?

Slide 8

Slide 8 text

@mattphilip #prdcdeliver DELIVERY CONCERNS Service Product Team 
 (Internal) Customer (External) Viewpoint Component

Slide 9

Slide 9 text

@mattphilip #prdcdeliver FEEDBACK NEEDS Is our 
 team 
 healthy? Is our 
 service delivery fit for its purpose? Is our 
 product 
 healthy? Is our 
 product
 fit for its purpose? Service Product Customer 
 (Build right thing) Team 
 (Build thing right)

Slide 10

Slide 10 text

@mattphilip #prdcdeliver FEEDBACK LOOPS ? ? ? ? Service Product Customer 
 (Build right thing) Team 
 (Build thing right)

Slide 11

Slide 11 text

@mattphilip #prdcdeliver FEEDBACK LOOPS Retrospective ? ? ? Service Product Customer 
 (Build right thing) Team 
 (Build thing right)

Slide 12

Slide 12 text

@mattphilip #prdcdeliver FEEDBACK LOOPS Retrospective ? ■ Automated build/tests ■ Code metrics ■ Performance monitors ? Service Product Customer 
 (Build right thing) Team 
 (Build thing right)

Slide 13

Slide 13 text

@mattphilip #prdcdeliver FEEDBACK LOOPS Retrospective ? ■ Automated build/tests ■ Code metrics ■ Performance monitors ■ Demo ■ Usage metrics ■ Money! Service Product Customer 
 (Build right thing) Team 
 (Build thing right)

Slide 14

Slide 14 text

@mattphilip #prdcdeliver FEEDBACK LOOPS Retrospective ? ■ Automated build/tests ■ Code metrics ■ Performance monitors ■ Demo ■ Usage metrics ■ Money! Service Product Customer 
 (Build right thing) Team 
 (Build thing right)

Slide 15

Slide 15 text

@mattphilip #prdcdeliver A POSSIBLE SOLUTION Retrospective Service- Delivery Review ■ Automated build/tests ■ Code metrics ■ Performance monitors ■ Demo ■ Usage metrics ■ Money! Service Product Customer 
 (Build right thing) Team 
 (Build thing right)

Slide 16

Slide 16 text

SERVICE-DELIVERY REVIEW

Slide 17

Slide 17 text

@mattphilip #prdcdeliver A regular, quantitatively-oriented discussion between a customer and delivery team about the fitness for purpose of its service delivery.

Slide 18

Slide 18 text

@mattphilip #prdcdeliver 7 KANBAN CADENCES

Slide 19

Slide 19 text

@mattphilip #prdcdeliver WHO SHOULD ATTEND?

Slide 20

Slide 20 text

@mattphilip #prdcdeliver TOPICS (“IS OUR SERVICE FIT FOR ITS PURPOSE?”) ▫︎Delivery times (aka Cycle/Lead/Time-in-Process) of recent work and tail length in distribution ▫︎Blocker-clustering results and remediations ▫︎Work-type mix (% allocation to work types) ▫︎Classes of service/expectations of each work type ▫︎Value-demand ratio (value-add or failure demand) ▫︎Due-date performance (fixed-date misses) ▫︎Policy changes ▫︎Results of fitness surveys (e.g., F4P Box Score) ▫︎“What obstacles stand in the way of our service- delivery expectations?”

Slide 21

Slide 21 text

@mattphilip #prdcdeliver FEEDBACK METRICS ■ Team health ■ Engagement ■ Flow efficiency ■ Delivery time distribution ■ Throughput ■ Due-date performance ■ Mean time to restore ■ Code health ■ Performance ■ Revenue ■ Usage metrics ■ App-store rating Service Product Customer 
 (Build right thing) Team 
 (Build thing right)

Slide 22

Slide 22 text

SERVICE-DELIVERY REVIEW CANVAS FITNESS CRITERIA METRICS What does our customer value about our service? e.g. Predictable delivery, quality, delivery-time expectation at 85th% Delivery Team (single kanban): SERVICES WE PROVIDE Which service requests / work items types do we accept? What are the service level expectations of each work item type? PARTICIPANTS IN REVIEW E.g., Flow manager, coach, exec sponsor, Product owner, customer(s), external stakeholders, delivery team reps
 INPUTS OUTPUTS DUE-DATE PERFORMANCE How well did we do with on-time delivery of fixed-date items? EXPEDITE PERFORMANCE How well did we do with on-time delivery of expedite items? STANDARD-URGENCY PERFORMANCE How well did we do with on-time delivery of expedite items? Service-level expectation: 85th percentile: 50th percentile: BLOCKER CLUSTERS Express largest clusters by type, count and total days blocked ACHIEVEMENTS AND SHORTFALLS VS. EXPECTATIONS OPTIONS TO REDUCE RISK Or system-design changes to improve capability vs. expectations (e.g., reduce WIP) FORECAST Based on delivery times, our expectation that we will complete remaining work IMPROVEMENT HYPOTHESES We believe that will result in and we’ll know because of Date: “Is our service delivery fit for its purpose according to our customer?”

Slide 23

Slide 23 text

@mattphilip #prdcdeliver DELIVERY-TIME SCATTERPLOT

Slide 24

Slide 24 text

@mattphilip #prdcdeliver DELIVERY-TIME HISTOGRAM

Slide 25

Slide 25 text

@mattphilip #prdcdeliver FLOW-EFFICIENCY TREND

Slide 26

Slide 26 text

@mattphilip #prdcdeliver VALUE-DEMAND RATIO 0% 25% 50% 75% 100% 7-Jan 14-Jan 21-Jan 28-Jan 4-Feb 11-Feb 18-Feb 25-Feb 4-M ar 11-M ar 18-M ar 25-M ar 1-Apr

Slide 27

Slide 27 text

@mattphilip #prdcdeliver PROBABILISTIC FORECAST

Slide 28

Slide 28 text

@mattphilip #prdcdeliver AGING WORK IN PROGRESS

Slide 29

Slide 29 text

@mattphilip #prdcdeliver BENEFITS OF A SERVICE-DELIVERY REVIEW ▫︎Forces you to focus on customers and become fit for the purpose for which they chose you ▫︎Sets clear standards ▫︎Generates feedback with (meaningful) data ▫︎Forces you to understand why you fail and align improvement efforts ▫︎Builds customer trust and loyalty ▫︎Gives employees greater sense of achievement

Slide 30

Slide 30 text

@mattphilip #prdcdeliver Delighting customers 
 doesn’t build loyalty; 
 reducing their effort—
 the work they must do 
 to get their problem solved
 —does.

Slide 31

Slide 31 text

@mattphilip #prdcdeliver TAKEAWAYS FOR NEXT MONDAY ▫︎Identify and involve your customer ▫︎Ask the “fitness” question (What do you value…?) ▫︎Discover your services ▫︎Establish service-delivery expectations ▫︎Keep doing the other useful feedback loops ▫︎Reduce/combine meetings rather than add new ▫︎Consider as way to measure “agile adoption”

Slide 32

Slide 32 text

@mattphilip #prdcdeliver REFERENCES AND FURTHER EXPLORATION ▫︎ http://www.djaa.com/kanban-cadences ▫︎ https://www.slideshare.net/agilemanager/kanban-cadences- information-flow ▫︎ https://mattphilip.wordpress.com/2017/05/24/service-delivery- review-the-missing-agile-feedback-loop/ ▫︎ When will it be done? by Dan Vacanti (https://leanpub.com/ whenwillitbedone) ▫︎ http://kanbanize.com/ ▫︎ https://actionableagile.com/ ▫︎ https://hbr.org/1988/07/the-power-of-unconditional-service- guarantees ▫︎ http://www.icmi.com/Resources/Customer-Experience/2015/10/ Ten-Customer-Expectations-and-How-They-Are-Changing ▫︎ https://hbr.org/2010/07/stop-trying-to-delight-your-customers

Slide 33

Slide 33 text

@mattphilip #prdcdeliver Questions? THANK YOU