4 Quadrant: Focus Area based Team Retrospective.

The Regular and most popular retrospectives end with action items on the specific person in the team. 

while the retrospective's primary goal is to enable the team to reflect onto themself and tune their behaviour for becoming more effective. In order to provide such a platform I practiced and coached 4 quadrant, focus area based retrospectives.

In which the team focus on the over all improvement and not just an action item. this is truely the team's behavioural change and their actions to become more effective. 

Based on many successful coaching experience, i would like to present this activity based session.


The team identify the focus areas for improvements, then identifies the small delta improvement in that focus area that is measurable. then they decide on if they need external coaching or internally the team can achieve the goal.


Focus areas | Coaching/Training


Measurement | Self / team 


Outline/Structure of the Tutorial

The recap of the goal for Retrospective

Introduction to 4 quadrant method.

Activity for using the new 4 quadrant method. 

summarise the outcome.


Learning Outcome

Key outcome:

Conduct Effective retrospective

Introduction to new and effective retrospective method.

Target Audience

Team members, Scrum Masters

schedule Submitted 6 years ago

Public Feedback

comment Suggest improvements to the Speaker
  • Pramod Sadalage
    By Pramod Sadalage  ~  5 years ago
    reply Reply



    Looks like http://agilemetaphors.com/presentations/ has expired the domain registration. Are you sure the link is correct?



    • Naveen Nanjundappa
      By Naveen Nanjundappa  ~  5 years ago
      reply Reply

      Hi Pramod,

      Yes, 2 days before my domain expired and is down. I am currently working on the website, sorry for the inconvinence caused. 


      I don't have a presentation related to this specific topic, I would be happy to discuss with you in person and explain the thoughts behind my presentation. would that help ?

      my contact number is 0-9980505003 


      Naveen Nanjundappa

      • Pramod Sadalage
        By Pramod Sadalage  ~  5 years ago
        reply Reply

        If you have the presentation with you, load them on slideshare/dropbox. They do not have to be for this specific topic

    • Nitin Ramrakhyani
      By Nitin Ramrakhyani  ~  6 years ago
      reply Reply

      Hi Naveen,

      Thanks for submission. Retrospectives are certainly a very crucial aspect of being/ practising Agile, so this topic will certainly arouse alot of interest.

      Could you please elaborate a bit more on the learning outcomes, structure/outline of your overall talk. I checked the link that you provided but couldn't find the slides related to this talk. Can you point us to the deck that you intend to use?

      Also, I suggest that you take a look at some of the other similar proposals and see if you can come up with any significant differentiator/ USP for your talk based on your rich experience. That'll help the review team in shortlisting the best proposals.

      Look forward to hear from you.



      • Naveen Nanjundappa
        By Naveen Nanjundappa  ~  5 years ago
        reply Reply

        <Naveen> Most of the times the retrospectives are done with specific data gathering style (Plus, Delta - Start-stop-continue and so on.. ) and eventually end up with action items for improvement areas. What I have noticed is these action items are usually short term oriented and reflect to some quick fixes and individual focus.


        The retrospective I have proposed here is the result of my coaching and building winning teams with more focused approach towards "reflecting onto ourselves and tuning our behaviour for becoming more effective"


        These session will be activity based, a situation from a real life will be given to the teams and retrospective session will be held by the participants in groups.


        Step 1. Team members will read through the situation and list the Plus and Delta.

        Step 2. I will guide them through getting the focus areas for improvements. This will be a group of similar items from both plus and delta.

        Step 3. Voting on focus areas if there are more than 2

        Step 4. Discussion on top 2 focus areas and how much to improve on those areas.

        Step 5. List the measurement for the improvement (for example if the team doesn't have stories updated in the task board, one of the measurement could be. " as a team we all update the task board every day")

        Measurement is the small list of achievable items with reference to the focus area.

        Step 6. pick the measurement item and ask the team if they need "external coaching/training" to improve and achieve the measurement or they would do it "self / within team collaboration"

        Step 7. each item shall be mapped to either as, can be achieved with external support or internal support. Thus the focus is helping the team improve and become more effective by focusing on the focus group and the measurement (small improvements)

        Step 8. concluding what/how the teams will improve in the next sprint and closure.


        Most of the times I have found that the teams had 4 or 5 votes for fist of five ! Raising the confidence level of the team members and also clearly indicating that is the "improvement/effectiveness focus area" for the team during the sprint.



        I don't have the slides for this yet, but I have samples of the actual team retrospective which I can share in person if required. (please ask If required) 


        The key differentiator in this approach is the goal is to build "winning and self organising teams" and not just focus on stort term fixes / tasks. It also enables the team to appreciate the principles of agile and help them see visibly what is being improved on and to what extent. 


        I am sure there is a lot of learning from is focus based retrospective to the teams and audience.