How to describe agile delivery in a government tender

Government digital teams increasingly expect agile delivery, and many digital standards, such as the UK Service Standard and similar ones in Canada and Australia, are built around it. But many buyers still have to approve budgets and scope up front. Your methodology answer has to bridge the two.

Lead with outcomes, not ceremonies

Evaluators don't award marks for using the word "scrum". They award marks for showing how your approach reduces their risk. Start with what they get:

• Working software early, often within the first month.
• Regular demos where they can see progress and change direction.
• Decisions made by their product owner, not by you.
• A clear picture of budget spent and remaining at all times.

Show the phases

Many public digital projects follow a phased approach:

1. Discovery: understand users and the problem. Often two to eight weeks.
2. Alpha: test ideas and technical approaches with prototypes.
3. Beta: build the real service and release it to users, first privately, then publicly.
4. Live: run and improve it.

Say which phases this tender covers and what you'll deliver at the end of each.

Explain the governance

Public buyers need accountability. Describe:

• Roles: their product owner, your delivery manager, who signs off what.
• Cadence: sprint length, planning, demos, retrospectives.
• Reporting: what they'll get each sprint, such as burn-up charts, budget used and risks.
• Change: how scope changes are agreed. See managing change requests.

Fixed budget, flexible scope

Many buyers worry that agile means open-ended cost. Explain how you'll work within a fixed budget: a prioritized backlog, the most valuable features first, and a clear point where the buyer decides what to do with the remaining budget. This often pairs with a capped time and materials model.

Bring evidence

As with every answer, prove it. "On a 2025 project for a provincial agency, we released the first version to 50 staff in week six and went live to the public in month five, within the original budget."

Common questions

Can you use agile on a fixed-price government contract?

Yes, often by fixing price and time while letting scope flex, or by pricing each phase separately. Explain the approach clearly in your bid.

What if the tender asks for a waterfall plan?

Give them what they ask for. You can still show iterative testing and demos within the plan, but don't argue with the buyer's chosen method.

Should I include a Gantt chart?

If the buyer asks for a timeline, yes. A high-level chart with phases, milestones and releases works well for agile projects too.