Why take a Continuous Delivery approach in your organisatiion
Download as PPTX, PDF2 likes479 views
The document discusses the continuous delivery (CD) approach in IT service transformation, emphasizing its benefits in delivering features quickly, improving engagement, and enhancing customer satisfaction. It presents two case studies showcasing the successful implementation of CD in different enterprises, detailing the challenges faced and the outcomes achieved. Key takeaways include the importance of team collaboration, communication, and adopting a customer-centric mindset for ongoing improvements.
Why take a Continuous Delivery approach in your organisatiion
- 1. Dr Nish Mahanty @nishmahanty Why would you take a Continuous Delivery approach? The path to successfully transforming your IT Services.
- 4. 4 Two case studies of how I’ve applied CD in different enterprises
- 5. 5 Continuous Delivery is a method of getting features to our customers fast and often. http://productblog.seek.com.au/continuous-delivery
- 6. 6 Continuous Delivery is a method of getting features to our customers fast and often. And then incrementing on those features based on metrics and customer feedback http://productblog.seek.com.au/continuous-delivery
- 7. 7 Warning!
- 8. 8 CD often starts as a “tools” conversation
- 9. 9 Then you realise that your processes need to change
- 10. 10 Then you realise that your structures aren’t quite right
- 11. 11 Finally you notice (if you are successful) that your culture has changed
- 12. 12
- 13. 13 Common set of challenges
- 16. 16 Do more with less
- 17. 17 Improve Engagement & Retain Talent
- 21. 21 Keep the lights on
- 22. 22 Keep the lights on & don’t screw up
- 24. 24 Case Study 1: Online Accounting Software
- 29. 29 Challenges
- 36. 36 Approach
- 37. 37 Assemble the team, and brainstorm the problems
- 38. 38 Create a Value-Stream-Map for our delivery process and identify constraints
- 39. 39 Agree a model based on: Common KPIs Clear communications Trust
- 40. 40 Agreed a list of incremental improvements
- 41. 41 1. Agreed proportions of capacity for each class-of- service and stakeholder
- 42. 42 2. Improved communications between the teams
- 43. 43 3. Introduced Functional automation tests Automated functional tests 0 21 56 79 110 132 146 160 173 S O N D J F M A M # of Scenarios
- 44. 44 4. Introduced TDD and CI Automated functional tests 60 65 65 65 80 83 93 94 94 S O N D J F M A M % Coverage
- 45. 45 5. Automated our deployment scripts Automated functional tests Deployment duration (mins) S O N D J F M 130 98
- 46. 46 Outcomes
- 47. 47 Improved our predictability and delivery times Automated functional tests Cycle Time for Defects and Features (days) Cycle Time (Features and Defects) S O N D J F M 30 9.8
- 48. 48 Reduced our environment constraints Automated functional tests Time spent preparing an environment for a deployment (days) Cycle Time (Features and Defects) Delivery Duration 87% faster release 11 1
- 49. 49 Shifted the customer NPS by 70 points!
- 50. 50 Improved Team Engagement High Performance/ Hewitt Best Employer Zone 30% 100%0% 65%40%
- 51. 51 Relieved the pressure on the backlog
- 52. 52 Case Study 2: SAP Service Delivery
- 54. 54 Core platform for HR and Finance
- 55. 55 Challenges
- 56. 56 Demand for new functionality
- 57. 57 Two major stakeholders (with differing priorities)
- 59. 59 Approach
- 60. 60 Assemble the team, and train them on Kanban
- 61. 61 Assemble the team, and train them on Kanban (in particular, Kaizen, and Flow)
- 62. 62 Create a Value-Stream-Map of the delivery pipeline.
- 63. 63 Create a Value-Stream-Map of the delivery pipeline, and build a Kanban wall for their work
- 64. 64 SAP Team Kanban wall
- 65. 65 Month 1 Consultation /Envisaging Triage/ Prioritisatio n Investigate/ Analyse Solution Design Implement/ Build Test UAT CR Approval / CAB Deploy/ Close out Waiting Doing
- 66. 66 Month 2 Consultation /Envisaging Triage/ Prioritisatio n Investigate/ Analyse Solution Design Implement/ Build Test UAT CR Approval / CAB Deploy/ Close out Waiting Doing FinanceHR
- 67. 67 Month 3 Consultation /Envisaging Triage/ Prioritisatio n Investigate/ Analyse Solution Design Implement/ Build Test UAT CR Approval / CAB Deploy/ Close out Waiting Doing FinanceHR
- 68. 68 Outcomes
- 70. 70 Better visibility of priorities and progress for the stakeholders
- 73. 73 In Summary
- 74. 74 Why would you adopt Continuous Delivery?
- 75. 75 Take team driven approach
- 77. 77 Maintain a mindset of Continuous Delivery of value for the customers
- 78. 78 Thank you, and good luck
- 79. 79 Questions?
Editor's Notes
- #2: Understand the audience What is their background How many lead teams Are using some from of Agile/Lean Already started on the Continuous Delviery journey questions
- #24: My approach to delviering these outcomes is to adopt ideas from the CD handbook. I’ve been a passionate advocate for these ideas before they were called this, and it’s the reason I’m here today talkig on the topic.
- #66: A few things to notice. Ots of WIP for the number of people in the team. Very batchy
- #67: A few things to notice. Ots of WIP for the number of people in the team. Very batchy
- #68: A few things to notice. Ots of WIP for the number of people in the team. Very batchy