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

6906RE: [scrumdevelopment] pigs vs chickens

Expand Messages
  • Kristan Vingrys
    Apr 5, 2005
      I understand that the customer should not talk in the stand-up meetings, but as a customer I sometimes find this is not pratical.
      When developers are starting to talk about an issue and are off track I feel that I should be able to speak up adn correct them. Or if they are discussing a problem and I have a potential solution by changing the requirement slightly, I also think I should speak up or in some cases I have some information about how the feature is going to be used which will help the issue.
      If as a Customer I cannot speak in a stand-up meeting and must wait until the end of an iteration before I can interact with the team, that seems wrong and not very agile.
      What is the best way to deal with this? Sometimes I keep quiet in the meeting and at the end seek out the people involved in a particular task so I can discuss the issue further. Is this how it should be handled, or should I just speak during the stand-up meeting but keep any chatter short and relevant to the current topics being discussed?
       -----Original Message-----
      From: David H. [mailto:dmalloc@...]
      Sent: Tuesday, 5 April 2005 5:59 PM
      To: scrumdevelopment@yahoogroups.com
      Subject: Re: [scrumdevelopment] pigs vs chickens

      On Apr 5, 2005 4:20 AM, w6rabbit <bwhite@...> wrote:
      > One thing we do differently, is that managers typically are not
      > allowed to speak.
      > We DO allow project managers to speak, but only about things related
      > to the product they are managing on.
      Speak where? In your daily Scrum?
      How do manage to finish in 15 minutes with all this chatter?

      > In short, we see them as part of our team.  They *don't* get to ask
      > questions of talk about purely manager things, like what someone else
      > is working on.
      If they are product owners toward your team they are not part of your
      team and will never be. If they have concerns or wish to add, prepare
      or come up with different ways of guiding your work, that is what the
      product backlog is for when it comes to goal changing issues. Apart
      from that they should of course be allowed to communicate with the
      team during the Planning meetings for each sprint. After that the team
      should be left alone and no longer disturbed.

      To Post a message, send it to:   scrumdevelopment@...
      To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...

    • Show all 43 messages in this topic