Prioritisation Exercise: Difference between revisions

From AgileMe
Jump to navigation Jump to search
(Created page with "Category:Agile:WorkshopsCategory:Agile This workshop provides some experience in creating a Product Backlog in the form of a Story Map and running a dice based simulation against it to explore the need to make prioritisation decisions. ==Learning Objectives== * To be able to form a meaningful Product Backlog in the form of a story map * To order the items in a meaningful way * To be able to respond to the changing situation and make prioritisa...")
 
No edit summary
Line 1: Line 1:
[[Category:Agile:Workshops]][[Category:Agile]]
[[Category:Agile:Workshops]][[Category:Agile]]


This workshop provides some experience in creating a Product Backlog in the form of a [[Story Mapping|Story Map]] and running a dice based simulation against it to explore the need to make prioritisation decisions.
This workshop provides some experience in creating a Product Backlog with a [Priority Filter] and running a dice based simulation against it to explore the need to make prioritisation decisions.


==Learning Objectives==
==Learning Objectives==
Line 29: Line 29:
==Tasks==
==Tasks==
# Arrange the "Prioritisation Headers" as per the diagram below
# Arrange the "Prioritisation Headers" as per the diagram below
# Arrange the A4 envelopes under the backlog header in the desired prioritisation order
# Arrange the A4 envelopes under the headers in the desired prioritisation order
# To get the first iteration completion rate:
# Select which items are going to be attempted for the first sprint and placed them under that header
# To get the first iteration effort completed:
## Roll all of the dice
## Roll all of the dice
## Subtract the total of the red dice (impact of technical debt) from the white dice
## Subtract the total of the red dice (impact of technical debt) from the white dice
## The result is the first iteration completion rate
## The result is the first iteration effort completed
# Select which items have had been work
# Select which items in the sprint have had been completed by spending the effort completed against the item effort
# Repeat for the next sprint and so on


# Call over the facilitator to review and discuss
(Hint) At any time the envelopes can be opened by the participants to "decompose" the initiative or epic into smaller items.
 
When finished call over the facilitator to review and discuss


[[File:Prioritisation headers.jpeg|600px|Prioritisation Headers Arrangement]]
[[File:Prioritisation headers.jpeg|600px|Prioritisation Headers Arrangement]]

Revision as of 10:00, 17 May 2022


This workshop provides some experience in creating a Product Backlog with a [Priority Filter] and running a dice based simulation against it to explore the need to make prioritisation decisions.

Learning Objectives

  • To be able to form a meaningful Product Backlog in the form of a story map
  • To order the items in a meaningful way
  • To be able to respond to the changing situation and make prioritisation decisions

Timings

Allow for 30 minutes for table groups to successfully complete their tasks

Materials

Setup

  1. Cut up the "Prioritisation Initiatives, Epics and Stories"
  2. Choose one of the themes and place stories that belong to that theme in an A5 envelope
  3. Stick the epic of the corresponding theme to the front of the A5 envelope and seal it
  4. Place the A5 envelope inside an A4 envelope
  5. Stick the initiative of the corresponding theme to the front of the A4 envelope and seal it
  6. Repeat for the other themes until there are several A4 envelopes, one for each theme, with an A5 envelope inside it, with stories inside the A5 envelope

Tasks

  1. Arrange the "Prioritisation Headers" as per the diagram below
  2. Arrange the A4 envelopes under the headers in the desired prioritisation order
  3. Select which items are going to be attempted for the first sprint and placed them under that header
  4. To get the first iteration effort completed:
    1. Roll all of the dice
    2. Subtract the total of the red dice (impact of technical debt) from the white dice
    3. The result is the first iteration effort completed
  5. Select which items in the sprint have had been completed by spending the effort completed against the item effort
  6. Repeat for the next sprint and so on

(Hint) At any time the envelopes can be opened by the participants to "decompose" the initiative or epic into smaller items.

When finished call over the facilitator to review and discuss

Prioritisation Headers Arrangement

See Also