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.
17. 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
20. 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
23. 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
24. Honourable mentions
4 Stakeholder Interviews
4 Persona Development
4 User Journey Analysis
4 Analytics & Data Mining
4 Feature Mapping
4 Brand workshops
28. 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
31. 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
34. 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
39. 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
42. 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
50. 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
52. 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]]
"""
...
53.
54. 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
57. 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