• Skip to main content
  • Skip to footer

Agile Pain Relief Consulting

Scrum and Agile Training and Resources

  • Certified Scrum Training
    • Certified ScrumMaster (CSM) Training
    • Advanced Scrum Master Certification (A-CSM)
    • Certified Scrum Product Owner (CSPO) Training
    • Certified Scrum Developer (CSD) Training
    • Private Scrum & Agile Training
      • Agile Foundations Private Training
    • Choose the Right Scrum Training for Your Needs
    • FAQs and Policies
  • What Is Scrum
  • Free Resources
    • A Jargon-Free Introduction to Scrum
    • *NEW* Agile Glossary and Reference Library
    • The Guide to Effective Agile Retrospectives
    • Online Agile Teams Game (Beta)
    • Five Steps for Creating High-Performance Teams FREE ebook
    • Foundational Scrum Free Learning Series
    • The Story of a Sprint
    • Free Virtual Scrum Meet-Up
    • Get Scrum Education Units (SEU)
    • Articles & Interviews
    • Newsletter
  • Blog
    • Scrum by Example – Stories for the Working ScrumMaster
    • Beyond Scrum Blog Series
    • Scrum Anti-Patterns – How We Hold Back Our Scrum Teams

Good Agendas Make Great Meetings

October 26, 2007 by Mark Levison 3 Comments

Agenda - image licensed from Photodune
At Agile 2007, I attended Jean Tabaka’s “Why I don’t like Mondays”. In this session, Jean emphasized the importance of a meeting purpose and agenda. At the time I thought “Well my meetings use the standard Scrum agendas and we get a lot of value out of the meetings.” Wow was I ever wrong. I bought Jean’s book Collaboration Explained and found a revised set of Agendas.

It’s fun to compare the standard review and retrospective agenda

  1. The team demos the product.
  2. What went well? Often a round robin.
  3. What went poorly? another round robin.
  4. What could we improve next time? yet another round robin.

Stunningly we discovered only the obvious issues and did little to fix them.

Compare with what we use now:

Purpose: To demonstrate potentially shippable functionality completed by the team during the sprint, to update the Product Backlog based on the demo and to learn about team practices to keep, change or add.

Outputs: Updated Product Backlog with new items and priorities, any new team practices, recommendations for the next sprint.

Ground Rules:

  • The core point is to show respect for your fellow team members.
  • No email or surfing the web.
  • No side conversations (via IM etc)
  • No cellphones or blackberries
  • Join the meeting on time (Global Crossing issues aside)

Agenda for the Review and Retrospective:

  1. What was our commitment for the sprint?
  2. What was our final set of completed items?
  3. What is our demonstration of these items?
  4. What was our final burndown chart?
  5. What did we learn about our estimates?
  6. What changes are there in the Product backlog items, priorities or estimates?
  7. What documented issues/concerns were we able to address? (i.e. from our last retrospective).
  8. What are our current issues/concerns?
  9. What worked well that we’d do again?
  10. What practices would we alter or drop?
  11. What new practices would we want to introduce next sprint?
  12. Based on our last two weeks work what appreciations do we have for individuals? In/outside the team someone who had a particularly valuable affect on our success.
  13. What is our Action Plan?
  14. Have we met the purpose we set out today?

What a difference – we discover new problems and since we have an action plan with people responsible for each item. Things tend to get done. Wow.

To quote one of my team members “the old review and retrospective agenda didn’t help remind her what happened and where we ended up. By breaking things down into smaller more focused chunks the new agenda (and prompting questions) has made our retrospectives more valuable”. Another has said that finally the planning meetings leave them with confidence that we’ve planned well. I just feel ashamed for having taken so long to discover I was running bad meetings.

The agendas in Jean’s book Collaboration Explained also include prompt questions – which help focus peoples minds on the question. Finally I will add that the agendas (she covers Scrum, XP, Crystal) are only a handy appendix at the end of an amazing book. My copy is dog eared.

Caveat Emptor – if you buy Jean’s book after clicking on my link I get 4% of the price. Buy many copies so I can afford to replace my worn out copy.

Image via: https://photodune.net/
Mark Levison

Mark Levison has been helping Scrum teams and organizations with Agile, Scrum and Kanban style approaches since 2001. From certified scrum master training to custom Agile courses, he has helped well over 8,000 individuals, earning him respect and top rated reviews as one of the pioneers within the industry, as well as a raft of certifications from the ScrumAlliance. Mark has been a speaker at various Agile Conferences for more than 20 years, and is a published Scrum author with eBooks as well as articles on InfoQ.com, ScrumAlliance.org an AgileAlliance.org.

Filed Under: Software Development Tagged With: Agendas, Agile, Agile Retrospective, Jean Tabaka, Scrum

About Mark Levison

Mark Levison has been helping Scrum teams and organizations with Agile, Scrum and Kanban style approaches since 2001. From certified scrum master training to custom Agile courses, he has helped well over 8,000 individuals, earning him respect and top rated reviews as one of the pioneers within the industry, as well as a raft of certifications from the ScrumAlliance. Mark has been a speaker at various Agile Conferences for more than 20 years, and is a published Scrum author with eBooks as well as articles on InfoQ.com, ScrumAlliance.org an AgileAlliance.org.

Reader Interactions

Comments

  1. Anna Forss says

    October 27, 2007 at 4:48 am

    Started to read your blog a couple of weeks ago. We started our agile project in January and it’s so nice to feel we’re not alone with our discussions.

    Reply
  2. Jeremy Crosbie says

    October 30, 2007 at 11:54 am

    Another good book is _Agile Retrospectives: Making Good Teams Great_ (https://www.pragprog.com/titles/dlret). I found this book very helpful in that it gives you ideas on how to mix-up the agenda of a retrospective, otherwise I find they become rote and rapidly lose their value.

    Something that is important to add to the agenda is a review of the previous retrospective’s action plan and determine if the plan was met, why/why not, etc.

    Reply
  3. mandy says

    July 1, 2010 at 1:57 am

    Great! I have been using the old style of retrospective, and tired of it. now I can try to use your new items . and hope can find the problems in our team.

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Footer

  • Certified Scrum Training
  • Private Training
  • Effective Agile Retrospectives
  • Agile Reference Library
  • About Us
  • FAQs and Policies
  • Sitemap
  • Partners

Contact Us


Follow Us

  • LinkedIn
  • Mastodon
  • RSS


Subscribe for Scrum & Agile news and more resources





© 2011–2024 Mark Levison & Agile Pain Relief