The Artima Developer Community
Sponsored Link

Agile Buzz Forum
Good Agenda's make Great Meetings

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Mark Levison

Posts: 877
Nickname: mlevison
Registered: Jan, 2003

Mark Levison an agile software developer who writes Notes from a tool user.
Good Agenda's make Great Meetings Posted: Oct 26, 2007 10:47 AM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by Mark Levison.
Original Post: Good Agenda's make Great Meetings
Feed Title: Notes from a Tool User
Feed URL: http://feeds.feedburner.com/NotesFromAToolUser
Feed Description: Thoughts about photography, software development, reading, food, wine and the world around us.
Latest Agile Buzz Posts
Latest Agile Buzz Posts by Mark Levison
Latest Posts From Notes from a Tool User

Advertisement

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.Agenda-small

 Its funny 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.

This post is part of the ongoing series: One year of Scrum - Lessons Learned.

The parts are:

  • Working at a Distance is hard
  • Good Agenda's make for great meetings This post
  • A great Product Owner is key
  • Embrace Failure
  • Build Trust first
  • Light Touch Leadership is required
  • Healthy builds matter

Caveat Emptor - if you 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.

If you enjoyed this post, subscribe now to get free updates.

Read: Good Agenda's make Great Meetings

Topic: Billions For Facebook? Previous Topic   Next Topic Topic: October Smalltalk Digest

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use