AgileLunch Meetup - Listen to your Board
•
2 j'aime•141 vues
Tune your senses, unhide your work. A presentation on visualizing work, delivered at Agile Lunch Meetup, Toronto, ON.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à AgileLunch Meetup - Listen to your Board
Similaire à AgileLunch Meetup - Listen to your Board (20)
Plus de Fernando Cuenca
Plus de Fernando Cuenca (11)
Dernier
Dernier (20)
AgileLunch Meetup - Listen to your Board
- 1. Listen to your board! Tune your senses, unhide your work fernando@squirrelnorth.com @fer_cuenca Fernando Cuenca SQUIRRELNORTH ALTERNATIVE PATHS TO AGILITY Agile Lunch Meetup February 22nd, 2019
- 3. Yesterday, I worked on X. Today, I’m going to continue working on X. I have no blockers. No blockers. No blockers. No blockers. No blockers. No blockers. No blockers.
- 4. Where is my stuff? What am I going to get at the end? Why does it take this long? Flow
- 6. People are rarely “blocked.” But work can easily stop flowing. Use “blockers” to refer to work, not people.
- 10. Stand back, observe, ask questions… Start from where you are now... … and evolve from there. Listen to your board. It’s trying to tell you something….
- 11. Physical vs. Digital: a False Dichotomy Visible vs. Invisible
- 13. Code Back- end ServiceAdd Product to Shopping Cart Add missing tests to automation suite 2+2 = 5 How Come? Regression testing for August Release Investigate DB lock issue in Server TO-1 Product Feature ProductionIssue Defect Paul Product Manager Ted Test Manager Dev Team Ursula User Implementation Tasks ReleaseTesting Sarah Sys Admin
- 14. Code Back- end ServiceAdd Product to Shopping Cart Add missing tests to automation suite 2+2 = 5 How Come? Regression testing for August Release Investigate DB lock issue in Server TO-1 Product Feature ProductionIssue Defect Paul Product Manager Ted Test Manager Dev Team Ursula User Implementation Tasks ReleaseTesting Sarah Sys Admin Model different kinds of work differently Stand Back Question: What are the different “things” we work on?
- 15. Code Back- end ServiceAdd Product to Shopping Cart Add missing tests to automation suite 2+2 = 5 How Come? Regression testing for August Release Investigate DB lock issue in Server TO-1 Product Feature ProductionIssue Defect Paul Product Manager Ted Test Manager Dev Team Ursula User Implementation Tasks ReleaseTesting Sarah Sys Admin What you visualize is what you will talk about. Stand Back Question: What deliverables are we working on?
- 16. Add Product to Shopping Cart ID: 12345 Start: 10/30/18 End: / / Cycle Time: Customer: Paul UX DBA Legal Writer Req’d Done þ þ ý ý þ þ “Who is this for?” “What external dependencies does this item have?” “What’s the age of this item? “Where do I find more details?” “Who’s working on what?”
- 18. ProgBA Tester BA writes the User Story Programmer implements the solution Tester verifies the acceptance criteria We’re DONE!
- 19. Discovery Discovery Discovery Discovery https://connected- knowledge.com/2014/04/19/understanding- kdp by Alexei Zheglov Model your process as collaborative knowledge discovery, rather than hand-offs.
- 20. Do we understand the feature? Do we know how to build it? What happens when we try to actually implement it? Did we build what we thought we built? Is this what the Business was really looking for? What happens when we integrate this feature with the others? Visualize “stages the work goes trough” rather than “activities people do.” Stand Back Questions: How do we discover the knowledge required to deliver what we deliver?
- 21. Add Product to Shopping Cart Investigate DB lock issue in Server TO- 1 Product Feature Production Issue Paul Product Manager Sarah Sys Admin Specification Code Construction Exploratory Testing We’re DONE! Diagnostic & Reproduction Solution ing Remediation Monitoring We’re DONE The workflow depends on the type of work.
- 22. Visualize different workflows using different lanes. Stand Back Question: How do we process different kinds of work?
- 24. Split Point Re-assembly Point “Packet Switching” Section Stand Back Questions: Where are all the component parts of a deliverable? What’s the proportion of completeness? What deliverables move together/independently? What’s waiting for what?
- 25. Team A Team B
- 26. Team A 1 2 Feature Development 1 UX Team User Experience & Design 2 Architects System Architecture Stand Back Question: How are various services interconnected?
- 27. Model Hierarchies with “Flight Levels.” https://www.leanability.com/en/blog-en/2017/04/flight-levels-the- organizational-improvement-levels by Klaus Leopold Stand Back Questions: What is the “bigger picture”? Which team/group is working on the various pieces?
- 29. Transformation Point New Work Type: “Release Build” Stand Back Question: What’s the life-cycle of various deliverables? How are we batching work? What’s the impact to flow efficiency?
- 30. Explicitly model “queues” and waiting stages that significantly interrupt flow. Stand Back Questions: How close are we to completion? Where does work stop flowing? Get stuck?
- 31. Use this style as a “transitional” state towards more explicit visualization. Stand Back Question: What do I need my team to see right now? 0% 100%
- 33. Conventions on how to read the board. Rules to guide decision making.
- 35. • Code written • Unit Tests written • Code checked in • Automatic build passes • Test cases identified • Pull request to Trunk issued • Reviewer available • Review passes • Suggested changed completed & tested • … • … • … Visualize transition rules Stand Back Question: Can I move a ticket to the next column? What are the “rules of the game” Do we all agree on them?
- 36. What should I pull in next? Can I pull it now? Selection Capacity
- 37. (2-5) (5) (3) (2) (2) (4) (10) Select by Cost of Delay Profile Capacity Constraints with WIP Limits
- 42. Make your “commitment point” visible and explicit, as well as the extent of the commitment. Stand Back Questions: What is the “span” of our commitments? Are we committing too soon?
- 43. Identify different levels of “commitment” (and who cares about each”)
- 44. Wrapping Up: Listen to your Board!
- 45. Stand back, and observe • What deliverables are we working on? • Is this the adequate mix of work? • Where are all the component parts of a deliverable? • What’s the proportion of completeness? • What deliverables move together/independently? • What’s waiting for what? • What is the “bigger picture”? • Which team/group is working on the various pieces? • Can I move a ticket to the next column? • What are the “rules of the game” • Do we all agree on them? • How are various services interconnected? • How do we discover the knowledge required to deliver what we deliver? • How close are we to completion? • Where does work stop flowing? Get stuck? • What do I need my team to see right now? • How do we process different kinds of work? • What work is not moving? • How long has it been blocked? • What needs attention? • What is the “span” of our commitments? • Are we committing too soon?
- 46. Patterns in the flow Mix of work Look for patterns High WIP
- 47. Expect Evolution
- 48. Visible boards are “social” Visualization will affect what you talk about… … and how you talk about it.
- 50. SQUIRRELNORTH ALTERNATIVE PATHS TO AGILITY