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

34775Re : [scrumdevelopment] Re: Thanksgiving sprint

Expand Messages
  • Florence Chau
    Nov 24, 2008
    • 0 Attachment
      Hello Aleksey,

      What we do in theses cases is adding a story and evaluate it. Then we remove a equivalent story. That way, we don't feel overwhelmed.


      De : Aleksey D. <alexeyd@...>
      À : scrumdevelopment@yahoogroups.com
      Envoyé le : Lundi, 24 Novembre 2008, 17h39mn 04s
      Objet : [scrumdevelopment] Re: Thanksgiving sprint

      Really quick reply, because it sounds I should go and start planning
      next sprint now. We planned sprint according to our velocity, but
      several distractions came up, so we got into debt. No excuses, just
      thinking about the next step.


      --- In scrumdevelopment@ yahoogroups. com, "Mark Summers"
      <markwilliamsummers @...> wrote:

      > As a general rule you are better off keeping with the schedule just
      > accept less into the Sprint. Keeps in sink with other peoples diaries
      > and keeps the rhythm going.
      > One thing that worries me is that you talk about technical debt and the
      > need to recharge, have your team been working slightly above their
      > capacity?
      > Schedule less work into the Sprint use the holiday as an excuse if
      > needed. Prioritise the technical debt as the highest priority and work
      > to stop those interuptions.
      > --- In scrumdevelopment@ yahoogroups. com, "Aleksey D." <alexeyd@>
      > wrote:
      > >
      > > Quick question, my team had 14 two-week sprints in a row. The last one
      > > had too many distraction and waas not very successful. The sprint
      > > planning is today (11/24/08). This week is only 3 work days for us due
      > > to the Thanksgiving weekend. What would be a better option for us:
      > >
      > > 1) schedule a 3 days break this week to catch up on tech debts,
      > > recharge, and etc.
      > > 2) schedule a normal sprint, taking less available time into account
      > > 3) schedule a one-off 3 weeks sprint
      > >
      > > Thanks for the advice!
      > >
      > > --Aleksey
      > >