My current project is facing a lot of pushback from senior management who are used to fixed-price contracts and strict deadlines. They are uncomfortable with the 'evolving requirements' of an Adaptive/Agile approach. How can I convince them of the value without risking my position?
3 answers
The key is to change the conversation from 'scope' to 'value.' Instead of promising a set list of features, promise the delivery of the highest-value features first. Use a Minimum Viable Product (MVP) approach to show them tangible results early on. Once they see a working product in four weeks rather than four months, their anxiety usually drops. I also suggest involving them in the Sprint Demos. Seeing the progress firsthand builds a level of trust that no status report can match. It shifts the dynamic from a 'contract' to a 'partnership.'
Barbara’s advice on MVPs is solid. But Amanda, how are you currently handling the legal aspect of the 'fixed-price' contracts? If the contract is rigid, how do you plan to adjust the 'Definition of Done' without triggering a formal change request every two weeks?
Education is the best tool. I held a short 'Agile for Executives' workshop to explain that 'Adaptive' doesn't mean 'No Plan.' It just means a 'Flexible Plan.'
Nancy is right. Most pushback comes from a lack of understanding. Once they realize they have more control over the final product, they usually become your biggest supporters.
Thomas, we use 'Agile Fixed Price' contracts where the budget is fixed but the scope is flexible within a set of 'story point' tiers. This way, the client knows the max cost, but we have the freedom to swap low-priority features for high-priority ones as the project evolves. It satisfies the legal team while giving the project team the flexibility they need.