How Intel Improved Delivery
0 likes517 views
Mark Brodnik presented on how his team at Intel improved project delivery through adopting Agile practices. They transitioned from using a spreadsheet to track work to using CA Agile Central. Initially they used Scrum but found Kanban worked better for their flow of work. With these changes, they reduced their cycle time from 37 to 14 days. The team was hesitant to change at first but became fully bought into the Kanban approach after a few weeks of use.
How Intel Improved Delivery
- 1. World® ’16 How Intel Improved Delivery Mark Brodnik - PMP, Program Manager - Intel Corporation AMX45S AGILE MANAGEMENT
- 2. 2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD © 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies. The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA. For Informational Purposes Only Terms of this Presentation
- 5. 5 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Public Service Announcement § Movember is Men’s Health Month § Take control of your health and look after yourself
- 6. 6 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD My Background With Agile § Started my career as an application developer doing agile-like practices without really knowing it § Detoured into Process Improvement, took a 5 year journey with CMMI® § Agile exposure in our Agile Competency Center as the Rally Product Owner § Came back to application development using Agile methods § Product Line Manager for Service Management BI team driving Agile changes § Our IT group is currently driving a DevOps conversion
- 7. 7 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD My Team § 5 BI Developers, 1 Systems Analyst, 1 Product Owner § Responsible for maintaining the long term data storage and reporting for our Service Management tool § We focus on 5 key roadmap areas: – Self-Service BI – Advanced BI – Enterprise Integration – Dashboards – Operations
- 8. 8 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD What We Used to Do § SharePoint list with 33 columns § Weekly update meeting § Problems: – Data quality – Organization – Tracking status
- 11. 11 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Driving Change § Organizing roadmap items with portfolio feature § Create roadmap items as initiatives Transition SharePoint List to Rally
- 16. 16 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Converting to Kanban or: § Our Iterations and releases were arbitrary (not aligned to feature delivery) § We have to split stories to meet the needs of a fixed iteration – Because of Analysis delays – Customer Requirements delays – Customer Testing delays – Release Window timing – External team dependencies What We Learned From Retrospectives
- 18. 18 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Converting to Kanban § As a team, we came up with our Kanban States and WIP limits – None/Ready – Analysis – Development – Unit Test – Preview – Customer Test – CCB – Accepted
- 20. 20 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Results – Cycle Time Comparison Prior system = 37.1 days Current system = 14.3 days
- 21. 21 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Results Conversion from the hybrid waterfall to Agile Scrum took about 3 months § Improved Cycle Time § Custom field filters enabled easy quarterly summaries Conversion from Scrum to Kanban took about 3 weeks § Agile approach that better aligns to how we work § Team initially hesitant to switch but after a week they were completely bought in