Difference between revisions of "Strengths-Based Retrospective"

From Agile Retrospective Resource Wiki
Jump to navigation Jump to search
 
Line 8: Line 8:
 
Flip charts and post-it notes.
 
Flip charts and post-it notes.
 
===Process:===
 
===Process:===
Discovering strengths: Think of something that succeeded in this iteration that the team managed to accomplish beyond expectation, and which produced benefits for you, the team, and/or for your customers. Now ask yourself and your team the following questions:
+
'''Discovering strengths''': Think of something that succeeded in this iteration that the team managed to accomplish beyond expectation, and which produced benefits for you, the team, and/or for your customers. Now ask yourself and your team the following questions:
  
 
   * How did we do it? What did we do to make it successful?
 
   * How did we do it? What did we do to make it successful?
Line 18: Line 18:
 
If you are using the [http://www.benlinders.com/2013/which-questions-do-you-ask-in-retrospectives/ four key questions], the question "What did we do well?" can also be used as a solution-focused approach to find strengths that can be deployed to address problems a team is facing.  
 
If you are using the [http://www.benlinders.com/2013/which-questions-do-you-ask-in-retrospectives/ four key questions], the question "What did we do well?" can also be used as a solution-focused approach to find strengths that can be deployed to address problems a team is facing.  
  
Defining actions: Think of a problem that you had in the past iteration, one that is likely to happen again. For example a problem that is keeping you and your team from delivering benefits for your customers? Now ask:  
+
'''Defining actions''': Think of a problem that you had in the past iteration, one that is likely to happen again. For example a problem that is keeping you and your team from delivering benefits for your customers? Now ask:  
  
 
   * How can you use your individual or team strengths to solve this problem?
 
   * How can you use your individual or team strengths to solve this problem?
Line 25: Line 25:
  
 
Again, this applies appreciative inquiry by envisioning what can be done using the previously discovered strengths and giving energy to the team members to carry it out.
 
Again, this applies appreciative inquiry by envisioning what can be done using the previously discovered strengths and giving energy to the team members to carry it out.
 +
 
===Source:===
 
===Source:===
 
This exercise is described in the book [http://www.benlinders.com/getting-value-out-of-agile-retrospectives/ Getting Value out of Agile Retrospectives], written by Luis Gonçalves and Ben Linders. The book can be downloaded from [http://www.infoq.com/minibooks/agile-retrospectives-value InfoQ] or [https://leanpub.com/gettingvalueoutofagileretrospectives LeanPub]. Also available as a [http://www.amazon.com/Getting-Value-Agile-Retrospectives-Retrospective/dp/1304789624/ Paperback Edition]
 
This exercise is described in the book [http://www.benlinders.com/getting-value-out-of-agile-retrospectives/ Getting Value out of Agile Retrospectives], written by Luis Gonçalves and Ben Linders. The book can be downloaded from [http://www.infoq.com/minibooks/agile-retrospectives-value InfoQ] or [https://leanpub.com/gettingvalueoutofagileretrospectives LeanPub]. Also available as a [http://www.amazon.com/Getting-Value-Agile-Retrospectives-Retrospective/dp/1304789624/ Paperback Edition]

Latest revision as of 07:12, 10 September 2014

Use:

A strengths-based retrospective is a different approach for an agile / Scrum retrospective. Instead of coming up with a list of actions to start doing new things (which you might not be capable of doing), your actions result in doing more of the things that you are already doing and which you are good at.

Length of time:

45 - 90 minutes

Short Description:

A strength-based retrospective consists of two steps: discovering strengths, then defining actions that use them. Both steps consist of asking retrospective questions.

Materials:

Flip charts and post-it notes.

Process:

Discovering strengths: Think of something that succeeded in this iteration that the team managed to accomplish beyond expectation, and which produced benefits for you, the team, and/or for your customers. Now ask yourself and your team the following questions:

 * How did we do it? What did we do to make it successful?
 * What helped us do it? Which expertise or skills made the difference? Which strengths that you possess made it possible?
 * How did being part of a team help to realize it? What did team members do to help you? Which strengths does your team have?

The questions are based on Appreciative Inquiry, an approach that focuses on value and energy. These questions give visibility to good things that happened and explore the underlying strengths that made it possible.

If you are using the four key questions, the question "What did we do well?" can also be used as a solution-focused approach to find strengths that can be deployed to address problems a team is facing.

Defining actions: Think of a problem that you had in the past iteration, one that is likely to happen again. For example a problem that is keeping you and your team from delivering benefits for your customers? Now ask:

 * How can you use your individual or team strengths to solve this problem?
 * What would you do more frequently that would help prevent the problem from happening again?
 * Which actions can you take, which you are already capable of?

Again, this applies appreciative inquiry by envisioning what can be done using the previously discovered strengths and giving energy to the team members to carry it out.

Source:

This exercise is described in the book Getting Value out of Agile Retrospectives, written by Luis Gonçalves and Ben Linders. The book can be downloaded from InfoQ or LeanPub. Also available as a Paperback Edition