MDA Retrospective: Difference between revisions

From AgileMe
Jump to navigation Jump to search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
[[Category:Agile:Workshops]][[Category:Agile]]
[[Category:Agile:Workshops]][[Category:Agile]]
==Outcomes==
==Outcomes==
This retrospective  
This retrospective attempts to uncover the deeper impacts of the process using the MDA (Mechanics, Dynamics and Aesthetics) framework as a means to determine the current processes and their behavioural impact and emotional responses, and determine possible future processes given the desired emotional responses and behaviours.


==Timings==
==Timings==
Line 11: Line 11:
* Post-it notes
* Post-it notes


==Tasks==
==Preparation==
 
On a sheet of flip chart paper or on a whiteboard create a table with Mechanics, Dynamics, Aesthetics in one column and Observations, Impacts and Changes as a title row.
 
 
AESTHETICS (Emotional Responses)


{| class="wikitable"
{| class="wikitable"
!colspan="4"|Shopping List
!colspan="4"|MDA RETROSPECTIVE
|-
|-
|
!|
!|OBSERVATIONS
!|OBSERVATIONS
!|IMPACTS
!|CHANGES
!|CHANGES
|-
|-
|MECHANICS (Rules, Processes, Actions)
!|MECHANICS
|
(Rules, Processes, Actions)
|
|
|
|
|-
|-
|DYNAMICS (Behaviours)
!|DYNAMICS
|
(Behaviours)
|
|
|
|
|-
|-
|AESTHETICS (Emotional Responses)
!|AESTHETICS
|
(Emotional Responses)
|
|
|
|
Line 42: Line 38:




# Start by drawing up a 3 x 3 grid on the flip chart paper with icons or titles for each of the quadrants: "Good Stuff", "Challenges", "Ideas & Actions", and "Recognition"
==Connections==
# Next invite the team to write on post-it notes which items helped them during the Sprint.
# Invite the team to meet each other and briefly discuss the processes, behaviours and emotional responses that they currently observe in the current environment.
# Then invite the team to place their items in the "Good Stuff" quadrant with a few details about why these were important to them. (Encouraging some team discussion can also help to uncover some more detail about why these items had a positive impact on the team.)
==Concepts==
# Repeat steps 2 and 3 for the "Challenges" and then "Ideas & Actions".
# Introduce the MDA framework as a means to uncover the processes, behaviours and emotional responses.
# Dote vote on each of the actions with each team member casting 3 votes to understand which actions are the most important and prioritise them accordingly.
==Concrete Practice==
# Finally invite the team to write post-it notes for the "Recognition" quadrant so that they can recognise who in the team or outside of the team really helped them during the Sprint, and place these on the flip chart paper. (It is usually good practice to ask the team how they might want to recognise someone outside of the team e.g. cake or a simple email of thanks for example.)
# Ask the attendees to grab some post it notes and a sharpie, and write down what processes they see currently in their environment, placing these in the '''Mechanics''' section under the '''Observations''' header
 
# Then ask the attendees to write post it notes for the behaviours that are caused by the mechanics and place these in the '''Dynamics''' section under the '''Observations''' header
Don't forget to select at least one action to carry forwards to the next Sprint Planning session to be resolved in the next Sprint.
# Once this is done, then ask the attendees to write post it notes for the emotional responses that are caused by the behaviours and place these under the '''Aesthetics''' section under the '''Observations''' header
 
# At this point give the attendees time to process their responses for a couple of minutes
==Alternatives==
# Now challenge the attendees with writing post it notes for what are the desired emotional responses that they would like to have in their environment and place these in the '''Aesthetics''' section under the '''Changes''' header.
An alternative for this technique is to simply facilitate the conversation and write up the findings on the flip chart paper rather than using post-it notes. This can help to improve the flow of the conversation
# Next ask the attendees to write post it notes for what behaviours might lead to those desired aesthetics and place them in the '''Dynamics''' section under the '''Changes''' section
# Finally, ask the attendees to write post it notes for the processes that might enable the dynamics and desired aesthetics, and place these in the '''Mechanics''' section under the '''Changes''' section
==Closure==
# Finally derive some actions that might allow the desired '''Mechanics''' to be implemented, and this becomes an action plan or tasks to be placed on a backlog to be ordered along with the work
# Invite the team to share their observations and insights about the session.


==References==
==References==
# Agile Retrospectives: Making Good Teams Great, Esther Derby, Diana Larsen, (2006)
# Agile Retrospectives: Making Good Teams Great, Esther Derby, Diana Larsen, (2006)
# Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009
# Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009

Latest revision as of 07:42, 10 November 2020

Outcomes

This retrospective attempts to uncover the deeper impacts of the process using the MDA (Mechanics, Dynamics and Aesthetics) framework as a means to determine the current processes and their behavioural impact and emotional responses, and determine possible future processes given the desired emotional responses and behaviours.

Timings

Allow 30-60 minutes for this exercise

Equipment

  • Sheet of flip chart paper
  • Sharpies for everyone
  • Post-it notes

Preparation

On a sheet of flip chart paper or on a whiteboard create a table with Mechanics, Dynamics, Aesthetics in one column and Observations, Impacts and Changes as a title row.

MDA RETROSPECTIVE
OBSERVATIONS CHANGES
MECHANICS

(Rules, Processes, Actions)

DYNAMICS

(Behaviours)

AESTHETICS

(Emotional Responses)


Connections

  1. Invite the team to meet each other and briefly discuss the processes, behaviours and emotional responses that they currently observe in the current environment.

Concepts

  1. Introduce the MDA framework as a means to uncover the processes, behaviours and emotional responses.

Concrete Practice

  1. Ask the attendees to grab some post it notes and a sharpie, and write down what processes they see currently in their environment, placing these in the Mechanics section under the Observations header
  2. Then ask the attendees to write post it notes for the behaviours that are caused by the mechanics and place these in the Dynamics section under the Observations header
  3. Once this is done, then ask the attendees to write post it notes for the emotional responses that are caused by the behaviours and place these under the Aesthetics section under the Observations header
  4. At this point give the attendees time to process their responses for a couple of minutes
  5. Now challenge the attendees with writing post it notes for what are the desired emotional responses that they would like to have in their environment and place these in the Aesthetics section under the Changes header.
  6. Next ask the attendees to write post it notes for what behaviours might lead to those desired aesthetics and place them in the Dynamics section under the Changes section
  7. Finally, ask the attendees to write post it notes for the processes that might enable the dynamics and desired aesthetics, and place these in the Mechanics section under the Changes section

Closure

  1. Finally derive some actions that might allow the desired Mechanics to be implemented, and this becomes an action plan or tasks to be placed on a backlog to be ordered along with the work
  2. Invite the team to share their observations and insights about the session.

References

  1. Agile Retrospectives: Making Good Teams Great, Esther Derby, Diana Larsen, (2006)
  2. Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009
Retrieved from "https://agileme.wiki/wiki/index.php?title=MDA_Retrospective&oldid=1330"