For this ATQ, Ben Linders helped me out with the questions.

1) When do you normally do a retrospective?

a) Just before the start of a sprint, to prepare everything that is needed to do the sprint
b) After the sprint review of each sprint, when you have all the input that is needed to reflect and decide upon actions
c) As a servant leader you only do it when the team asks for it, and as often as they think they need it
d) The retrospective is a part of the sprint review, where you reflect on the product and the process
e) Between the planning game and the sprint review, so that you can do improvements during the sprint

2)  Who should attend the retrospective?

a) All team members
b) The scrum master and some of the team members
c) Everybody in the team, except for the product owner
d) Everybody who is attending the sprint review, to get as much feedback as possible
e) The product owner, team members, and their managers

 

3) What is the best way to do a retrospective?

a) There are many good ways to do retrospectives, the facilitor usually proposes a way to do it depending on the team needs and the issues at hand
b) You can use the the four key questions from retrospectives, as a minimum ask the team what went well and what should be improved
c) There is no best way to do a retrospective, as the purpose of a retrospective varies in agile projects
d) Team members should submit problems before the retrospective, and the scrum master decides what is most urgent to discuss
e) Most teams use sticky notes to collect actions what should be improved

4) What happens with the actions that come out of retrospectives?

a) They are given to the project manager so that (s)he can plan the actions and assign people
b) Team members will pick up these actions during the next sprint, to continuously improve their way of working
c) The scrum masters collects them and documents them in a report
d) There shouldn’t be much actions coming out, as the next sprint is already filled up with user stories
e) They are documented, and will be discussed in the next retrospective to check if they are finished

 Please add your answers in the comments and on monday I’ll publish Ben’s answers.







7 Responses to “Agile Thursday Quiz: Retrospectives”

  1. Guy says:

    1.b, 2.a (in some cases c, depends on the relationship between team and PO), 3.a, 4.b is optimal, though I can’t say I haven’t seen e or c…

  2. Irene says:

    Yeah, my favourite quiz is back :)

    1 b and d: Not sure what the implications are of saying it’s part of the review or comes after it. I think it’s important to do it at the very end of the sprint to get as much input as possible and before the start of the next sprint so you can plan resulting actions for the oncoming sprint.

    2 a and possibly d: We usually had the PO in the retrospective as well because his job is part of the process, too. However it’s important that the team is safe to speek freely. If the presence of the PO makes team members shut up then he should only be invited when the team decides they need him to improve the process/product.

    3 a, c and b

    4 b and e

    Looking forward to Monday!

  3. yhanoulle says:

    Irene: I’m continuously looking for new quizes, yet I get very slow response. so if you are inspired to write one, feel free..

  4. Carl Shaulis says:

    1. b
    2. a
    3. a
    4. b

  5. [...] week I published the Agile Thursday Quiz about Retrospectives. Here are the answers from Ben Linders. (who created these [...]

  6. Robin says:

    What are the answers?

  7. Gerald says:

    IMO.
    1. b,e
    2. a
    3. a,b
    4. b


Leave a Reply