You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When we're ready to work on a story we run a story kickoff. For me, the most important aspects of that kickoff are:
- Everyone in the team arrives at a shared understanding of what we need to do
- That understanding is captured clearly and unambiguosly so we can refer back to it
- We have explored both happy paths and edge cases so that we minimise mistakes / unpleasant surprises
To fulfil these criteria there are some sub-aspects I like to see:
- We start with a blank slate so everyone is along for the journey (this doesn't preclude prep work)
- Everyone in the team is awake and focussed on the task in hand
- Everyone feels able to contribute
- We don't waste brain power on formal grammars when we are capturing our thoughts (such as given-when-thens)
For the last three years the technique I've used to tick all of these boxes is Example Mapping, which was invented by Matt Wynne of Cucumber.
What you need to run an Example Mapping session inside Jira:
- Your team of devs, testers, product owner, scrum master or what have you. Bring them together around a single screen, or run a video meeting and share your screen. We typically have some team members remote, so run a video meeting.
- Example Mapping for Jira app, Click the link to try it for free in the Atlassian Marketplace.
Get started
When you're ready to run a story kickoff, browse to the issue and click the Create Example Map button:
You will see the full screen editor, which allows you to capture rules, examples and questions. Repeat the following until you are out of ideas:
- Someone in the team suggests a rule
- Everyone thinks of examples that illustrate that rule (both happy and sad path)
- Some examples will drive out further rules
It is also important to capture questions as you go. Sometimes you can answer them straight away and other times you will come back to them.
Keep going until you are happy that all the rules have sufficient examples and you can't think of any more rules.
You can drag the rules around into an order that makes sense.
Here's a simple example to give you an idea:
Review
After you are done with the story kickoff, Example Mapping for Jira formats your Example Mapping session directly into the issue view. The team can refer back to it as the story is being coded, tested, accepted, deployed etc. You can always go back to edit it if you need to. This is how the above example looks in the issue view:
TeamUp Labs' Example Mapping tool has been on the web for a couple of years now and is used by companies such as Axa, Bloomberg, Maersk and Vonage. It has recently launched as a Jira app, with super-tight integration, no need to leave Jira, with all of your data stored in your own Jira org.
Give it a try and let me know how you get on!