Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am the SM of a team and would like to know who should set the goal for the retrospectives


migration rejected from Nov 13 '15 at 18:11

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as too broad by MichaelT, GlenH7, JB King Nov 13 '15 at 18:11

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

I think you should provide a bit more detail. Don't know about all, but I am certainly unable to understand what problem this post targets. – Pankaj Upadhyay Sep 17 '11 at 17:02

The other answers here seem to take a pretty shallow approach to this. I tend to disagree. This meeting is the most important part of your improvement process so spending time to prepare it is well worth the time.

Finding the goal is your job (as the Scrummaster, Coach or facilitator). Use the sprint and team as input to find it. This is called the retrospective purpose. This should be a short sentence formulated as a question.

The purpose is what your meeting should focus on. It answers the question: What is the reason for this meeting?.

The purpose should be broad enough so it doesn’t constrain the team and still narrow enough to be useful. For instance, How can we work better? is too broad since it opens up too many possibilities.

There is more to this though, so you may want to check out a book about it or a course. It's also worth pointing out that the team is in charge of the meeting, so they may very well decide that they want to focus on something else. In which case you have to toss your idea away and go with theirs.