5 Comments
No, I haven't crossed over to the Dark Side just yet, but I have found myself in the disturbing situation where progress isn’t needed or wanted. I am now in probably the second or third round of Stan Vs Windows 8. It’s not a top billing event, but one that has left me rather disappointed.
I got a fabulous new laptop which has technology improvements everywhere. Battery life is superb with a system to protect if for 5 years. Great processor, good storage capacity, nice display and a very nice keyboard. All around I am very pleased with the hardware.
So we all agree that projects should expect a significant amount of change. Agile projects are geared to deal with change in an inexpensive way. That’s all great but there still needs to be a mechanism in play to pay for the change, inexpensive or not. That’s simple you say, that’s just contingency. Well it is, but if we use the word contingency then to some ears we are saying ‘just in case money’. But we have already agreed that change is inevitable, so it’s certainly not just in case, it’s going to be needed.
Here at IndigoBlue we are encouraging everyone to contribute to our blog page as one way of sharing our current thoughts about Agile delivery and transition and strategic change management with a wider audience. Talking with my colleagues we realised that for some of us the thought of writing a blog is exciting and an opportunity to share views with a wider audience but for others the thought was quite daunting.
9 Comments
I've been thinking for some time now that traditional "Supply of Goods" contracts make building a collaborative client/supplier relationship tough. The nature of the contract is to fix the requirements up front, agree delivery milestones and try to focus the team on delivering what has been defined up front.