project planning

Fixed-price projects are a challenge to manage when using agile practices, as software teams need the flexibility to change what they are building based on customer need, and that often alters what can be done within a fixed budget. However, there are ways to achieve agility even within a fixed-budget constraint. Here are three ways to make a fixed-price project a win for all parties involved.

Agile teams can easily get puzzled by the heated debate happening between advocates for estimation and those in the #NoEstimates camp. However, by comparing how they solve these problems, we can identify many common practices between the two groups and see they are not truly at odds—they actually complement each other. Let's bridge the gap.

You've heard of a minimum viable product, which has only enough features to create a working model and provide feedback for further development. If you want to get started on a new project quickly, Allan Kelly suggests assembling a minimum viable team—only a few people, with only the necessary skills. They begin work right away, with a small budget and tight feedback loops, driving down risk.

Many organizations appear to suffer anxiety at the thought of programming. They want to get everyone but the programmers in a room to discuss a project down to the minute and the dollar, without a full understanding of the coding required. But a few hours of code experimentation generates far more understanding than days of debate by architects and analysts. Don't be scared of programming.