My talk will revolve around the retrospectives and the concept of Futurospective. We do retrospective to inspect what went wrong and what went good to continue. We do retro after the sprint is over. Can't we do a FUTUROSPECTIVE during the sprint to figure out what all can went wrong, so as we can lay down a list of activities which we feel can go wrong and we can take preventive measure in advance so as to avoid them. Prevention is always better than cure.

My talk will have :

>> Retrospectives and its effectiveness

>> Futurospectives

>> A Small game

 

 
0 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

>> Benefits and Importance of Retrospectives

>> Continuing Retrospectives

>> What Futurospective is?

>> How and when to do it?

>> Game

Learning Outcome

>> Benefits and Importance of Retrospectives

>> Continuing Retrospectives

>> What Futurospective is?

>> How and when to do it?

 

Target Audience

PO, Scrum Master, Developers and all who do or are present in Retrospectives

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Tathagat Varma
    By Tathagat Varma  ~  3 years ago
    reply Reply

    Anju - do you have data points, either from literature or from your own experiences, that help you strengthen the hypothesis to support premortem? While at a conceptual level, I agree that premortem is an interesting concept, and that prevention is always better than cure, it would be great to have that backed by some real-world examples. 

     

    regards,

    TV

    • Anju Gahlawat
      By Anju Gahlawat  ~  2 years ago
      reply Reply

      Hi TV,

      Yes I will be sharing my personal experience which we are currently using in our project. Apart from this I have few references to the surveys and studies done across to strengthen my viewpoint.

       

      Thnx