15 janeiro 2008
Blz então... postando serio agora..
Na lista de discussão gringa de XP (extremeprogramming) está rolando uma discussão muito interessante sobre a utilização de XP por uma equipe apenas para planejamento. Confesso que achei extremamente interessante. Em seu post inicial Stefan Arentz descreve a utilização principalmente da prática de jogo do planejamento e estimativas... acompanhe o post na íntegra.
Gostaria de chamar a atenção para um reply:
John A. Maxwell
> Hmm makes me wonder.. does XP works on a fixed cost project ?
It depends on what you mean by "work". If you mean, will it help you get the most value for the money spent, yes. If you mean, will it let you know as early as possible if you're not gonna meet all of the goals (if that's the case), again, yes.
If you mean, will it cause the impossible to suddenly become possible, no (well, unless it was only very slightly impossible :-). If you mean, will it enable you to delude yourself into thinking you can do too much work in too little time, again, no.
If you mean, will it give you a magic wand, to make the people who want more done than time and resources allow stop being unreasonable... maybe. It depends on whether they're prepared to face reality, and even more importantly, on _how_ they're prepared to face it. Further exposition below. (...)
Yep. Welcome to every fixed price contract I've ever heard of. A news flash, though: most of the time, the people applying the pressure _already_ _know_ they aren't going to get everything they ask for. They just don't know any other way to get as much as possible. The logic is simple (albeit incomplete and incorrect): the harder they push, the harder the programmers will work, and the more will get done.
But _your_ side of that is that you have to be honest enough to tell the truth, even when it's not what the person you're talking to wants to hear. Not whine about the truth, but accurately, calmly, and professionally report your progress, how much the customer can expect to get from you every time you sit down to plan an iteration, etc.
There are good reasons why the white book talks about "courage". It's not a joke or "feel good" filler, and it's not easy.
EditNote: Aos finalizar o post, vi que o James Shore também publicou sobre este mesmo post... coincidência?