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

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

Expand Messages
  • srinivas chillara
    Aug 27, 2013
      The last point made is a good one. 
      However much of the conversation for a user story taken up in a given sprint happens during the sprint. So no worries there. 

      I don't think the "look ahead" team mentioned by Richard was an exclusive set. 


      From: Cass Dalton <cassdalton73@...>
      To: scrumdevelopment@yahoogroups.com
      Sent: Tuesday, 27 August 2013 9:10 PM
      Subject: Re: [scrumdevelopment] Concept of "work ahead" team

      It's not just the hierarchy.  The team contributes to the story decomposition, estimation, and refinement because they're the ones that will be doing the work.  They are the ones with skin in the game.  Having someone else refine stories leads to unrealistic estimates and allows ambiguities about the Definition of Done to slip through.  It short circuits the "Conversation" part of the 3 C's of user stories because the team is not part of the story conversation.  It also adds back some of the waterfall handoffs in the form of analysts and architects handing off work to developers.

      If you find yourself falling into the practice because iteration sessions are too long and devs get bored, then 1) have them attend a grooming session elsewhere in the iteration, and 2) make sure that you're not splitting work along resource/architecture boundaries.  If you split work along architecture and resource boundaries, the UI guy will be board while the team discusses non-UI stories, but that's an indication that the work is being stovepiped in the old waterfall fashion.

      If you find yourself falling into the practice because the dev team feels like they can't meet their commitments if they take time out of the iteration to refine stories, then you should probably reevaluate the pressures that the PO and SM are putting on the team.

      On Tue, Aug 27, 2013 at 10:47 AM, srinivas chillara <ceezone@...> wrote:
      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