One little help for your next retrospective

We all know it: What to do in the upcoming retrospective? Once again the “Same procedure as every Sprint”? Beside the all known literature where do I find a good inspiration?

Check out the RETROMAT. It is a great tool that combines 87 Methods randomly chosen and considers thereby the structure of a  retrospective (Set the stage, gather data, generate insights, decide what to do, close retro). It is easy and very helpful way to get an idea for your next retrospective.

Give it a try: http://plans-for-retrospectives.com

 

What about the 4th question for the Daily Scrum?

According to the Scrum Guide the Daily Scrum comes along with three questions*:

1. What did I do yesterday that helped the Development Team meet the Sprint Goal?

2. What will I do today to help the Development Team meet the Sprint Goal?

3. Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

I observed many Daily Scrum which were like following: All three question have been answered, the Daily Scrum was finished. Check! But afterwards the team gathered to make the real plan for the day. In my eyes this is very weird. Actually these questions give the impression that the team is conducting a kind of a brief mission planning for the day. And that is absolutely right. But a mission planning needs to find an answer on a further and essential question:

4. Did we really find the best way to reach our goal for today or to reach our sprint goal?

So why not adding this fourth question to your Daily Scrum and giving the team the chance to conduct a real mission planning day by day?

 

*Thanks to Hendrik M. :)

The Sprint Goal – more than just a bunch of user stories

Today I want to share my insights about the sprint goal:

  • It is a short but complete sentence about the outcome of the sprint.
  • It is as specific as possible.
  • It is NOT just the amount of user stories.
  • It helps the team to stay on focus during the sprint.
  • It is allowed to edit user stories as far as they do not have an impact on the sprint goal.
  • The team is committed on the sprint goal and not on the user stories.

Here is a very easy sprint goal which we defined in one of my last sprint planning:

“In this sprint we want to have the first export of PDF-files”

What is your experience?

Insights of an Agile Coach's daily business

Folgen

Erhalte jeden neuen Beitrag in deinen Posteingang.