Re: How to convince people of the Daily Scrum
- Hi there,
Jumping in a bit late on this: I think it's difficult to sell the
individual practices in Scrum standalone. They don't seem "efficient"
and often may be seen as unpleasant. I've found that when people
really "get" Scrum as a whole they are more open to the individual
practices, often eager to do them to keep high visibility, etc.
I remember reading Ken's black book way back when and I can still
remember the "ah-ha!" moment. It was during the discussion on
empirical vs. defined processes and why empirical methods are
necessary in complex projects.
Do your teammates really understand that scrum is a shift away from
defined processes toward "empirically" inspecting and adapting to the
complexities of the project? I'd start there because it tends to be
liberating to be free of the defined-process shackles.
Besides the book, the CSM course is a good way to really immerse in
this thinking and come away charged up for doing Scrum.
But I can certainly appreciate your situation in that it's tough
trying to get people to change in a decent/good situation. If they
like things the way they are and don't feel a need for change, maybe
they should keep on doing what they are doing. Is that so bad if the
results are good?
-- Victor Szalvay
--- In email@example.com, "mkg6_hotmail" <mkg6@...> wrote:
> I'm slowly trying to get people in my team to work with Scrum. Other
> teams in my organization have adapted to Scrum and most of them are
> pleased with the method.
> As our team is not in chaos (or we don't know we are), there is not
> much willingness to change. I think we can benifit from using Scrum
> because it will make our development process more transparent and
> will show whether we are really on track.
> I seem to have some success with getting a backlog list compiled,
> but I want to introduce the Daily Scrum too.
> The arguments against it from my teammates is that we already meet
> once a week and there is no need for a daily meeting. We are sitting
> with the desks in a square and there is a lot of osmotic
> One of the things to be agile is to choose a process that is 'barely
> enough'. Wouldn't doing without the Daily Scrum be sufficient?
> I'd like to convince them that it is not, but I also do not want to
> follow a recipe because that is what the cookbook says...