Re: [scrumdevelopment] Huge challenge
- On Thu, Jul 1, 2010 at 8:08 PM, Rafael Nascimento <rafaelnascimento.rj@...> wrote:
He lived all his life into waterfall and RUP projects. To him, Agile is a mess. An anarchy. It's that really wrong idea of no dates, no rules and no documents. But, otherwise, he even doesn't try to understand what it's all about. He is near to the end of his career, and if he always did what he does and, for him, it brought the results, why to change now, you know?yeah that seems to be the issue and I have seen it with other managers as well. If you are really passionate ( which you seem to be ) about a successful Agile adoption, leverage you passion to be patient enough to show by example that Agile is not about no date , no rules and no documents.
Fortunately, he fixed only a date. Not the team, and not the scope. This is good.
But he doesn't wanna see the deadline, sometimes, moving forward, as I need to provide him feedback at each end of sprint, and it will sue happen.
Do you think if scope is not fixed, you can still deliver on time a scope that is of highest value .Do you think showing early working software will make him see the fruits of the agile adoption ?
I think not wanting to move the deadline even an hour a bad thing, since software projects don't act this way. It's natural.
And the other bad thing is to control what each one is doing, like previously assingning task to each one during the planning meeting.
Do you think showing value in other areas like early working software , getting things committed for a Sprint done etc will automatically have his need for controlling what each person is doing go away?
WORK is GOOD
2010/7/1 Roy Morien <roymorien@...>
Well, fixed delivery dates are not uncommon, and are not necessarilly a problem, unless they are unreasonable. How you actually go about developing and delivering the product should be up to you ... or does he have the authority and intention to impose that on you? If that is the case, you have little choice, I would suggest. Just make your promised delivery date as reasonable as you can get away with (and I choose my words here carefully).
Given that an 'agile' project is more likely to deliver a useful product sooner, or more effectively, then you use the fixed deadline as a target, and keep everyone informed regularly of the likelihood of what you will be able to deliver by that date. That is, assuming he lets you do it this way.
Not much else you can do, I would suggest.
Date: Thu, 1 Jul 2010 23:39:34 -0300
Subject: [scrumdevelopment] Huge challenge
I need a help from you. I have a huge challenge and was wondering what would be your approach.
I need to sell the Scrum framework to a 52 years old director of a huge company who knows the framework superficially and not entirely agree with it. We have a big project, divided into several large modules. This man always imposes ScrumBut into each module of the project which, of course, cannot make their deliveries on time.
This man likes to have fixed dates ahead. He thinks the Scrum does not cause people to deliver the entire sprint "done". There is always a balance of work per sprint "undone" and no "punishment" for this fact. He also likes to control what each person is doing, in detail.
How would you sell Scrum to this man? Recalling that he is a director who is unlikely to change his mind overnight.
Thank you all!
Looking for a hot date? View photos of singles in your area!