Project M87
•
0 likes•177 views
Slides from 9/5/19 Kanban Coaching Exchange with Claudia & David. Their talk looks at flow efficiency and charting.
Recommended
Recommended
More Related Content
Similar to Project M87
Similar to Project M87 (20)
More from Helen Meek
More from Helen Meek (20)
Recently uploaded
Recently uploaded (20)
Project M87
- 1. Project M87 • The Event Horizon Telescope (EHT) — a planet-scale array of eight ground-based radio telescopes forged through international collaboration — was designed to capture images of a black hole. • Since then we have been working on building Automated Telescope Calibration software, and Mass Calculation is next. Things have not gone very rosy so far, and we need to again collaborate to get the entire picture. • We are keen to find out how we can get things done without it taking an entire galactic year!
- 2. Let’s not waste time • Divide yourselves in groups of max 7 people
- 3. Flow efficiency Touch time Total time to deliver * 100%
- 4. Analyse Accept customer issue DEV Test Release Notify customer 10 mins 1 day 1 day 1 day 1 day 1 day 5 days 7 days 9 days 2 days 10 mins Flow Efficiency = 5 days/ 28 *100% =18%
- 5. Assignment: Flow Efficiency 0 1 00
- 7. Changes Everyone involved in Project 87 had a catch up. Together you decided to implement the following changes: • A cross functional Scrum team was formed consisting of: - 5 development team members: Luke, Anakin, Ben, Rey, Qui- Gon - Scrum Master: Windu - Product Owner: Leia • Han and his colleagues implemented infrastructure as code and self service infrastructure. • Align the sprint cadence with the release window. Note: in the future the team aims to release on demand so they are not restricted to only release once a fortnight.
- 8. The hard reality Your team has already run 8 sprints. The team is consistently completing 1-3 Product Backlog Items per sprint. However, things are not really flowing. Each sprint, it seems that more and more Product Backlogs Items are being carried over to the next sprint and you are not sure what the underlying problem is. The longer this goes on, the longer it seems to take before Product Backlogs Items are done. It seems like the mass blackhole functionality is falling in a black hole! In the last sprint retrospective your team agreed to focus on flow and use flow based metrics to help you.
- 10. Assignment: Daily Scrum 0 1 00
- 13. In Dev Dev Complete In Test DoneReady to DeploySprint Backlog SLE: 85% of items delivered in 68 days or lessSLE Days Weeks Blocked
- 18. Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Sprint 7 Sprint 8 Approximate average cycle time = 67 days Approximate average cycle time = 24 days
- 20. In Dev Dev Complete In Test DoneReady to DeploySprint Backlog SLE: 85% of items delivered in 68 days or lessSLE Days Weeks Blocked