Re: First week of a Sprint
- --- In email@example.com, "Dave Nicolette"
> ... Kane Mar describes this antipattern herehttp://kanemar.com/2005/11/03/the-staggered-iterative-waterfall-anti-pattern-part-1/
> and I have an article about it hereI'd like to point out that your excellent article provides far more
context information whereas mine just talks about the specific
problem. For those interested in reading these articles, I'd recommend
that both be read together.
- --- In firstname.lastname@example.org, "Kier" <kieroneil@...> wrote:
>I've found that breaking the habit of thinking in Waterfall is
> Thank you everyone for your responses.
> We are new to it and I'm the only person that knows Scrum & Agile more
> than a little.
> The mindset here is still firmly in Waterfall but we have agile-like
> If I can get them through a couple of iterations I'm sure it's going
> to get wide acceptance.
> Thanks again,
something that's very difficult to do. Part of the problem is that, on
the surface, arguments for waterfall make sense. It makes sense that
we would want to make sure everyone is fully occupied for the duration
of a sprint.
But for any complex system we can only optimize along one variable and
Scrum is optimized for having high quality code in production. I would
resist the tendency to optimize the team, and let *them* figure out
how to best use their time to deliver the work that they've committed to.
Hope that helps. Best regards,