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

57149Re: [scrumdevelopment] Concept of "work ahead" team

Expand Messages
  • srinivas chillara
    Aug 27, 2013
      Hello Richard,
      Quite right you are. A sub-team (of a chosen few) which regularly does this tends to form a unspoken (maybe even spoken) hierarchy which is best avoided. 

      However, sometimes it is difficult to get everyone in on these "work ahead" sessions/meetings.
      So we can rotate people in/out of this. A good ScrumMaster will facilitate this (possibly using some form of volunteering). In addition a good Scrum Master can keep an eye out for problems that may be originating from the "work ahead" team. 

      Of course we can inspect and adapt, as always.


      From: Richard Griffiths <richard@...>
      To: scrumdevelopment@yahoogroups.com
      Sent: Tuesday, 27 August 2013 12:28 PM
      Subject: [scrumdevelopment] Concept of "work ahead" team

      Hi all, I’ve started to hear this more often – the “work ahead” team being a smaller group out of the team (BA, Architect, UX) who will groom the stories, relatively size them, have them ready for the team to do further work on.
      Shouldn’t the whole team be involved in these exercises, not the chosen few?
      Speed is n0 subsitute fnor accurancy

    • Show all 25 messages in this topic