Affinity Mapping - Revision history

Mmusij at 23:58, 20 November 2018

2018-11-20T23:58:20Z

← Older revision		Revision as of 23:58, 20 November 2018
Line 4:		Line 4:
	This technique can be useful in Retrospectives for example where a range of improvement ideas may be presented by the team, but now need to make sense of the ideas, grouping them, categorising them and removing overlaps and duplicates.		This technique can be useful in Retrospectives for example where a range of improvement ideas may be presented by the team, but now need to make sense of the ideas, grouping them, categorising them and removing overlaps and duplicates.

	[[File:Affinity_mapping.jpg\|Affinity Mapping]]		[[File:Affinity_mapping.jpg\|500px\|Affinity Mapping]]

	==Tasks==		==Tasks==

Mmusij at 23:57, 20 November 2018

2018-11-20T23:57:55Z

← Older revision		Revision as of 23:57, 20 November 2018
Line 3:		Line 3:

	This technique can be useful in Retrospectives for example where a range of improvement ideas may be presented by the team, but now need to make sense of the ideas, grouping them, categorising them and removing overlaps and duplicates.		This technique can be useful in Retrospectives for example where a range of improvement ideas may be presented by the team, but now need to make sense of the ideas, grouping them, categorising them and removing overlaps and duplicates.

			[[File:Affinity_mapping.jpg\|Affinity Mapping]]

	==Tasks==		==Tasks==

Mmusij at 06:47, 12 November 2018

2018-11-12T06:47:27Z

← Older revision		Revision as of 06:47, 12 November 2018
Line 1:		Line 1:
	[[Category:Agile:Workshops]][[Category:Agile]]		[[Category:Agile:Workshops]][[Category:Agile]]
	Affinity Mapping can be done in conjunction with the 2 ~~Minute~~ Brainstorm and allows attendees to simply group together and categorise a range of ideas and make sense of the data.		Affinity Mapping can be done in conjunction with the [[2 Min Brainstorm]] and allows attendees to simply group together and categorise a range of ideas and make sense of the data.

	This technique can be useful in Retrospectives for example where a range of improvement ideas may be presented by the team, but now need to make sense of the ideas, grouping them, categorising them and removing overlaps and duplicates.		This technique can be useful in Retrospectives for example where a range of improvement ideas may be presented by the team, but now need to make sense of the ideas, grouping them, categorising them and removing overlaps and duplicates.

Mmusij: Created page with "Category:Agile:WorkshopsCategory:Agile Affinity Mapping can be done in conjunction with the 2 Minute Brainstorm and allows attendees to simply group together and categ..."

2018-11-12T06:47:03Z

Created page with "Category:Agile:Workshops Category:Agile Affinity Mapping can be done in conjunction with the 2 Minute Brainstorm and allows attendees to simply group together and categ..."

New page

[[Category:Agile:Workshops]][[Category:Agile]]
Affinity Mapping can be done in conjunction with the 2 Minute Brainstorm and allows attendees to simply group together and categorise a range of ideas and make sense of the data.

This technique can be useful in Retrospectives for example where a range of improvement ideas may be presented by the team, but now need to make sense of the ideas, grouping them, categorising them and removing overlaps and duplicates.

==Tasks==
* Grouping the ideas:
** One by one: If the team are holding their own ideas, then ask if one person would like to share one of their ideas with the team, and if there are any duplicates to group them together in the centre of the table. Ask if another person would like to share another idea and repeat until all of the ideas are grouped in the centre of the table.
** All at once: If there are a number of ideas in the centre of the table or on a whiteboard / flip chart paper for example, then the ask the team to collectively group them together and form categories of ideas
* Ask the team to then write up the categories of the ideas either on post it notes or by writing on a flip chart paper or similar. Some teams like to draw boundaries around the post-it notes if there are a number of them and we need to make a distinction between categories
* If appropriate, ask the team to refactor the categories into something more meaningful using the ideas as inspiration – this can be useful to use the collective thinking in the team to arrive at a first cut Product Backlog for example, where the ideas have influenced the creation of the Product Backlog Items as a starting point