KIMBERLY ANDRIKAITIS
  • Home
  • Shop
  • Blog
  • AMA
  • Links
  • Resume
  • Contact

Adventures in Agile

Release Retrospective Considerations

7/1/2018

0 Comments

 
I like to schedule an 'as needed' Release retrospective with my teams for them to inspect the release from a holistic, big picture point of view. It's essential to pause from the nitty gritty of everyday coding/testing so they can review the release process and course correct/pivot if necessary.

The list below includes some questions that I ask the team to mull over, so they can pinpoint, assess and identify improvements.

Questions to consider: 
  • What were the major milestones in this release? 
  • Who were all the team members/roles, stakeholders, influencers? When did they join/leave?
  • What worked well in this release?
  • What were some “Ah Ha” moments?
  • What was frustrating for us?
  • What were our major distractions?
  • What do we still not understand?
  • How well do you think we did?
  • What practices do we want to keep or do again?
  • What can we throw away / what’s not working?
  • What are our ongoing problems?
  • What problems can we fix or escalate?
  • What 2 or 3 new things would we like to try?
  • What is our action plan for instituting these recommendations?

To save the team time and to allow for some serious juicy conversation, I will forward this list of considerations a few days ahead of time. 
0 Comments

Your comment will be posted after it is approved.


Leave a Reply.

    Author

    Just an agile-dork writing about dorky agile things.

    Archives

    January 2021
    May 2020
    April 2020
    March 2020
    January 2020
    July 2019
    April 2019
    December 2018
    September 2018
    August 2018
    July 2018
    June 2018
    May 2018
    April 2018

    Categories

    All
    Coaching
    Introspection
    Relationship Building
    Scrum Events
    Scrum Values
    Working Remote

    RSS Feed

Proudly powered by Weebly
  • Home
  • Shop
  • Blog
  • AMA
  • Links
  • Resume
  • Contact