Forums

By posting to our forums you are agreeing to the Forum terms of use.
Answer
Last Post 26 Jul 2013 08:43 AM by JamesHobson. 5 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
don.enzo
New Member
New Member
Posts:4
don.enzo

--
02 Jul 2013 08:14 AM
    Hi everbody,

    who can answer me about this question :

    A Scrum Master is introducing Scrum to a new Team. The Team has decided that a retrospective is unnecessary. What action should the Scrum Master take?

    A) discuss with product owner

    B) do what self organising team say

    C) begin doing retrospectives

    D) tell management

    Thank you a lot.
    don.enzo
    New Member
    New Member
    Posts:4
    don.enzo

    --
    03 Jul 2013 03:49 AM
    Hi again,

    nobody can answer about my question ???? Please.....

    Thanks !!!
    Romain Trocherie
    New Member
    New Member
    Posts:14
    Romain Trocherie

    --
    03 Jul 2013 06:34 AM
    Hi Fabio,

    The retrospective is a core part and necessary ceremony. As such, the Scrum Master has to ensure they are done properly and make them productive.
    don.enzo
    New Member
    New Member
    Posts:4
    don.enzo

    --
    03 Jul 2013 07:05 AM
    Thanks !!!!
    Don Enzo
    New Member
    New Member
    Posts:1
    Don Enzo

    --
    04 Jul 2013 01:42 AM
    Hi again,

    Some people told me the Scrum Master can not require to The Development Team. That's why his answer is :
    "do what self organising team say "

    Wthat do you think about that version ?

    Thanks.
    JamesHobson
    New Member
    New Member
    Posts:4
    JamesHobson

    --
    26 Jul 2013 08:43 AM
    The purpose of the scrum master is to ensure make the scrum process work. In my opinion the correct answer isnt given, which is to identify why the team does not see the value of a retrospective and to sell it to the team as a concept. It could be that the retrospectives are being handled badly and too slow, for example, whihc can be addressed.

    Lacking that as an option, I would go for "start doing retrospectives".

    The team is self organising, but are not anarchists, they are self organising within the framework of scrum. That means they can make changes and optimisations, and the detail of their work is not dictated from above, but it does not mean that they can exclude siginficant parts of the process.
    You are not authorized to post a reply.


    Feedback