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

Re: ScrumMaster's role

Expand Messages
  • davenicolette
    +1 to the group s consensus about the article.
    Message 1 of 19 , Apr 4 1:37 PM
      +1 to the group's consensus about the article.

      --- In scrumdevelopment@yahoogroups.com, "Tobias Mayer" <tobiasgmayer@...> wrote:
      >
      >
      > Leave it to Mike to call a spade a spade :-)
      >
      > Most people here seem to agree that the Scrum Master is no kind of
      > liaison or conduit to anyone. I'd like to add that there are no
      > conduits at all in Scrum. A couple of posts have suggested that the PO
      > is a conduit between team and customer. Bad idea. I have seen this
      > happen, and it is generally a disaster. What we end up with is a
      > disempowered, go-between PO afraid to make any decisions for fear of
      > making the wrong one. We end up with a person who has all the
      > responsibility (single wringable neck -- I hate that term) and no
      > decison making ability.
      >
      > The extract Amr posted here from the article does, as Mike, Dan and Jim
      > suggest, show a rather non-Scrum mindset. It is very, very difficult
      > sometimes for people to fully grasp Scrum -- that it is not simply a
      > veneer over existing ways of working. It is an entirely new way of
      > thinking.
      >
      > Tobias
      >
      >
      > --- In scrumdevelopment@yahoogroups.com, mike.dwyer1@ wrote:
      > >
      > > This smacks of a PMBoK mindset and Dan, Jim and others are being too
      > kind
      > > Sent via BlackBerry by AT&T
      > >
      > > -----Original Message-----
      > > From: Dan Rawsthorne dan.rawsthorne@
      > >
      > > Date: Wed, 01 Apr 2009 18:42:24
      > > To: scrumdevelopment@yahoogroups.com
      > > Subject: Re: [scrumdevelopment] ScrumMaster's role
      > >
      > >
      > > I don't like it. For one thing, the PO doesn't need a liaison to the
      > > team, the PO is part of the team and does most of the stuff described
      > > here himself. Second of all, the SM doesn't work for the PO, the SM
      > > works for the team. I teach that one of the major responsibilities is
      > to
      > > help the relationship between the PO and the rest of the team, and
      > being
      > > under the PO's thumb (as it is described here) doesn't seem helpful.
      > >
      > > Dan Rawsthorne, PhD, CST
      > > Senior Coach, Danube Technologies
      > > dan@, 425-269-8628
      > >
      > >
      > >
      > > amr_samadisy wrote:
      > > >
      > > > One of the articles under review for the upcoming issue of the agile
      > > > journal describes the ScrumMaster's role as follows:
      > > >
      > > > the ScrumMaster's duties to the Product Owner are more clearly
      > > > defined and limited in scope. Rather than "putting fires out,"
      > the
      > > > ScrumMaster's support work with the Product Owner tends to be
      > more
      > > > easily anticipated and performed on a regular, ongoing basis. In
      > > > essence, this work can be summarized as assisting the Product
      > > > Owner with various preparatory activities. These often include
      > > > updating the Product Owner about the team's progress and
      > > > successes, assisting in the preparation of the backlog for
      > sprint
      > > > planning (also known as backlog grooming), and radiating
      > important
      > > > status updates to all team members and stakeholders.
      > > >
      > > > In many ways, the ScrumMaster's role in regard to the Product
      > > > Owner can be seen as a kind of liaison for the team, reinforcing
      > > > its communication with the Product Owner. As such, he or she is
      > an
      > > > essential hub for communication, working to make sure that
      > > > everyone involved in the project is on the same page.
      > > >
      > > > That is not my understanding - in fact, that sounds like a problem
      > and
      > > > advice I wouldn't want to give to the readers. At the same time, I
      > > > realize that there are many opinions/definitions/etc... of how Scrum
      > > > really should work. So, I'm doing some due diligence and fact
      > > > checking. Does this description sound right to you?
      > > >
      > >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.