Support and Initiate a DevOps Transformation

102,589 views

Published on

Slides to Damon Edwards keynote at DevOps Days Silicon Valley 2013

Published in: Technology, Business
2 Comments
22 Likes
Statistics
Notes
  • Why is phase 2 always the problem?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • My dear, How are you today? i will like to be your friend My name is Sheikha Ghunaim , am a 43 years old divorcee. Please write to me in my email ( sheikhaghunaim2@hotmail.com ). im honest and open mind single woman. im going to tell more when i see your response. Regards Sheikha.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
102,589
On SlideShare
0
From Embeds
0
Number of Embeds
92,499
Actions
Shares
0
Downloads
346
Comments
2
Likes
22
Embeds 0
No embeds

No notes for slide

Support and Initiate a DevOps Transformation

  1. 1. Leading the Horses to Drink A Practical Guide to Initiating and Supporting a DevOps Transformation DEVOPS DAYS Damon Edwards
  2. 2. Damon Edwards @damonedwards dev2ops.org DevOps Cafe damon@simplifyops.com
  3. 3. Wait... SimplifyOps?
  4. 4. rundeck.org
  5. 5. DTO Solutions DevOps and Automation Consulting
  6. 6. Shorten Dev Re ove m Ops Ah-ha! a l l of C onfus io W n
  7. 7. “How do I explain it” “My managers don’t get it” “Dev group won’t talk to me” “Ops group won’t talk to me” “QA says I’m dangerous” “I don’t know where to start” BUT.... “People say they are too busy getting real work done” “My boss told me to buy DevOps by next quarter or else” “I still don’t know where to start” “I still don’t know where to start” “Is anybody listening to me?” “THEY all just don’t get it”
  8. 8. 3 step process...
  9. 9. 3 step processs...
  10. 10. 3 step process... 1. Build the “Why?”
  11. 11. Rule #1
  12. 12. Rule #1 “DevOps”
  13. 13. Rule #1 “DevOps”
  14. 14. How we feel
  15. 15. How we feel
  16. 16. How we feel
  17. 17. How we feel
  18. 18. How we feel
  19. 19. How we look to everyone else
  20. 20. How we look to everyone else
  21. 21. How we look to everyone else
  22. 22. How we look to everyone else
  23. 23. DevOps misappropriation
  24. 24. DevOps misappropriation
  25. 25. DevOps misappropriation
  26. 26. Rule #2
  27. 27. Rule #2 There is no other “Why?” than the “Why?” of the business
  28. 28. Rule #2 There is no other “Why?” than the “Why?” of the business
  29. 29. Go ask people
  30. 30. 3 step process... 1. Build the “Why?” 2. Build organizational alignment
  31. 31. Ultimate goal: Develop a Common DevOps Vision
  32. 32. Ultimate goal: Develop a Common DevOps Vision expanded from
  33. 33. Ultimate goal: Develop a Common DevOps Vision 1. See the system expanded from
  34. 34. Ultimate goal: Develop a Common DevOps Vision 1. See the system expanded from 2. Focus on flow
  35. 35. Ultimate goal: Develop a Common DevOps Vision 1. See the system expanded from 2. Focus on flow 3. Recognize feedback loops
  36. 36. Ultimate goal: Develop a Common DevOps Vision 1. See the system expanded from 2. Focus on flow 3. Recognize feedback loops 4. Look for continuous improvement opportunities
  37. 37. “DevOps Vision??”
  38. 38. “DevOps Vision??”
  39. 39. Overt actions
  40. 40. Overt actions 1. Teach concepts
  41. 41. Overt actions 1. Teach concepts 2. Getting everyone on the same page
  42. 42. Overt actions 1. Teach concepts 2. Getting everyone on the same page a. value stream mapping
  43. 43. Overt actions 1. Teach concepts 2. Getting everyone on the same page a. value stream mapping b. timeline analysis
  44. 44. Overt actions 1. Teach concepts 2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis
  45. 45. Value Stream Mapping Core business service delivery process Current state value stream map Steering Committee Erica Switzer Full Projects / Expedites L/T Process time H/C Head count S/R Business Analyst Lead time P/T Scrap rate Erica Switzer D Estimates and requirements Defects EP Partially done TS Task switching W Erica Switzer Motion PD Project Manager Extra processes M Waiting Business Change request Daily Scrum meeting Mx3 Dx3 Develop Request QA build Technical Specification web assets L/T 6 weeks P/T 4 weeks H/C 12 S/R 5% Bob McNulty EP Cut project branch L/T 15 minutes P/T 5 minutes H/C 1 S/R 0% Chris Holmes Delta features and fixes L/T 8 weeks P/T 4 weeks H/C 5 S/R 25% Joe Harbaugh Dx2 QA Business Systems Support Wx2 Wx2 PDx4 Development Build and deploy Development Integration testing L/T 2 days P/T 4 hours H/C 1 S/R 10% Joe Harbaugh L/T 1 day P/T 1 day H/C 5 S/R 95% Joe Harbaugh D Release Engineering Stan Walters Deployment Document Jira issues TSx5 Set of service branches Deployment Meeting RT tickets Web Assets, flows and wireframes Development Program Management Development Daily Scrum meeting Jira issues Creative Change Control Forms Technical Operations Change Control RT tickets Release Build and deploy L/T 8 hours P/T 7 hours H/C 1 S/R 2% Fernando Gomez Acceptance testing L/T P/T H/C S/R Development Environments Documented test plans and cases W D D 5 days 5 hours 2 10% Raj Lee D PDx3 EP Feature testing L/T P/T H/C S/R Tested packages Mx8 PD Dx2 Deploy to Production Staging testing L/T 6 days P/T 90 minutes H/C 3 S/R 66% Frances Middleton 4 weeks 2.5 weeks 4 20% Raj Lee Deploy to Staging L/T 1 week P/T 3.5 days H/C 4 S/R 66% Frances Middleton Mx2 EP L/T 9 hours P/T 8 hours H/C 6 S/R 66% Allen Cannata Merge project branch L/T 30 minutes P/T 30 minutes H/C 1 S/R 33% Fernando Gomez PDx2 Build test plan L/T P/T H/C S/R QA Environments Build test cases 5 days 4 days 1 10% Raj Lee L/T P/T H/C S/R Staging Environment 2 weeks 8 days 2 20% Raj Lee Production Environment Performance testing Deploy to Performance L/T 6 days P/T 90 minutes H/C 3 S/R 66% Frances Middleton L/T 1 week P/T 3 days H/C 1 S/R 66% Allen Cannata Performance Environment 4 weeks 4 weeks 2 weeks 4 hours 4 weeks 1 day 1.5 days 7 hours 5 hours 1 hours 2.5 weeks 4.5 days 90 minutes 1.5 weeks 3.5 days 5.75 days Process Time = 62 days 8 hours 1.5 days 1 hour Lead Time = 113 days
  46. 46. Value Stream Mapping Core business service delivery process Current state value stream map Steering Committee Erica Switzer Full Projects / Expedites L/T Process time H/C Head count S/R Business Analyst Lead time P/T Scrap rate Erica Switzer D Estimates and requirements Defects EP Partially done TS Task switching W Erica Switzer Motion PD Project Manager Extra processes M Waiting Business Change request Daily Scrum meeting Mx3 Dx3 Develop Request QA build Technical Specification web assets L/T 6 weeks P/T 4 weeks H/C 12 S/R 5% Bob McNulty EP Cut project branch L/T 15 minutes P/T 5 minutes H/C 1 S/R 0% Chris Holmes Delta features and fixes L/T 8 weeks P/T 4 weeks H/C 5 S/R 25% Joe Harbaugh Dx2 QA Business Systems Support Wx2 Wx2 PDx4 Development Build and deploy Development Integration testing L/T 2 days P/T 4 hours H/C 1 S/R 10% Joe Harbaugh L/T 1 day P/T 1 day H/C 5 S/R 95% Joe Harbaugh D Release Engineering Stan Walters Deployment Document Jira issues TSx5 Set of service branches Deployment Meeting RT tickets Web Assets, flows and wireframes Development Program Management Development Daily Scrum meeting Jira issues Creative Change Control Forms Technical Operations Change Control RT tickets Release Build and deploy L/T 8 hours P/T 7 hours H/C 1 S/R 2% Fernando Gomez Acceptance testing L/T P/T H/C S/R Development Environments Documented test plans and cases W D D 5 days 5 hours 2 10% Raj Lee D PDx3 EP Feature testing L/T P/T H/C S/R Tested packages Mx8 PD Dx2 Deploy to Production Staging testing L/T 6 days P/T 90 minutes H/C 3 S/R 66% Frances Middleton 4 weeks 2.5 weeks 4 20% Raj Lee Deploy to Staging L/T 1 week P/T 3.5 days H/C 4 S/R 66% Frances Middleton Mx2 EP L/T 9 hours P/T 8 hours H/C 6 S/R 66% Allen Cannata Merge project branch L/T 30 minutes P/T 30 minutes H/C 1 S/R 33% Fernando Gomez PDx2 Build test plan L/T P/T H/C S/R QA Environments Build test cases 5 days 4 days 1 10% Raj Lee L/T P/T H/C S/R Staging Environment 2 weeks 8 days 2 20% Raj Lee Production Environment Performance testing Deploy to Performance L/T 6 days P/T 90 minutes H/C 3 S/R 66% Frances Middleton L/T 1 week P/T 3 days H/C 1 S/R 66% Allen Cannata Performance Environment 4 weeks 4 weeks 2 weeks 4 hours 4 weeks 1 day 1.5 days 7 hours 5 hours 1 hours 2.5 weeks 4.5 days 90 minutes 1.5 weeks 3.5 days 5.75 days Process Time = 62 days 8 hours 1.5 days 1 hour Lead Time = 113 days
  47. 47. Value Stream Mapping M Service pack review email W Release Program Management derived reqs. Estimates M PRD M EP Partially done TS Task switching W Waiting Technical Support Product Management EP(2) Documentum TS(2) M(3) W(2) ERR PRD M(3) checklist Remedy Ticket L/T = 60d P/T = 1d H/C = 1 S/R = >5% Victoria Doe D M EP(3) README QA Test L/T = 105d P/T = 11d H/C = 42 S/R = Sam Young L/T = 24d P/T = 4d H/C = 3 S/R = 50% Jen Garza MOP MOP Patch Calendar EP W Change Control EP Rollout Schedule L/T = 42d P/T = H/C = S/R = Peter Lee ERR PD(3) Selective Promotion L/T = 90d P/T = 15d H/C = 5 S/R = Steve Young New Targets W Server Provisioning Engineering Release M QA Forum Ticket M(3) BRD L/T = 60d P/T = 16d H/C = 3 S/R = 3% Reggie / Carlos MOP, SOP EP PD Cloud Services Release ERR D QA forum Tasks Motion PD Lockdown control Extra processes M PRD QA Environment QA Forum Ticket Defects EP W Cloud Services Release Memos L/T = 45d P/T = 21d H/C = 140 S/R = Bob Smith Scrap rate Customer Engineering Design Specs L/T = 45d P/T = 18d H/C = 23 S/R = Bob Smith Preliminary Development Head count S/R L/T = 105d P/T = 46d H/C = 15 S/R = 100% John Robert EP Engineering Planning Process Process time H/C Product Program Planning PD M(2) Lead time D Release Schedule L/T = P/T = H/C = S/R = Erica Smith PRD L/T P/T L/T = 28d P/T = 7d H/C = 1 S/R = Stephen / Xi crit bugs M(2) Current state value stream map Customer communication L/T = 56d P/T = 7d H/C = 6 S/R = 100% Suresh Wu Server Acceptance L/T = 14d P/T = 1d H/C = 4.5 S/R = 15% Lynn A. etc Remedy Ticket BTS README Full Development L/T = 75d P/T = 43d H/C = 130 S/R = Bob Smith M W(2) Deploy Release EP M(2) Commits Build L/T = 1d P/T = 0.3d H/C = 2 S/R = 33% John Doe Shared Drive Test PD(3) Release Promotion L/T = 60d P/T = 0.2d H/C = 1 S/R = >5% Victoria Doe Shared Drive Prod Packages XML Single Image Server L/T = 90d P/T = 8d H/C = 8 S/R = 2% Lewis S./Peter Y. M W(2) EP PD D(3) TS Production BRD
  48. 48. Value Stream Mapping M Service pack review email W Release Program Management derived reqs. Estimates M PRD M EP Partially done TS Task switching W Waiting Technical Support Product Management EP(2) Documentum TS(2) M(3) W(2) ERR PRD M(3) checklist Remedy Ticket L/T = 60d P/T = 1d H/C = 1 S/R = >5% Victoria Doe D M EP(3) README QA Test L/T = 105d P/T = 11d H/C = 42 S/R = Sam Young L/T = 24d P/T = 4d H/C = 3 S/R = 50% Jen Garza MOP MOP Patch Calendar EP W Change Control EP Rollout Schedule L/T = 42d P/T = H/C = S/R = Peter Lee ERR PD(3) Selective Promotion L/T = 90d P/T = 15d H/C = 5 S/R = Steve Young New Targets W Server Provisioning Engineering Release M QA Forum Ticket M(3) BRD L/T = 60d P/T = 16d H/C = 3 S/R = 3% Reggie / Carlos MOP, SOP EP PD Cloud Services Release ERR D QA forum Tasks Motion PD Lockdown control Extra processes M PRD QA Environment QA Forum Ticket Defects EP W Cloud Services Release Memos L/T = 45d P/T = 21d H/C = 140 S/R = Bob Smith Scrap rate Customer Engineering Design Specs L/T = 45d P/T = 18d H/C = 23 S/R = Bob Smith Preliminary Development Head count S/R L/T = 105d P/T = 46d H/C = 15 S/R = 100% John Robert EP Engineering Planning Process Process time H/C Product Program Planning PD M(2) Lead time D Release Schedule L/T = P/T = H/C = S/R = Erica Smith PRD L/T P/T L/T = 28d P/T = 7d H/C = 1 S/R = Stephen / Xi crit bugs M(2) Current state value stream map Customer communication L/T = 56d P/T = 7d H/C = 6 S/R = 100% Suresh Wu Server Acceptance L/T = 14d P/T = 1d H/C = 4.5 S/R = 15% Lynn A. etc Remedy Ticket BTS README Full Development L/T = 75d P/T = 43d H/C = 130 S/R = Bob Smith M W(2) Deploy Release EP M(2) Commits Build L/T = 1d P/T = 0.3d H/C = 2 S/R = 33% John Doe Shared Drive Test PD(3) Release Promotion L/T = 60d P/T = 0.2d H/C = 1 S/R = >5% Victoria Doe Shared Drive Prod Packages XML Single Image Server L/T = 90d P/T = 8d H/C = 8 S/R = 2% Lewis S./Peter Y. M W(2) EP PD D(3) TS Production BRD
  49. 49. Timeline Analysis Core business service delivery process Current state value stream map Steering Committee Erica Switzer Full Projects / Expedites L/T Process time H/C Head count S/R Business Analyst Lead time P/T Scrap rate Erica Switzer D Estimates and requirements Defects EP Partially done TS Task switching W Erica Switzer Motion PD Project Manager Extra processes M Waiting Business Change request Daily Scrum meeting Mx3 Dx3 Develop Request QA build Technical Specification web assets L/T 6 weeks P/T 4 weeks H/C 12 S/R 5% Bob McNulty EP Cut project branch L/T 15 minutes P/T 5 minutes H/C 1 S/R 0% Chris Holmes Delta features and fixes L/T 8 weeks P/T 4 weeks H/C 5 S/R 25% Joe Harbaugh Dx2 QA Business Systems Support Wx2 Wx2 PDx4 Development Build and deploy Development Integration testing L/T 2 days P/T 4 hours H/C 1 S/R 10% Joe Harbaugh L/T 1 day P/T 1 day H/C 5 S/R 95% Joe Harbaugh D Release Engineering Stan Walters Deployment Document Jira issues TSx5 Set of service branches Deployment Meeting RT tickets Web Assets, flows and wireframes Development Program Management Development Daily Scrum meeting Jira issues Creative Change Control Forms Technical Operations Change Control RT tickets Release Build and deploy L/T 8 hours P/T 7 hours H/C 1 S/R 2% Fernando Gomez Acceptance testing L/T P/T H/C S/R Development Environments Documented test plans and cases W D D 5 days 5 hours 2 10% Raj Lee D PDx3 EP Feature testing L/T P/T H/C S/R Tested packages Mx8 PD Dx2 Deploy to Production Staging testing L/T 6 days P/T 90 minutes H/C 3 S/R 66% Frances Middleton 4 weeks 2.5 weeks 4 20% Raj Lee Deploy to Staging L/T 1 week P/T 3.5 days H/C 4 S/R 66% Frances Middleton Mx2 EP L/T 9 hours P/T 8 hours H/C 6 S/R 66% Allen Cannata Merge project branch L/T 30 minutes P/T 30 minutes H/C 1 S/R 33% Fernando Gomez PDx2 Build test plan L/T P/T H/C S/R QA Environments Build test cases 5 days 4 days 1 10% Raj Lee L/T P/T H/C S/R Staging Environment 2 weeks 8 days 2 20% Raj Lee Production Environment Performance testing Deploy to Performance L/T 6 days P/T 90 minutes H/C 3 S/R 66% Frances Middleton L/T 1 week P/T 3 days H/C 1 S/R 66% Allen Cannata Performance Environment 4 weeks 4 weeks 2 weeks 4 hours 4 weeks 1 day 1.5 days 7 hours 5 hours 1 hours 2.5 weeks 4.5 days 90 minutes 1.5 weeks 3.5 days 5.75 days Process Time = 62 days 8 hours 1.5 days 1 hour Lead Time = 113 days
  50. 50. Waste Analysis Core business service delivery process Current state value stream map Steering Committee Erica Switzer Full Projects / Expedites L/T Process time H/C Head count S/R Business Analyst Lead time P/T Scrap rate Erica Switzer D Estimates and requirements Defects EP Partially done TS Task switching W Erica Switzer Motion PD Project Manager Extra processes M Waiting Business Change request Daily Scrum meeting Mx3 Dx3 Develop Request QA build Technical Specification web assets L/T 6 weeks P/T 4 weeks H/C 12 S/R 5% Bob McNulty EP Cut project branch L/T 15 minutes P/T 5 minutes H/C 1 S/R 0% Chris Holmes Delta features and fixes L/T 8 weeks P/T 4 weeks H/C 5 S/R 25% Joe Harbaugh Dx2 QA Business Systems Support Wx2 Wx2 PDx4 Development Build and deploy Development Integration testing L/T 2 days P/T 4 hours H/C 1 S/R 10% Joe Harbaugh L/T 1 day P/T 1 day H/C 5 S/R 95% Joe Harbaugh D Release Engineering Stan Walters Deployment Document Jira issues TSx5 Set of service branches Deployment Meeting RT tickets Web Assets, flows and wireframes Development Program Management Development Daily Scrum meeting Jira issues Creative Change Control Forms Technical Operations Change Control RT tickets Release Build and deploy L/T 8 hours P/T 7 hours H/C 1 S/R 2% Fernando Gomez Acceptance testing L/T P/T H/C S/R Development Environments Documented test plans and cases W D D 5 days 5 hours 2 10% Raj Lee D PDx3 EP Feature testing L/T P/T H/C S/R Tested packages Mx8 PD Dx2 Deploy to Production Staging testing L/T 6 days P/T 90 minutes H/C 3 S/R 66% Frances Middleton 4 weeks 2.5 weeks 4 20% Raj Lee Deploy to Staging L/T 1 week P/T 3.5 days H/C 4 S/R 66% Frances Middleton Mx2 EP L/T 9 hours P/T 8 hours H/C 6 S/R 66% Allen Cannata Merge project branch L/T 30 minutes P/T 30 minutes H/C 1 S/R 33% Fernando Gomez PDx2 Build test plan L/T P/T H/C S/R QA Environments Build test cases 5 days 4 days 1 10% Raj Lee L/T P/T H/C S/R Staging Environment 2 weeks 8 days 2 20% Raj Lee Production Environment Performance testing Deploy to Performance L/T 6 days P/T 90 minutes H/C 3 S/R 66% Frances Middleton L/T 1 week P/T 3 days H/C 1 S/R 66% Allen Cannata Performance Environment 4 weeks 4 weeks 2 weeks 4 hours 4 weeks 1 day 1.5 days 7 hours 5 hours 1 hours 2.5 weeks 4.5 days 90 minutes 1.5 weeks 3.5 days 5.75 days Process Time = 62 days 8 hours 1.5 days 1 hour Lead Time = 113 days
  51. 51. Waste Analysis   (Mary Poppendick’s “Seven Wastes of Software Development”)
  52. 52. How do you develop an org’s DevOps Vision? 1. Teach concepts 2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis
  53. 53. How do you develop an org’s DevOps Vision? 1. Teach concepts 2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis 3. Develop metrics chains
  54. 54. Metrics Chains What matters to the business Capability that influences what matters to the business Activity over which an individual can cause/influence outcomes
  55. 55. How do you develop an org’s DevOps Vision? 1. Teach concepts 2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis 3. Develop metrics chains
  56. 56. How do you develop an org’s DevOps Vision? 1. Teach concepts 2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis 3. Develop metrics chains 4. Identify projects / experiments against baseline
  57. 57. How do you develop an org’s DevOps Vision? 1. Teach concepts 2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis 3. Develop metrics chains 4. Identify projects / experiments against baseline 5. Repeat steps 2 - 4 (continuous improvement program)
  58. 58. Doing it without talking about “DevOps Vision”! 1. Teach concepts 2. Getting everyone on the same page a. value stream mapping b. timeline analysis c. waste analysis 3. Develop metrics chains 4. Identify projects / experiments against baseline 5. Repeat steps 2 - 4 (continuous improvement program)
  59. 59. Doing it without talking about “DevOps Vision”! 1. Teach concepts 2. Getting everyone on the same page 1. See the system a. value stream mapping b. timeline analysis c. waste analysis 3. Develop metrics chains 4. Identify projects / experiments against baseline 5. Repeat steps 2 - 4 (continuous improvement program)
  60. 60. Doing it without talking about “DevOps Vision”! 1. Teach concepts 2. Getting everyone on the same page 1. See the system a. value stream mapping 2. Focus on flow b. timeline analysis c. waste analysis 3. Develop metrics chains 4. Identify projects / experiments against baseline 5. Repeat steps 2 - 4 (continuous improvement program)
  61. 61. Doing it without talking about “DevOps Vision”! 1. Teach concepts 2. Getting everyone on the same page 1. See the system a. value stream mapping 2. Focus on flow b. timeline analysis c. waste analysis 3. Recognize feedback loops 3. Develop metrics chains 4. Identify projects / experiments against baseline 5. Repeat steps 2 - 4 (continuous improvement program)
  62. 62. Doing it without talking about “DevOps Vision”! 1. Teach concepts 2. Getting everyone on the same page 1. See the system a. value stream mapping 2. Focus on flow b. timeline analysis c. waste analysis 3. Recognize feedback loops 3. Develop metrics chains 4. Identify projects / experiments against 4. Look for continuous baseline improvement opportunities 5. Repeat steps 2 - 4 (continuous improvement program)
  63. 63. While theory and high-level concepts are introduced and explained, the focus of this workshop is on imparting practical “nuts and bolts” knowledge that attendees can use immediately in their day-today work. By Day 2, your team will be practices new techniques to analyze and diagnose your own DevOps problems. By Day 3, your team will be identifying potential solutions and building an improvement roadmap. Important Tool: Workshops Day 2 Day 3 Morning Sessions: • Analyzing Your Current State Morning Sessions: • Process Improvement and Automation Toolchain Design Principles • Solutions Discussion Agenda Day 1 Morning Sessions: • Welcome and Kickoff • Raising the Bar: Trends and High Performance • Case Study • Anti-Patterns Lunch Lunch Afternoon Sessions: • Successful Design Patterns • Organization and Process • Technical • Learning to See: Analyzing and Diagnosing Problems Afternoon Sessions: • Problem Identification Techniques • Improvement Metrics • Technical Deep Dive Lunch Afternoon Sessions: • Solutions Discussion (cont’d) • Project Listing and Roadmap Building Wrap-up = Principles = Analysis = Design
  64. 64. 3 step processs... 1. Build the “Why?” 2. Build organizational alignment 3. Continuous improvement loops
  65. 65. Continuous Improvement Plan Act Do Check
  66. 66. Continuous Improvement Plan Act Do Check
  67. 67. 3 step processs... 1. Build the “Why?” 2. Build organizational alignment 3. Continuous improvement loops
  68. 68. A word about breaking silos...

×