Deep dive into RETROSPECTIVES- how do we break the usual norms so that these reflections could be made thought-provoking ones!

schedule Mar 27th 05:15 PM - 06:15 PM place Esquire Hall

         Retrospectives are the primary learning, reflection and readjustment techniques on agile projects. A good Agile team is always striving to become better than before. And an effective retrospective enables the team to sieze its opportunity to improve! 

Retrospectives enable whole-team learning, act as catalysts for change, and generate action.

R-> Realize where you are and where you want to be

E-> Engage the teams in fruitful discussions

T-> Team work to build “We over I” attitude

R-> Relish the power of Inspect and Adapt cycles

O->Openness and Transparency to make retrospectives efficient and effective

In my view, this is not any new concept or a jargon the team needs to really master, but yes in reality sometimes it becomes challenging to keep the momentum lively all times! Over a period of time, we see these symptoms in a retrospective. 

R-> Repeated issues pop-up

E-> Engrossing & Engaging discussions are missing

T-> Team present virtually, loses trust.

R-> Routine stuff, nothing interests the teams.

O->Observably gets boring over time.

To catalyse conversations among team members, retrospectives need to be viewed from a different perspective. This presentaion talks about why the retrospectives efficacy fades off over a period of time and then talks about some very interesting techniques that I used with the teams to make these meetings lively!  Teams need to do out-of-box thinking and appreciate that these short gatherings need not  be done only by using the techniques or methods prescribed in the book but could be done by quoting some situational specific examples that would make the teams really think and speak!

 

 
6 favorite thumb_down thumb_up 11 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  1. 10 min - Talk about few key retrospective techniques-Fly High, Team Yann, Team Journey, Focus Focus etc that I have used,  I would explain the situation that I was posed with and what made me come up with that specific idea/technique for doing the retrospective. Give an option to the audience if they would like to select any of them specifically to practice.
  2.  45 min- exercise, Divide the audience into groups and do an actual retrospective and present.
  3. 5 min -Q&A

Learning Outcome

 The intent of this session is to generate a thought process among the auidence to come up with their own situational specific ways for holding these meetings.

Take away: Toolkit of retrospective techniques that can be used at work place. (not there in the book)

                  Learn some key tips of how a retrospective can be done effectively, by practicing them in the worshop.

Target Audience

Scrum practitioners wanting to learn effective techniques to make the inspect and adapt cycles effective!

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Dhaval Dalal
    By Dhaval Dalal  ~  7 months ago
    reply Reply

    Hi Madhavi,

        Can you convert this into a 60 mins workshop instead of a talk?  Workshop will be very involving for the audience, esp for a topic like retrospectives.  Please do give an outline of how the workshop would be run.

    thanks,

    Dhaval.

  • Madhavi Ledalla
    By Madhavi Ledalla  ~  2 years ago
    reply Reply

     

    Hi Dhaval,

      Thanks for your inputs. Yes, I can convert this into a workshop, but if I do it as a complete workshop I may not be able to cover all the techniques outlined in the presentation. I have added few thoughts for joint, release and distribute retrospectives also; I can quickly talk about these and point to the articles where we can find more information.

    What we can do is we can practice one technique as an exercise at the end of the session.  

    So the outline of the session would be something like this:

    1.      5 min - Introduction

    2.      30 min- Toolkit of few retrospective techniques (Situation specific)- not there in the book. While sharing the techniques I used, I would explain the situation that I was posed with and what made me come up with that specific idea/technique for doing the retrospective.      Some tips for doing the retrospectives

    4.      20 min- exercise, I would give a scenario and the audience can get divided into groups and do an actual retrospective and present.

    5.      5 min -Q&A

      Do let me know your thoughts on this; I would be glad to make this as a workshop.

     

    Thanks, Madhavi.

    • Naresh Jain
      By Naresh Jain  ~  2 years ago
      reply Reply

      Hi Madhavi,

      Thanks for being open to converting this to a workshop. Please go ahead and turn this into a workshop. Its perfectly fine not to cover all the techniques, just focus on the most important ones and do a 100% workshop on it (no theory required.)

      Also we would need a video from any past presentation to understand how you facilitate a workshop.

      Thanks for your consideration.

      • Madhavi Ledalla
        By Madhavi Ledalla  ~  2 years ago
        reply Reply

        Hi Naresh,

         Thank you for the suggestions, I am glad to hear from you and I have converted this session into a workshop as suggested. I did facilitate team and joint retrospective workshops during the coaching engagements, and also presented the same topic in Regional Scrum Gathering India 2014 and Agile Hyderabad 2014.But unfortunately these sessions were not recorded. But, I have pictures of the Regional Scrum Gathering India 2014 and Agile Hyderabad 2014 sessions; I have already shared these in the links section, I can share few more pictures of the sessions and retrospectives. All the pictures that I used in the presentation deck are the actual retrospective pictures that I facilitated with my teams.

        I did facilitate a game in Lean India Summit 2014, in Bangalore, a small snippet of that can be seen towards the end in one of the video that is uploaded in the YouTube (https://www.youtube.com/watch?v=EIYVTGfaD0M), please see from 56:20 sec onwards. Uploaded the same vedio in the vedio links section.

        So the proposed agenda would be :

        1.     10 min - Talk about few key retrospective techniques-Fly High, Team Yann, Team Journey, Focus Focus etc that I have used,  I would explain the situation that I was posed with and what made me come up with that specific idea/technique for doing the retrospective. Give an option to the audience if they would like to select any of them specifically to practice.

        2.      45 min- exercise, Divide the audience into groups and do an actual retrospective and present.

        3.     5 min -Q&A

         

        Thank you for the feedback, please do let me know if this outline is acceptable, I would be glad to take up any suggestions/feedback from the committee. Please let me know If you need any other supporting data, I would try my best to provide the same.

         

        Thanks, Madhavi.

         

         

  • Madhavi Ledalla
    By Madhavi Ledalla  ~  2 years ago
    reply Reply

    Hi Prasad,

      Yes, surely I would be sharing the impact of using the techniques I noticed with the teams. Please do let me know if you would like to know any other details.

     

    Thanks, Madhavi.

  • Prasad
    By Prasad  ~  2 years ago
    reply Reply

    Madhav

    Hope you will also bring some insights from actual usage of techniques and its impact ( before and after)

    ~PP

  • Madhavi Ledalla
    By Madhavi Ledalla  ~  2 years ago
    reply Reply

    Hi Jerry,

      This topic is going to focus on the various techniques (process) that can be used in the "Gather Data Step" of the retrospective course, so that the teams can wear a diffirent thinking hat and come up with good data points for discussion. Hope this helps!

    Thanks, Madhavi.

  • Jerry Rajamoney
    By Jerry Rajamoney  ~  2 years ago
    reply Reply

    Hi Madhavi,

    Thanks for this topic. I have the following query based on the topic outline. Is this topic is going to focus on the process of doing a retrospective or the people and their behaviour perspective too?

    Thanks,

  • Madhavi Ledalla
    By Madhavi Ledalla  ~  2 years ago
    reply Reply

    Hi Joel,

       I have cleaned up the slides, updated the presentation deck and uploaded it back. Do let me know if you have any queries/suggestions. Would be glad to answer them.

     

    Thanks, Madhavi.

  • Madhavi Ledalla
    By Madhavi Ledalla  ~  2 years ago
    reply Reply

    Hi Joel,

     Thank you for the feedback. Yes, surely. I would clean up all the slides. I would be adding few more techniques to share with the audience. In short, my slides would have only the picture of the technique and I would explain the process of using it with the teams.

    Thanks again for your comments. I would be glad to answer any further queries.

    Regards,

     

    Madhavi.

  • Joel Tosi
    By Joel Tosi  ~  2 years ago
    reply Reply

    Hi Madhavi,

         I like the submission, retrospectives are something a large number of teams struggle with, especially over time.  Your slides show this is well thought out.  The only thing I would offer up is that there are so many words on your slide, during a presentation people would spend too much time reading and not enough time listening.  Is that something you are comfortable cleaning up some?

    Best,

    Joel


  • Liked Nanda Lankalapalli
    keyboard_arrow_down

    Nanda Lankalapalli - Happy Teams are key to successful agile transformation– Teams’ self-design

    Nanda Lankalapalli
    Nanda Lankalapalli
    Agile Evangelist
    Independent
    schedule 2 years ago
    Sold Out!
    45 mins
    Experience Report
    Advanced

    Agile Teams' self-design is very important (though not very common) exercise in a large-scale agile transformation. In teams’ self design, team members choose their own teams in a collaborative way. This concept here is that the teams will gel quickly and excel when they are self-designed.

    In this session I am going to present my experience with such exercise. I facilitated at least 4 such sessions to help an organization as part of a large-scale transformation. The session is going to explain

    1. Benefits of Feature teams over Component teams
    2. Self-design of feature teams
    3. Pilot exercise of self-design of 2 feature teams.
    4. Large scale self-design of 4 product groups with 30 to 50 members per group.

     

  • Liked Krishnamurty VG Pammi
    keyboard_arrow_down

    Krishnamurty VG Pammi - 6 X 2 Planning Errors in Scaled Agile Delivery Model

    Krishnamurty VG Pammi
    Krishnamurty VG Pammi
    Agile Coach
    IVY Comptech
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    2 major errors across 6 agile planning events give us 12. Learning “what not to do”, can sometimes help us identify risks early in the cycle so that, as a team, we can effectively respond to these risks.

    Agile planning happens at multiple levels. In scaled agile delivery model, effective outcome of one planning event can influence the other significantly either positively or negatively.

    Come and learn top 12 experiential insights. These will help you alert your teams on “what not to do” during Scaled Agile Planning events. I tried capturing top 12 errors across 6 planning events namely Strategy Planning, Portfolio Planning, Product Planning, Release Planning, Iteration Planning and Daily Planning.

  • Liked Vijay Bandaru
    keyboard_arrow_down

    Vijay Bandaru - Scrum Master Experience Report

    Vijay Bandaru
    Vijay Bandaru
    Agile Coach
    IVY Comptech
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    This presentation brings a different perspective for the Scrum Masters and helps them to become more powerful Scrum Masters through their enhanced soft skills. I am going to cover how the teams evaolve, how the change is resisted, how the teams behave, how Scrum Master can handle all these effective to make the teams deliver working software every sprint continuously.

    The information explained below is from my experience as Scrum Master and Coach. Below are the points that will be covered in the presentation:

    Primarily I am planning to cover the anti patterns that will push the teams back and where the Scrum Master can support the teams with his knowledge, experience and interpersonal skills. For example please find below some scenarios:

    1. In effective sprint planning: Team might miss some of the tasks while doing the sprint planning part 2 so they will anyway identify them during the development of the stories so these tasks take additional time which is not budgeted. So they will have to miss some stories which will impact the sprint goal. So I encourage the scrum masters to collect all such unidentified tasks on a separate colr sticky notes and during retrospective discuss with the team to see how much % of the capacity is gone for that tasks. At the same time are there any tasks in that list can be repeatable tasks (Eg: Code review) so this will help the team to come up with a tasks checklist which will help the teams to do effective sprint planning part 2 

    2. Partially ready stories pushed into the sprint: Sometimes product owners push the stories that are not fully ready and the team cannot say "No" in this case either the story gets changes during the sprint or it cannot be finished due to unknown factors. So Scrum Master to encourage the team to have a proper DOR (Definition of Ready) and get a working agreement between the PO and team so that they will work around it whilst they understand "Responding to change over following a plan"

    3. Cross functional behavior: Team generally does not want to become cross functional because they are fine with what they are. Scrum Master has to bring a change in their thought process and get them agreed to become cross functional. For this it takes time so SM has to also manage the management expectations with respect to set the expectation in the dip in productivity

    4. Pale retrospectives: This is another area where Scrum Master has to provide support to teams and get the liveliness and make the teams high performance teams

    5. Timeboxing: Most of the teams do not respect this important guideline. Again SM has to get the importance of this characterstic in to the teams and get them aligned towards this. So there are some examples which I can quote such as if different people arrive at different timings, how much time is wasted and how many times we need to recap on the points already discussed, how much gap created etc

    6. Stop starting and start finishing: This will cover to complete the stories/tasks that you are working before you pick up something. In general the teams pick up many items at a time and complete them close to 100% but not 100% so this will impact the sprint goal. In such case the SM has to provide inputs to the team to pick as few as possible but close them as soon as possible so this way the value delivery at the end of sprint is guaranteed

    7. Lack of importance for quality: In the hurry of completing the stories the team at times give less or no importance to the quality. So the probability of escaped defects or getting rejection for the stories is high. So the Scrum Master has to educate the teams to strictly define/refine/follow the Definition of Done for each story. I saw many teams having their DOD in the tools like VersionOne but not infront of their eyes. 

    8. I know when I see it: Information radiators. This will be the key for the teams to adjust their pace as per the principle #8. So creating big visible information radiators and updating the underlysing details frequently will bring attention in the team and they naturally tend to adjust their delivery mode as per the requirement 

     

  • Liked Vijay Bandaru
    keyboard_arrow_down

    Vijay Bandaru - Lean and Kanban Implementation from Trenches

    Vijay Bandaru
    Vijay Bandaru
    Agile Coach
    IVY Comptech
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    I was part of a Large Scale Agile transformation in my organization and I was one of the Agile coaches there. As part of transformation we have created LeanOps teams to manage the technical debt, production incidents with a focused concentration. This article covers the following:

     

    - Why the trasnformation required?

    - What are the structural changes implemented?

    - LeanOps inception

    - Lean Ops working Model

    - Challenges with the LeanOps

    - How we addressed those challenges?

    - Goal oriented approach

    - Q & A

  • Liked Devesh Chanchlani
    keyboard_arrow_down

    Devesh Chanchlani - Case Study - When the estimates were accurate ..

    60 mins
    Case Study
    Intermediate

    This talk deals management's perspective into measuring progress. As an orthodox practice, many times they would like to measure it in terms of amount of work done (in hours). As part of this interesting case-study, we would explore if it is the right perspective and how it affects teams, and what scrum brings to the table.

  • Liked Vijay Bandaru
    keyboard_arrow_down

    Vijay Bandaru - A retrospection on a Large Scale Agile Transformation

    Vijay Bandaru
    Vijay Bandaru
    Agile Coach
    IVY Comptech
    schedule 3 years ago
    Sold Out!
    60 mins
    Case Study
    Advanced

    This is a case study prepared based on a large scale agile transformation happened at a product based company with over 5000 employees across 5 different locations. The transformation journey started with a clear vision and a timeline. There was a detailed plan and management buy-in for this transformation. I am presenting the key details of the transformation in this case study. This case study covers the critical activities carried out as part of the transformation and what went well and what went wrong during the transformation.

    “Challenges” are to be expected in any rapidly changing enterprise in a dynamic and exciting market, and they must be addressed to survive and thrive. The enterprises which stand out and set an example to the rest are the ones which handle these challenges in a different way leaving the foot prints for others to adapt these good practices and benefit out of them.  Healthy organizations continuously learn and re-invent themselves to go from good to great, and this is what we are striving to do.

     This is a practical Agile Transformation case study of an organization.  Our key drivers for change include:

    • Improve platform and gaming availability
    • Reduce feature cycle time
    • Reduce defects in production
    • Develop flexible, multi-skilled teams
    • Produce high value features first
    • Enhance cross site business collaboration

    We started our agile journey during September 2013.  In the presentation the following points would be covered:

    - Why did we choose transformation?

    - What was our roadmap of transformation?

    - What was our approach towards the transformation?

    - What were our challenges during the transformation?

    - Solutions to the challenges that we faced during the transfformation?

    - What tools we have selected?

    - What are the outcomes of the transformation?

    - What is our current status and what is remaining?

    - Any questions and answers

  • Liked Krishnamurty VG Pammi
    keyboard_arrow_down

    Krishnamurty VG Pammi - Role of Scrum of Scrum meetings in achieving Transparency and Speed - Experiential insights on what it takes to reflect “shared team goal” in scaled agile framework

    Krishnamurty VG Pammi
    Krishnamurty VG Pammi
    Agile Coach
    IVY Comptech
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Are you in need of stepping up “Transparency” & “Speed” in your scaled agile framework? Are you experiencing the difficulty that most of your scrum teams are focusing on their individual team specific goals and thus missing “whole-team” thinking towards “Shared Project goals”?

    Learn our practical case study on how our teams could able to establish “Transparency and Speed” through realizing the connect among our “Daily Scrum”, “Scrum of Scrum”, “Scrum of Scrum of Scrum” events on a happening project that comprises of 18 scrum teams belonging to 10 business components located at 4 different countries.

    Experience how our teams are able to instil the sense of urgency among the virtual teams and understood the noble purpose/role of “scrum of scrum” events in resolving cross site dependencies promptly through our 3 step framework “Plan, Perform and Adapt”

    (1)    Plan:  Easy to use planning practices adopted by our teams to make our scaled “scrum of scrum” agenda simple and relevant.

    (2)    Perform: Ground level challenges resolved by our teams and how our team could able to implement the agenda set in achieving transparency, speed and thus quality.

    (3)    Adapt: Practices our team implemented in responding to the change and adopted “whole team thinking” in achieving“ shared project goals”

    Scrum of Scrum events helped our team progress quickly and easily. Our team could able to coordinate and integrate their work effectively. The interesting thing is that our teams could able detect the risks early in this game and came up with apt response strategies to address them.  

    Keeping the discussions short and focussed in these events comes with practice and preperation. Our teams are kept current with “cross team dependencies”, “Risks with response plan”, “Issues and their progress” and “number of added stories and defects since we last met”.  Our teams leveraged Visual communication channels when it comes to “scrum of scrum of scrum” across different sites.

    Come and experience our case study and take-a-way “useful” learnings to make your scaled agile project achieve “Transparency”, “Speed” and thus “Agility” with teams reflecting “whole-team thinking” and working for “Shared project goals day after day….

  • 60 mins
    Talk
    Advanced

    There is a world of difference between the management principles in the era of the Industrial revolution to the current world of information revolution. We need to acknowledge the increasing gap between the way employees are being managed at work, and the way they want to be managed. Many surveys have been done in this area, ending in headlines like “6 out of 10 employees are miserable” and “74 percent of staff not engaged at work.” Dig into these surveys and you’ll see the quality of leadership on top of the list of complaints. The poor state of leadership and management skills in organizations is being driven by a broad range of factors, including but not limited to

    The changed nature of work - More of skill and innovation

    The increasing education of employees - Continuous improvement and learning needs

    The needs of later generations - The more sofisticated needs of the system

    The pace of change - The quick pace of changes

    In the current “rat race”, the management focusses on higher productivity and higher ROI, but they lack the capacity to “motivate” their employees that can take them to the next level of thinking. The "leaders" do not understand the subtle difference between teaching, mentoring and coaching. They use these words interchangeably without realizing that coaching teams can help them to increase the productivity, morale and create great employees resulting in more successful products.

    A new coaching model is required to enable continous improvement with quick feedback cycles that fosters adaptability and innovation.

    Two relevant quotes which I can relate to this issue are

    "It is people who build organizations and not organizations who make people" - unknown

    "Beware of little expenses; a small leak will sink a great ship" - Benjamin Franklin

     

  • Liked Madhavi Ledalla
    keyboard_arrow_down

    Madhavi Ledalla - Will Scrum alone create miracles! Or does it need some best buddies…..Let us understand through a real team story!

    Madhavi Ledalla
    Madhavi Ledalla
    Agile Coach
    ADP
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Summary of the presentation :

    Scrum is a framework. It just suggests some good practices which are like guidelines similar to the good-to-do things. These practices keep the system moving and are like driving directions that enable us to have a healthy rhythm. Now how is this rhythm of scrum affected by the behavioural ecosystem? The blend of people right from the top management to ground level get affected by this adoption of Scrum and also influence the scrum adoption to a greater extent. This adoption is a journey, and Scrum aids in making this entire journey enjoyable and valuable, of course we need to add some ingredients and some spice to it to make this adoption journey valuable and fun-filled. So in this presentation we would talk about the powerful roles in Scrum and most importantly how to make the environment around it suitable to have a smooth ride.

    This case study is created based on a real journey of the team and the team is still continuing their scrum journey.

    This case study highlights the following.

     Background information
           Project Kick off
           Criticality
          Initial Expectation
          Final Outcome
     Role of organization top-management in this journey?
     How to handle the most important resource-“PEOPLE” in the Scrum journey?
     Some effective ways to clean up the chaos that scrum exposes?
     Learn what are the key ingredients of Scrum?
     How do we spice it up to make the ride a fruitful happy ride?
     Some creative and innovative ways to make the ride a fun and valuable ride!
     How can the master chef, the Scrum Master make this journey a success?
     How to churn the teams to become great teams!

     PS: I can submit a detailed report based on which the slide deck is created to the reviewers. Thank you.

    Agile adoption journey is very challenging and expensive but yet would yield great results if we do it in a proper phased manner with good planning and insight. Scrum, one of the agile methodologies, helps the projects to cater to the dynamics of changing market while delivering high quality software when combined with few engineering practices.

    True! Let us try to understand the ground realities of scrum and then see how its adoption gets effected by the surrounding ecosystems and environment using simple metaphors and then let us take a deep dive into the depth of the realities. Scrum is like a powerful filtration process that allows the filtrate to pass through smoothly while exposing the residues which are the real bottlenecks, impediments, road blocks in a transparent manner. Once these residues are cleared, crystal clear increments of working software could be seen by the Stakeholders. So it is up to the environment around Scrum to act on the realities that Scrum exposes and clear it up as early as possible so that the working software could be delivered faster. If we do not react to these impediments that Scrum exposes, we would be where we were earlier and nothing might get changed!

    Successful implementation of Scrum would need the key ingredients, which are the robust engineering practices like Continuous integration, Daily Builds, Automated build process, Build notifications, Continuous Deployment and Delivery in place to deliver quality software.

    We need to enable and empower the most important resource, “PEOPLE” very carefully all through the journey so that they do not get over churned and break half-way through the ride. We need to add just enough lubricant to make the team vehicle move smoothly. Organization plays a vital role in giving the necessary push as and when required by providing the essential support in terms of the infrastructure and other requirements that would aid the Scrum journey. People who have a positive attitude and who are willing to work with the team on the ground would sustain this adoption process. People who try to create roadblocks along the journey should be handled with care skilfully.

    Now to make the journey really a fun-filled ride, definitely some spice in the form of creativity and innovation is needed to produce the flavor to make scrum tour amazing and an exciting journey that churns good teams to great teams. The three roles of Scrum, the Product Owner, the Scrum Master and Development team should synchronize well with each other to succeed. Most important role in Scrum, the master chef i.e the Scrum Master keeps the Scrum team intact by ensuring that all the ingredients and spices are in proper ratio. The Scrum Master is the magic wand behind the scenes that can enable things really happen.

    The above points would be revelead by going through the journey of a  scrum team that I worked with.

     

  • Liked Sreedevi Vedula
    keyboard_arrow_down

    Sreedevi Vedula - The Practical Pyramid

    Sreedevi Vedula
    Sreedevi Vedula
    Quality Analyst
    ThoughtWorks
    schedule 2 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    An Ideal Test Pyramid is an invaluable technique to succeed with agile. However, it is challenging to have this ideal pyramid in practical projects for several conditions in the projects, like legacy code bases. To have a good test pyramid, several best practices of software development need to be followed. This talk discusses the practices that help in implementing test pyramid and the challenges faced by many teams in doing that and suggestions on how to overcome them.