Loading ...
Sorry, an error occurred while loading the content.

56651Re: [scrumdevelopment] Questions about shifting from traditional project management to SCRUM

Expand Messages
  • Nirmala Jegadheesan
    Feb 27, 2013
        In practical situations, the Scrum Master cannot stop from just advising the team. When the team is new and immature regarding the agile processes the Scrm master should do some hand holding until the team sets itself on the roll. Usually the Scrum Master organizes the retrospective meetings and track the decsions if implemented properly within the team. When there is a new process coming up, the PMO team should take up these roles inorder to mingle with the team and the process.

      From: Ron Jeffries <ronjeffries@...>
      To: scrumdevelopment@yahoogroups.com
      Sent: Wednesday, February 27, 2013 1:52 AM
      Subject: Re: [scrumdevelopment] Questions about shifting from traditional project management to SCRUM
      On Feb 24, 2013, at 8:03 AM, Nirmala Jegadheesan <jnirmala@...> wrote:
      Either a project or a product the team would require a SCRUM master who actually does the "Project Controlling " part. Hence based on the project style the PMO members can get distributed among the SCRUM teams and take up roles like SCRUM MASter, Product owner or Retrospective Handler. But in all the cases, the involvment given by the PMO team in SCRUM methods would be more deeper and clearer than when you have performed in tradional methods. Can explain in detail if you have more questions.

      I don't understand. The ScrumMaster is not supposed to do any "controlling" as far as I know. And I'm not aware of the role "Retrospective Handler" at all.

      Ron Jeffries
      I'm not bad, I'm just drawn that way.  -- Jessica Rabbit
    • Show all 13 messages in this topic