Agile Development with Fixed Milestones: How It Keeps Projects on Budget

Project team reviewing a milestone roadmap on a large screen in a modern Auckland office

Most business owners like the idea of agile. Working software early, regular check-ins and the freedom to change direction all sound sensible. What makes them nervous is the budget. If the scope can change every fortnight, how do you know what the project will cost or when it will finish? Agile development with fixed milestones is the answer many New Zealand organisations settle on. It keeps the flexibility of agile delivery while giving you clear checkpoints, agreed deliverables and a budget you can actually plan around.

This guide explains how the approach works, how it differs from pure time-and-materials agile and traditional fixed-price projects, and what to look for when you agree milestones with a development partner. If you are planning a build right now, our custom software development team uses this model on most projects, so the examples come from real-world practice rather than theory.

Why agile alone can make budgets feel uncertain

Agile methods such as Scrum and Kanban were designed to deal with uncertainty. Instead of writing a huge specification up front and building it in one long stretch, the team works in short cycles called sprints, usually one or two weeks long. At the end of each sprint you see working software, give feedback and adjust priorities.

Pure agile is usually billed on time and materials. You pay for the team’s time, and the finish line moves as priorities change. For a startup with investor funding to manage, or an SME that needs board approval for a fixed figure, that open-ended feeling is a real problem.

Fixed-price waterfall projects swing too far the other way. The price is locked, but so is the scope. Every change becomes a variation, relationships turn adversarial, and the final product often reflects what you thought you needed a year ago rather than what you need today.

How agile development with fixed milestones works

The milestone model sits between these extremes. The project is broken into a small number of meaningful stages, each with a clear outcome, an agreed budget and a target date. Inside each milestone, the team still works in agile sprints, so you see progress regularly and can adjust details along the way.

The basic structure

  1. Discovery and scoping. A short, paid discovery phase defines goals, users, key features, integrations and risks. This produces a prioritised backlog and a milestone plan.
  2. Milestone planning. The backlog is grouped into milestones that each deliver something usable, for example “customers can register and place an order” rather than “database complete”.
  3. Sprint delivery inside each milestone. The team builds in one- or two-week sprints, demos progress and refines details with you.
  4. Milestone review and sign-off. At the end of each milestone you review the agreed outcomes against acceptance criteria, sign off and release payment.
  5. Replanning. Before the next milestone starts, you confirm or adjust its scope based on what you have learned.

What is fixed and what stays flexible

The key is being explicit about which parts are locked and which can move.

Element Fixed per milestone? Notes
Budget Yes Each milestone has an agreed price or a capped budget.
Target date Yes, within a small buffer Dates are planned around sprint capacity.
Business outcome Yes For example, “staff can create and approve quotes”.
Detailed features Flexible Screens, fields and workflows can be refined during sprints.
Priorities between milestones Flexible Later milestones can be reordered or reshaped.

This is sometimes described as fixing time and cost while keeping scope adjustable. If something new becomes important mid-milestone, a lower-priority item of similar size is swapped out rather than the budget simply growing.

Benefits for New Zealand businesses

Predictable cash flow

Paying against milestones lines up spending with visible progress. For many NZ SMEs this is easier to manage than open-ended monthly invoices, and it makes conversations with your accountant, bank or board far simpler. Typical market ranges for a business application milestone sit somewhere around NZD 15,000 to 60,000 excl. GST, depending on complexity, but your own figures should always come from a proper discovery phase.

Lower risk

Because each milestone ends with working, tested software, you never get to month six and discover nothing works. If priorities change or funding is delayed, you can pause after a milestone and still own something usable.

Better decisions

Seeing real software early changes how people think. Features that seemed essential on paper are often less important once users try the first version, while small details turn out to matter a lot. Milestone reviews create a natural moment to act on that learning.

Healthier relationships with your development partner

Clear outcomes and acceptance criteria reduce arguments about what was promised. Both sides know what “done” means for each stage, which keeps the relationship collaborative rather than contractual.

Defining milestones that actually work

Good milestones are the difference between a smooth project and a frustrating one. Here are the principles we recommend.

  • Make each milestone deliver value. Aim for something a real user can do, not just a technical layer. “Warehouse staff can scan and receive stock” is better than “API built”.
  • Keep them a manageable size. Four to eight weeks per milestone is a common sweet spot. Long enough to deliver something meaningful, short enough to keep risk low.
  • Write clear acceptance criteria. List the specific scenarios that must work, including edge cases and roles such as admin and standard user.
  • Front-load the riskiest work. Integrations with Xero, payment gateways or legacy systems should be proven early, not left until the end.
  • Include non-functional requirements. Performance, security, accessibility and Privacy Act 2020 obligations belong in milestone criteria, not as an afterthought.
  • Plan a launch milestone. Data migration, training, go-live support and hosting setup deserve their own stage.

An example milestone plan

Imagine an Auckland trade supplier building a customer ordering portal. A sensible plan might look like this:

  1. Milestone 1: Trade customers can log in, browse products with their own pricing and see stock levels.
  2. Milestone 2: Customers can place orders, and orders flow into the existing accounting and inventory systems.
  3. Milestone 3: Staff can manage customers, pricing and order status from an admin dashboard.
  4. Milestone 4: Reporting, notifications, performance tuning and go-live.

After milestone 1, the supplier might realise customers care more about reordering past purchases than browsing. That feature can be pulled forward into milestone 2, with a lower-value item moved later, without blowing the overall budget.

Managing change without losing control

Change is normal in software projects. The milestone model does not stop it; it gives you a calm way to handle it.

  • Small changes within a milestone are handled inside the sprint process. A field added here, a workflow tweak there.
  • Larger changes are traded against existing backlog items of similar size, so the milestone budget stays intact.
  • Genuinely new scope becomes a new milestone or an extension, estimated and approved before work starts.

A transparent backlog that you can see at any time makes these trade-offs easy to discuss. You should always know what is in, what is out and what it costs.

Is this model right for your project?

Agile with fixed milestones suits most business software projects, but it is not the only option.

  • It works best for new products, internal platforms, customer portals, mobile apps and integration projects where you need budget certainty and expect to learn along the way.
  • Pure time and materials can suit long-term product teams with a stable budget and a high level of trust, or ongoing support and enhancement work.
  • A small fixed-price job can work for very well-defined, low-risk tasks such as a simple integration or a defined report.

If you are unsure, it helps to talk to a software development company that offers more than one engagement model, so the recommendation is based on your project rather than their preference.

What to ask a development partner

Before you sign, ask any potential partner these questions:

  1. How do you run discovery, and what do we receive at the end of it?
  2. How do you define milestones and acceptance criteria?
  3. How often will we see working software, and who attends demos?
  4. How do you handle changes within a milestone and between milestones?
  5. What happens if a milestone runs over?
  6. Who owns the code and data, and how is it handed over?
  7. What support is available after launch?

Clear, confident answers are a good sign. Vague replies or a reluctance to commit to anything in writing are not. You can read more about how we approach projects and partnerships on our about page.

Frequently asked questions

Is agile with fixed milestones the same as a fixed-price contract?

Not quite. Each milestone has a fixed or capped budget and an agreed outcome, but the detailed features inside it can be refined. A traditional fixed-price contract locks the full scope up front, which makes change slow and expensive.

What happens if a milestone takes longer than planned?

That depends on the agreement, so make sure it is written down. Commonly, if the overrun is caused by the development team’s estimate, the partner absorbs it. If it is caused by new scope or delayed client decisions, it is discussed and agreed before extra work goes ahead.

How many milestones should a project have?

Most business applications work well with three to six milestones. Fewer than that and each stage becomes large and risky. Many more and the overhead of reviews and sign-offs starts to slow things down.

Do we need to be heavily involved during sprints?

You need a product owner on your side who can answer questions within a day or two and attend demos, usually an hour or so each sprint. Quick decisions keep milestones on track more than anything else.

Can we stop the project after a milestone?

Yes. One of the main benefits of the model is that each milestone delivers working software you own. If priorities or budgets change, you can pause and resume later without losing what has been built.

Does this approach work for mobile apps and integrations?

Very well. Mobile apps benefit from early user testing, and integration projects benefit from proving the riskiest connections, such as Xero or a legacy database, in the first milestone.

Plan your project with confidence

Agile development with fixed milestones gives you the best of both worlds: the adaptability to build the right thing, and the budget certainty to plan your business around it. The key is a solid discovery phase, well-defined milestones and a partner who is open about trade-offs. If you would like help shaping a milestone plan for your own project, book a free 60-minute consultation with our Auckland team. We will talk through your goals, highlight the risks worth tackling first and suggest a realistic way to get there.

Share Article:
About Author

Consectetur sollicitudin cubilia facilisis lobortis lacus a ac phasellus. Mus pulvinar enim suspendisse pharetra id commodo platea nunc aliquet.