This document summarizes an event held by IIBA Adelaide on relative value prioritization. It describes a workshop technique used to collaboratively prioritize a backlog of 62 ideas for the IIBA Adelaide branch's delivery plan over the next two years. Participants ranked the ideas individually then negotiated as a group to finalize the rankings, achieving a shared prioritized backlog. Tips were provided on preparing for and facilitating the workshop technique.
2. IIBA® Australia acknowledges the Traditional Owners of
country throughout Australia and recognise their continuing
connection to land, waters and culture.
We pay our respects to Elders past, present and emerging
and extend our respects to all Aboriginal and Torres Strait
Islander people present with us today.
Acknowledgement of Country
3. Festival of Business Analysis
16 – 20 of October 2023
Australia & New Zealand
https://festivalofbusinessanalysis.org
5. Study Groups
17 August 2023
IIBA® Melbourne | Online
Product Ownership Analysis Study Group
28 August 2023
IIBA® Melbourne | Online
BABOK® Study Group
6. If you are interested and would like to express your interest in becoming a mentor
or mentee please scan the QR codes or visit the link below:
Mentoring Program
7.
8. Call for Volunteers
The IIBA Australia Chapter invites your expressions of interest (EOI) to join and support
us in providing our services to our members and community. Chapter volunteering is
activity and capacity based. In addition to completing this form, you are strongly
encouraged to get involved by attending Chapter events held in your local city.
For more information and to express your interest visit:
https://australia.iiba.org/volunteer
9. Follow us on Social Media
Join the Conversation NOW!
IIBA Australia IIBA Australia Chapter
@IIBAAUS
iiba_australia IIBA Australia
Chapter Ltd
iibaaustralia.com
13. Relative Value Prioritisation
What are we doing tonight?
Learn a workshop technique
“Relative Value Prioritisation”
Co-create IIBA Adelaide Branch’s
delivery plan for the next two
years
18/08/2023 13
14. The Product
Backlog
18/08/2023 14
“The list of stuff that needs to
get done ”
Random product owner
Tonight’s backlog
comprises 62
workshop ideas.
Not crying,
just “admiring
the problem”
15. The “Prioritised”
Backlog
“The agreed sequence in which
stuff should get done”
Random scrum master
Prioritisation is a
combination of factors:
18/08/2023 Relative Value Prioritisation 15
Value
Dependencies
Effort
Risk
16. How does this work then?
Part 1 – Initial Ranking (20 minutes)
• The table has 10 cards on it, numbered 1 to 10
• 1 is the lowest value and 10 is the highest
The numbers don’t represent anything, except that “2 is
more valuable than 1 and less valuable than 3”
18/08/2023 Relative Value Prioritisation 16
1 = Low
10 = High
17. How does this work then?
Part 1 – Initial Ranking (20 minutes)
• Write your name on the topic(s)
• Place your topic under the numbered card that most
fits the topic’s value
• Do not talk
• Do not touch anyone else’s topics
• Write notes on the back of the topics
18/08/2023 Relative Value Prioritisation 17
1 = Low
10 = High
18. How does this work then?
Part 1 – Initial Ranking (20 minutes)
18/08/2023 Relative Value Prioritisation 18
1 = Low
10 = High
Place your topic under
the numbered card that
most fits the topic’s
value
20. Ranking the stories
18/08/2023 Relative Value Prioritisation 20
Welcome back. Each ranking now has a second
number on it.
This is the maximum number of topics the ranking
can hold.
22. Ranking the stories
Part 2 – Final ranking (25 minutes)
• find your topic again
• negotiate with the other people for the same ranking
• defend your topic (or cave-in)
• move the less valuable topic to the lower rank
• repeat the process until all ranks have the max.
number of topics in them
18/08/2023 Relative Value Prioritisation 22
23. Ranking the stories
Part 2 – Final ranking (25 minutes)
18/08/2023 Relative Value Prioritisation 23
negotiate which topic
is more valuable, with
the other people for the
same ranking
24. So what just happened?
Wrap up
You have just:
• collaborated with your peers
• achieved a shared agreement
• co-created IIBA Adelaide Branch’s 2-year schedule
• learned a useful technique
• hopefully, had some fun
18/08/2023 Relative Value Prioritisation 24
25. Some tips for running this
Preparation
Print copies of the user stories:
• large enough to be easily readable
• A5-sized cards work well
• number the user stories for easy reference
The ranking cards can be post-it notes, but laminated cards
are soooo much more professional.
18/08/2023 Relative Value Prioritisation 25
26. Some tips for running this
Preparation
• Bring enough pens for everyone
• Remove most of the chairs from the room
And don’t tell the participants what to expect before they
arrive. It works best if they don’t know about part 2.
18/08/2023 Relative Value Prioritisation 26
27. How to ‘biggify’ this
More than 30 stakeholders?
• Ask a few people to act as “advocates” for a group of
stakeholders (reduces the numbers).
• Run two sessions in parallel with two groups of
stakeholders.
Then take the top-ranked stories from each and run
another session with this smaller set.
18/08/2023 Relative Value Prioritisation 27
I’m using this session as the official launch of my company Micromorphics Consulting. I started it in 2002 which makes it 21 years old this year, so the launch is a little overdue.
I’ve been in the IT industry for over 30 years and have spent time in most roles you can imagine (a few of which don’t exist anymore and some which I couldn’t imagine when I started). At various times a developer, trainer, database programmer, experience designer, project manager, scrum master and business analyst. Occasionally, a few of them at the same time.
What does Micromorphics do? Well, since it’s just me currently, it’s whatever I’m doing at any given time. But the plan is to specialise in “Capability Uplift and Coaching”.
Long way to go yet, but we have a logo now.
The purpose of tonight is two-fold.
Firstly, we will experience a technique that you can use in your workplace as a means to collaboratively rank a wide range of requirements / user stories in under 1 hour. Similar to a technique called ‘Stack Ranking’ but has a second part where true collaboration happens.
Secondly, we will co-create the topics that the IIBA Adelaide Brach will deliver over the next two years. The topics may not necessarily be suited for events such as this and may actually be better done as LinkedIn posts or articles.
The IIBA Team will commit to following the plan that you create for us tonight (of course, we’re agile and so if things change, we will pivot to deal with it).
Projects are essentially a series of tasks that get need to done in order to deliver value in the form of the project’s outcomes. This list of tasks is sometimes called the Product Backlog.
Common techniques such as MoSCoW (Must, Should, Could, Won’t) or assigning a Mandatory, Highly Desirable, Nice-to-have value, even giving them numbers 1, 2, 3, 4 only go some way towards ranking the stories. If you have 35 “Must Have” stories, which one gets delivered first?
Generally, a backlog item gets prioritised based on the highest urgency/benefit (value) and the smallest effort. (i.e. Weighted Shortest Job First), but other things can influence their position in the ranking – dependencies and risk.
A lower value or more complex task may need to be completed first if it enables the higher ranked task. And the Risk of not doing the work needs to be considered too. This can be viewed as another facet of the term ‘value’ - the cost of delay.
“Effort” and “Dependencies” can be easily defined and quantified, but Value can cover a number of concepts. Certainly, financial benefits are readily calculated, but what about (less easily quantifiable) benefits such as customer satisfaction, regulatory compliance, reducing technical debt, enhanced user experience?
By ranking requirements in order of relative value – we are merely saying that Requirement X is more valuable than Requirement Y, and less valuable than Requirement Z – without having to quantify it.
And 4 is not twice as valuable as 2,
In this workshop we look only at the Value of each requirement. Determining Effort and Dependencies are separate workshops.
Read your requirement(s).
Write your name on it.
Own it.
Understand it.
Fall in love with it.
Add notes if you want (they’ll help you in part 2)
You can read other people’s requirements, but you are not allowed to touch them.
There’s a full list of them pinned up on the walls
In this workshop we look only at the Value of each requirement. Determining Effort and Dependencies are separate workshops.
Read your requirement(s).
Write your name on it.
Own it.
Understand it.
Fall in love with it.
Add notes if you want (they’ll help you in part 2)
You can read other people’s requirements, but you are not allowed to touch them.
There’s a full list of them pinned up on the walls
Look at the cards on the table. I’ve written a number on them to represent the MAXIMUM number of stories at that rank, 1, 2, 4, 8, 16, 16, 8, 4, 2, and 1. It is your task to rearrange your cards to meet those numbers by negotiating with your peers.
Look at the cards on the table. I’ve written a number on them to represent the MAXIMUM number of stories at that rank, 1, 2, 4, 8, 16, 16, 8, 4, 2, and 1. It is your task to rearrange your cards to meet those numbers by negotiating with your peers.
You still can’t move someone else’s story (without their permission)
You definitely can talk
You still can’t move someone else’s story (without their permission)
You definitely can talk
There is a tactile component to this. Each person is physically getting up and moving their story to the rank they have agreed upon. You can sort-of do this online, with tools like Miro or Mural etc, but the physical act is so much more impactful since there is a physical commitment to move something.
Also, online conversations are difficult with just one active mic – breakout rooms or private chats are needed
There is a tactile component to this. Each person is physically getting up and moving their story to the rank they have agreed upon. You can sort-of do this online, with tools like Miro or Mural etc, but the physical act is so much more impactful since there is a physical commitment to move something.
Also, online conversations are difficult with just one active mic – breakout rooms or private chats are needed
If you have more than 30 stakeholders or more than 100 user stories.