Solution Icon

Solutions

Cutting-edge solutions tailored to everyday issues in the modern digital environment.

Services icon

Services

Innovative tools and services designed to address complex challenges today’s digital landscape.

IT FOR What WE DO MENU

Aerial view of an industrial facility at sunset

Services

Hexagon is reshaping industries through smarter systems, streamlined workflows, and bold digital innovation.

IT FOR HOW WE DO MENU

Aerial view of an industrial facility at sunset

Services

Hexagon is reshaping industries through smarter systems, streamlined workflows, and bold digital innovation.

Ready to clean up your CRM workflow?

Book a CRM Workflow Audit and see where leads, follow-ups, reporting, or disconnected tools can be fixed first.

Custom Software

Software Development Model: Which Fits Your Project?

How to pick a software development model: when waterfall, agile or a hybrid fits your project and contract, and what to ask a vendor first.

  • Custom Software
  • Buyer Guide
  • Updated November 2026
Dark cover with the words Development Model Which Fits? and the Hexagon IT Solutions label

The right software development model is the one that matches how much you already know about the work. If the scope is fixed, rules are clear and change is costly, a plan-first (waterfall) model works. If you will learn as you go, an agile model that ships small working pieces lowers risk. Most business projects end up with a hybrid: a fixed discovery phase, then short delivery cycles.

This guide is for owners, operations leaders and IT managers who are about to hire a team to build or rebuild software. It explains the main models in plain terms, when each fits, how the contract should follow the model, and what to ask a vendor before you sign.

What is a software development model?

A software development model is the order in which a team plans, builds, tests and releases the work. It decides when you see working software, when you can change your mind, and how money is spent along the way.

It is not a tool or a job title. Two vendors can use the same tools and still run your project very differently. One may disappear for four months and return with a finished system. Another may show you something usable every two weeks. Both are valid. The question is which one fits your project.

When does a waterfall plan make sense?

Waterfall means each phase finishes before the next starts: requirements, design, build, test, release. It suits work where the answer is known up front and change late in the project is expensive.

It tends to fit when:

  • Requirements are set by someone else. A regulation, a contract or a partner specification defines what must be built.
  • The work is a like-for-like replacement. You are moving an existing, well-understood process to a new platform.
  • Sign-offs are formal. Approvals at each phase are required by your board, auditors or a customer.

The risk is late feedback. Users often see the product only near the end, which is the most expensive time to find a wrong assumption. Even Winston Royce, whose 1970 paper is usually credited with the sequential model, described a single pass with no iteration as "risky and invites failure." If you choose waterfall, ask for clickable prototypes or early demos inside the design phase.

When is agile the better fit?

Agile is a family of methods built on the values in the 2001 Manifesto for Agile Software Development, such as working software and responding to change. Scrum is the most common form. The Scrum Guide describes sprints as fixed-length cycles of one month or less, with a small team that is typically 10 or fewer people.

Agile fits when:

  • You are building something new. A customer portal, an internal app or a product where users will tell you what they need once they try it.
  • Priorities will shift. Market, staff or process changes are likely during the build.
  • You can give the team regular time. Someone on your side must review work, answer questions and rank the backlog every cycle.

The last point is the one buyers underestimate. Agile moves decisions to you. If no one on your team can play the product owner role, the model loses most of its value.

Public agencies have adopted the same thinking. The U.S. Government Accountability Office publishes an Agile Assessment Guide with best practices for adoption, execution and program monitoring, which is a useful checklist for any buyer.

Can you mix waterfall and agile?

Yes, and for most mid-sized business projects we recommend it. A common pattern looks like this:

  • Discovery, fixed scope. Two to six weeks to map the process, agree the data, confirm integrations and write acceptance criteria for the first release.
  • Delivery, short cycles. Build and demo in sprints, with a ranked backlog and a clear definition of done.
  • Release gates. Formal sign-off before go-live, data migration and switching off the old system.

This gives finance a defined first phase and gives users early, working software. It also produces a better estimate for the rest of the work, because it is based on what discovery found rather than on guesses.

How should the contract match the model?

Many projects go wrong because the contract and the model point in different directions. A fixed-price contract with a vague scope pushes the vendor to say no to every change. A time-and-materials contract with no backlog or budget cap leaves you exposed.

Match them like this:

  • Waterfall work: fixed price against a detailed specification, with a written change-request process and agreed rates for changes.
  • Agile work: time and materials, or a fixed fee per sprint, with a monthly budget ceiling, a ranked backlog you own, and the right to stop after any sprint.
  • Hybrid work: fixed price for discovery, then sprint-based pricing for delivery once the backlog is estimated.

Whatever you choose, put acceptance criteria and testing duties in writing. Our guide on what to require from a vendor on testing covers the clauses we look for.

What should you ask a vendor before you sign?

These questions show quickly whether a vendor's model will work for you:

  • How often will we see working software, and in what environment?
  • Who on our side do you need, for how many hours a week, and for which decisions?
  • How do you handle a change request in the middle of a phase or sprint?
  • What does "done" mean for a feature: coded, tested, documented, deployed?
  • What happens to the code, data and documents if we stop after the first phase?
  • How will you report progress against budget each month?

If you are still writing the request, our software development RFP guide explains what to include so vendors answer these points in their proposals. For the questions to settle before any vendor is involved, see custom software strategy: 9 questions to answer first.

Frequently asked questions

Which software development model is best for a small business?

There is no single best model. For new tools where needs will change, a short discovery phase followed by agile sprints usually works best. For a well-defined replacement with fixed rules, a plan-first model can be simpler to manage and budget.

Is agile more expensive than waterfall?

Not by itself. Agile spreads cost across sprints and lets you stop or change direction early, which can reduce waste. It can cost more if the scope keeps growing without a budget ceiling, so set a monthly cap and review the backlog every cycle.

Can a fixed-price contract work with agile?

Yes, if the fixed price applies to a defined unit, such as a discovery phase or a single sprint with agreed capacity. Fixed price for an entire agile project with an open scope usually leads to disputes about change requests.

How long should a discovery phase take?

For most business applications, two to six weeks is enough to map the process, confirm integrations and data, and write acceptance criteria for the first release. Larger systems with many integrations may need longer.

Planning a custom software project?

We help teams pick a delivery model, scope a fixed discovery phase and build in short, visible cycles. Tell us what you want to build and we will suggest a plan that fits your budget.

Explore Custom Development

Sources

BUSINESS SYSTEMS

SOFTWARE

AI

INTEGRATIONS

Build, Improve, or Connect the Systems Your Business Depends On.

Whether you need custom software, CRM, ERP, AI, automation, integrations, or modernization, tell us what you’re trying to improve. We’ll review your requirements and recommend the most practical next step.

300+

Software projects delivered

37+

Enterprise apps built

150+

delivery team members

★★★★★ 4.7 on Google · 20 reviewsU.S.-led since 200721 awards & certifications →
Client results
BMG: cut the time lost on follow-ups by 70% with our CRM.
Utah Dental Association: convention registration streamlined from months to one month.

Tell Us About Your Project

No sales pressure. Tell us what you’re trying to build, improve, integrate, automate, or replace. We’ll review your answers and come back with a clear recommendation within 1 business day.

Prefer to talk now? Call +1 (801) 259-4800 or book a free 30-minute review.

© 2026 Hexagon IT Solutions. All rights reserved.