|
Written by Rachel Davies
|
|
Friday, 22 July 2011 00:12 |
|
| |
Being an Agile Coach is challenging in many ways. You have to balance many things (see Olaf Lewitz recent post Spotting the Balance) as you work with different teams and stay true to your own values. You are a catalyst for change, helping the teams you work with see how they can work differently and supporting them on their agile journey. To do this you will need a solid understanding of agile principles and plenty of experience in how to put them into practice. When Liz and I wrote our book on "Agile Coaching" we filled it with stories and... |
|
|
Written by Rachel Davies
|
|
Thursday, 07 July 2011 06:40 |
|
| |
Some words of advice on when to write the acceptance tests for our user stories. |
|
Written by Rachel Davies
|
|
Tuesday, 28 June 2011 03:15 |
|
| |
Summary of summery events for Agile Coaches in UK |
|
Written by Peter Schuh
|
|
Wednesday, 25 May 2011 22:55 |
|
| |
Estimates are a fact of life for most of us. And often – while not always – they are a necessity. If I weren’t using some form of estimation on my current projects, they would be twisted up like Sherman bow ties. And on fire. This brings us to an apparent paradox. The larger and [...] ShareThis |
|
Written by Scott Ambler
|
|
Monday, 09 May 2011 18:40 |
|
| |
One of the questions that I received during my Agile Journal webcast in April was “Can you address how to create firm fixed price quotes in response to commercial RFPs?” The good news is that I’ve written a fair bit about funding strategies for agile projects and have been really clear about my disdain for “fixed price” projects. To make my position clear, when it comes to doing a “fixed bid” development project where the customer requests that the scope, price, and schedule be defined up front, I personally believe:
-
It is unethical for teams to do fixed bid projects.
-
It is questionable at best for customers to request this, and grossly incompetent if they’re a “repeat offender”.
Having said that, I want to make several important points:
-
I want to make it clear that this is my personal opinion and not that of the organization that I currently work for, IBM.
-
This opinion is based on the overwhelming evidence which exists showing that “fixed bid” development projects are spectacularly bad ideas. I summarize this evidence in The Dire Consequences of Fixed-Price IT Projects and summarize data from a recent survey in Survey Shows Unethical Behavior Inside IT Development Teams. Note that the second article doesn’t directly address fixed-bid projects but instead explores some of the behaviors which fixed-bid projects motivate amongst IT teams.
-
Yes, it is possible to do fixed bid agile projects, as I describe in Agile on a Fixed Budget, and such an approach will increase your chance of success, but it’s still an incredibly bad idea.
-
The reason why we still have IT procurement people inflicting fixed bids upon us is because they don’t understand the implications of what they’re asking for and this in turn is because we don’t take the time to educate them as to their folly. So, if you’re in such a situation feel free to share this blog posting with them.
If your organization would like to understand the implications more thoroughly I’m happy to discuss it with them. Feel free to email me and we’ll set something up. |
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>
|
|
Page 1 of 75 |
