Scrum Control or Kanban Agility? You Can Have both, Using Metrics
4 likes19,268 views
The document discusses the comparison between Scrum and Kanban frameworks, emphasizing the importance of metrics in optimizing team performance and delivery speed. It highlights the need to revise meeting structures and focuses on reducing bottlenecks to enhance workflow efficiency. Ultimately, the choice between Scrum or Kanban should be based on team dynamics and leadership styles rather than a one-size-fits-all solution.
![Cycle / Lead time
/rest/api/2/issue/VVPRJ-3030?expand=changelog
fields.created = T1
changelog.histories.items[].field = “status” = “To Do”
changeling.histories.items[].created = T2
changelog.histories.items[].field = “status” = “Done”
changeling.histories.items[].created = T3
Lead time = T3 - T1
Cycle time = T2 - T1](https://image.slidesharecdn.com/02-plan-ghiraldelli-170504093017/85/Scrum-Control-or-Kanban-Agility-You-Can-Have-both-Using-Metrics-23-320.jpg)
Scrum Control or Kanban Agility? You Can Have both, Using Metrics
- 3. Scrum Control or Kanban Agility? You can have both using metrics MARCIO GHIRALDELLI | QUALITY ENGINEER | ATLASSIAN | @MARCIOGH
- 4. Agenda Scrum or Kanban? Fluent Metrics Revamping Meetings Takeaways
- 5. Scrum • Rituals • Time boxed • Story point • Sprint burndown
- 6. • Incremental • Limits • Pull work • Throughput Kanban
- 8. SCRUM OR KANBAN? Signals which made me consider Kanban
- 9. Scrum or Kanban? Deployment speed Story points value Continuous integration Deployment got faster than Scrum cycle Blue-Green deployments Tests in production environment and feature flags Bottlenecks
- 10. Deployment speed Story points value Story points vs Business value It became hard to map infrastructure story points into business value Scrum or Kanban? Bottlenecks
- 11. Deployment speed Story points value Testers without work at beginning of Sprint Have to shift some testers work from late-testers to early-planners Bottlenecks Scrum or Kanban? UX and Designers Eventually developers were being blocked by other teams work
- 12. SCRUM OR KANBAN? It depends on your team and your leadership style.
- 13. Agenda Scrum or Kanban? Fluent Metrics Revamping Meetings Takeaways
- 14. FLUENT METRICS From Scrum burndown to Kanban throughput
- 15. Fluent metrics Estimative Story points Fluency and predicability The more fluent, the more predicable. The more predicable, the better the estimations Kanban metrics
- 16. Fluent metrics Story points Homogeneous issues Issues broken by team capacity rather than complexity Focus on avoiding bottlenecks The smaller, the better Estimative Kanban metrics
- 17. Fluent metrics Fluent metrics 3 standard metrics focused on the pipeline speed Estimative Kanban metrics Story points JIRA Software + JQL + REST
- 19. Throughput Throughput = 43 / 14 = 3,07
- 20. /rest/api/2/search?jql=project=JPERF AND resolutiondate > startOfDay(-14d) AND resolutiondate < endOfDay() Throughput Response.total / 14
- 21. FLUENT METRICS Cycle Time Lead Time 2
- 22. Cycle / Lead time Lead time = 9 days Cycle time = 8 days
- 23. Cycle / Lead time /rest/api/2/issue/VVPRJ-3030?expand=changelog fields.created = T1 changelog.histories.items[].field = “status” = “To Do” changeling.histories.items[].created = T2 changelog.histories.items[].field = “status” = “Done” changeling.histories.items[].created = T3 Lead time = T3 - T1 Cycle time = T2 - T1
- 24. FLUENT METRICS Work In Progress3
- 25. Work In Progress (WIP) WIP = 23
- 26. Work In Progress (WIP) /rest/api/2/search?jql=project=VVPRJ AND status NOT IN ("To Do", “Done") AND created > startOfDay(-14d) Response.total
- 27. FLUENT METRICS Bird’s eye view across different teams
- 28. FLUENT METRICS
- 29. Fact High LT/CT variation Consequence TP unstable, poor delivery estimates Action Increase backlog refinement
- 31. Fact Low LT/CT gap Consequence Backlog starvation Action Increase backlog
- 32. Fluent metrics triggers bottleneck discussions. FLUENT METRICS
- 33. Agenda Scrum or Kanban? Fluent Metrics Revamping Meetings Takeaways
- 34. REVAMPING MEETINGS No more Scrum cycles. How to deal with meetings?
- 36. REVAMPING MEETINGS Team level discussion driven by Cumulative Flow Diagram
- 40. REVAMPING MEETINGS Retrospectives driven by Control Chart Diagrams
- 42. REVAMPING MEETINGS Meetings driven by data will speed up decisions.
- 43. Agenda Scrum or Kanban? Fluent Metrics Revamping Rituals Takeaways
- 44. Metrics Metrics are important to visualize your teams strengths and bottlenecks. Usage of metrics depends on you, not on the framework Meetings Data driven meetings improve the quality and speed of your teams decisions Scrum or Kanban? There's no better framework, it depends on your teams profile and your leadership style Takeaways
- 45. TAKEAWAYS
- 46. Thank you! MARCIO GHIRALDELLI | QUALITY ENGINEER | ATLASSIAN | @MARCIOGH