Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Modern Agile Project Toolbox

1,128 views

Published on

Agile is defined by an open development process driven by collaboration. But we know that collaboration is not always easy, and we need to come up with creative ways of establishing and supporting it.

For this reason, the agile community was very busy in the last decade coming up with new and innovative tools to boost collaboration - eg story mapping, impact mapping, example mapping, risk brainstorming, the 3 amigos workshop, stakeholder mapping, event storming etc. There are a lot of tools. But how do all they fit together, and when should you use one or another in the wider context of a project delivery?

This is a very practical session that will attempt to group and present modern agile tools in the context of project delivery and provide guidance recommendations for their use.

Published in: Technology
  • Be the first to comment

Modern Agile Project Toolbox

  1. 1. Modern Agile Project Toolbox
  2. 2. Konstantin Kudryashov @everzet
  3. 3. http://StakeholderWhisperer.com
  4. 4. @BDDLondon http://bddlondon.org
  5. 5. This talk is about...
  6. 6. Collaborative Decision Making
  7. 7. Individuals & Interactions over Processes & Tools
  8. 8. Workshops over Meetings
  9. 9. Discovering over Driving
  10. 10. Deliberate Discovery over Pre-project Discovery
  11. 11. Certainty of problem over Certainty of solution
  12. 12. Decision Making Framework 1. Surface Context & Goals 2. Expose Risks & Constraints 3. Explore Options 4. Form Delivery Strategy
  13. 13. The Good Practices over The Best Practices
  14. 14. 1. Context & Goals
  15. 15. Stakeholder Mapping
  16. 16. Making it work 4 Invite PS, PO and department champions 4 Use large canvas 4 Break brainstorming from analysis 4 Stakeholders must move themselves on canvas 4 Question power and interest 4 Address too many / not enough stakeholders
  17. 17. Metric Mapping
  18. 18. Making it work 4 Invite PS, PO and department champions 4 Use Increase / Decrease / Protect pattern 4 Metrics drive other metrics 4 Discuss metrics monitoring and reporting 4 Identify metric cadence vs coherence
  19. 19. Business Goal Definition
  20. 20. Making it work 4 Invite PO and PS 4 Start with milestone goals 4 Prefer metrics that influence behaviour 4 Ensure only 3-5 metrics per milestone 4 Focus on and challenge a business narrative 4 Make sure each milestone delivers value
  21. 21. Honourable mentions 4 Stakeholder Interviews 4 Persona Development 4 User Journey Analysis 4 Analytics & Data Mining 4 Feature Mapping 4 Brand workshops
  22. 22. 2. Risks & Constraints
  23. 23. Risk Discovery Workshop
  24. 24. Making it work 4 Engage everybody with high power and interest 4 Start from catastrophic outcomes 4 Make sure there are some crazy examples 4 Group by similarity 4 Work out root causes via scenarios
  25. 25. Strategic Event Storming
  26. 26. Making it work 4 Invite PO and department champions 4 Use unlimited space - large roll 4 Focus on events that happened in the past 4 Follow the flow of the business process 4 Events can branch and loop 4 The goal is to id the knowledge gaps and constraints
  27. 27. Skills Mapping
  28. 28. Making it work 4 Invite department champions 4 Brainstorm the skills needed in project 4 Use whiteboard in public place or a spreadsheet online 4 Everybody must have access 4 Everybody must be protected
  29. 29. Honourable mentions 4 Value Stream Mapping 4 Integration Mapping 4 Budget Discussions
  30. 30. 3. Options
  31. 31. Event Storming
  32. 32. Making it work 4 Invite PO and department champions 4 Pick a single narrow area to explore 4 Use unlimited space - large roll 4 Focus on Events. Commands and Rules will follow 4 Stop when constraint worth solving identified
  33. 33. Impact Mapping
  34. 34. Making it work 4 Invite department champions 4 Ensure variety of skill/expertise 4 Use a format suiting the audience 4 Ensure correct objectives 4 Keep options open 4 Remember Asteroids game 4 Every connection is hypothesis
  35. 35. Innovation Slider
  36. 36. Making it work 4 Invite PO and, optionally, PS 4 Describe innovation & predictability 4 Outline trade-offs 4 Discuss resulting approach
  37. 37. Honourable mentions 4 Platform demos 4 Prototyping 4 Wireframing
  38. 38. 4. Delivery Strategy
  39. 39. User Story Mapping
  40. 40. Making it work 4 Invite Product Owner 4 Start with the journey steps/activities 4 Use categories/topics to ease navigation 4 Use the timeline structure 4 Focus on capabilities rather than features 4 Remember Asteroids game
  41. 41. BDD & Examples
  42. 42. Feature: Image Disperser We have a pull of images and multi-paragraph text. We need to be able to disperse images throughout the text automatically. Rules: - Print all the images back to back if no paragraphs found - Spread images equally across paragraphs - If there are more images than paragraphs, multiple images are posted after a single paragraph - If there are more paragraphs than images, images are posted after couple of paragraphs ... Scenario: Two out of four images printed after each of two paragraphs Given a text with 2 paragraphs And 4 images When we disperse images into text Then the resulting text should look like: """ paragraph [[IMAGE]] [[IMAGE]] paragraph [[IMAGE]] [[IMAGE]] """ ...
  43. 43. Making it work 4 Invite the right stakeholders 4 Get closer to your stakeholders 4 Focus on the language that makes the problem, not solution easier 4 Visual examples do wonders
  44. 44. Example Mapping
  45. 45. Making it work 4 Product Owner aggregates initial set of rules 4 QA, Dev, PO, UX skills need to be represented 4 Examples are like episodes from The Friends 4 Split stories with too many rules 4 Turn stories with too many questions into spikes
  46. 46. Honourable mentions 4 Demand Mapping 4 Estimation 4 Mob programming
  47. 47. Decision Making Framework 1. Surface Context & Goals 2. Expose Risks & Constraints 3. Explore Options 4. Form Delivery Strategy
  48. 48. That's a lot of time spent talking!
  49. 49. Costs of rewriting the code over Costs of doing a workshop
  50. 50. Feedback loops define software costs
  51. 51. Our job is not to deliver software
  52. 52. Our job is to deliver the maximum amount of value with minimum amount of software
  53. 53. Workshops are sometimes the cheapest way to close particular feedback loops
  54. 54. Thank you!

×