Prioritisation Exercise - Revision history

Mmusij: /* Setup */

2022-05-17T12:14:09Z

Setup

← Older revision		Revision as of 12:14, 17 May 2022
Line 24:		Line 24:
	# Stick the epic of the corresponding theme to the front of the A5 envelope and seal it		# Stick the epic of the corresponding theme to the front of the A5 envelope and seal it
	# Place the A5 envelope inside an A4 envelope		# Place the A5 envelope inside an A4 envelope
	# Stick the initiative of the corresponding ~~theme~~ to the front of the A4 envelope ~~and seal it~~		# Stick the initiative of the corresponding themes to the front of the A4 envelope
	# 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		# Repeat for the other themes
			# There should be 4 x A4 envelopes, one for each pair of themes, with 2 x A5 envelopes inside each one, with 3 x stories inside each A5 envelope
			# Finally seal the A4 envelopes

	==Scenario==		==Scenario==

Mmusij at 10:06, 17 May 2022

2022-05-17T10:06:12Z

← Older revision		Revision as of 10:06, 17 May 2022
Line 26:		Line 26:
	# Stick the initiative of the corresponding theme to the front of the A4 envelope and seal it		# Stick the initiative of the corresponding theme to the front of the A4 envelope and seal it
	# 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		# 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

			==Scenario==
			The scenario is to deliver the maximum value possible within simulated 6 sprints. At various times the prioritisation choices will need to be made based upon the roll of the dice and how well the participants score.

	==Tasks==		==Tasks==
Line 35:		Line 38:
	## 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 effort completed		## The result is the first iteration effort completed
	# Select which items in the sprint have had been completed by spending the effort completed against the item effort		# Select which items in the sprint have had been completed by spending the effort completed against the item effort and mark the item when done and completed
			# Total up the value completed in the sprint and write it on the header
			# Unfinished items can be reprioritised in the backlog, prioritisation columns or in the next sprint
	# Repeat for the next sprint and so on		# 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.		(Hint) At any time the envelopes can be opened and replaced by the contents to "decompose" the initiative or epic into smaller items.

	When finished call over the facilitator to review and discuss		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]]

			==Debrief==
			* Reflect upon the prioritisation decisions that you made and how you made them through the simulation

	==See Also==		==See Also==
	* [[Wedding Planner]]		* [[Wedding Planner]]

Mmusij at 10:00, 17 May 2022

2022-05-17T10:00:01Z

← Older revision		Revision as of 10:00, 17 May 2022
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]]

Mmusij: 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..."

2022-05-17T09:54:44Z

Created page with "Category:Agile:Workshops Category: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..."

New page

[[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.

==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==
* Each team should have a printed copies of:
** [[Media:Prioritisation_headers.pdf|Prioritisation Headers]]
** [[Media:Prioritisation_stories.pdf|Prioritisation Initiatives, Epics and Stories]]
* 5 x white dice + 2 x red dice
* Post-it notes
* Marker pens

==Setup==
# Cut up the "Prioritisation Initiatives, Epics and Stories"
# Choose one of the themes and place stories that belong to that theme in an A5 envelope
# Stick the epic of the corresponding theme to the front of the A5 envelope and seal it
# Place the A5 envelope inside an A4 envelope
# Stick the initiative of the corresponding theme to the front of the A4 envelope and seal it
# 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==
# Arrange the "Prioritisation Headers" as per the diagram below
# Arrange the A4 envelopes under the backlog header in the desired prioritisation order
# To get the first iteration completion rate:
## Roll all of the dice
## Subtract the total of the red dice (impact of technical debt) from the white dice
## The result is the first iteration completion rate
# Select which items have had been work

# Call over the facilitator to review and discuss

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

==See Also==
* [[Wedding Planner]]