Fast. Simple. No meetings. No delays.
Home / Blog / Software Development / Delivering Software in Milestones: A Lightweight Process for Small Teams

Delivering Software in Milestones: A Lightweight Process for Small Teams

A lightweight delivery rhythm for small projects: written scope, two-week milestones, demos, acceptance criteria and change control.

Cover graphic for the article: Delivering Software in Milestones: A Lightweight Process for Small Teams

A software development process for small teams should be light enough to survive real deadlines: a written scope, a prioritised list of work, short milestones that end in a working demo, acceptance criteria for each item, and a simple way to handle changes. You do not need full Scrum ceremonies to get predictability.

The advice below is general, for a client and a small team working together on a web application or business system. It is a pattern you can adapt, not a description of any single organisation's method. If you are still working on the scope itself, start with how to write a software requirements document.

Process should fit team size

Frameworks such as Scrum were designed for larger teams with dedicated roles. Applied unchanged to a team of two to five developers and one busy client contact, they can produce more meetings than output: planning sessions, daily stand-ups, formal reviews and retrospectives that outweigh the work they manage.

Ask of every practice: what problem does it solve here, and what is the cheapest way to solve it? The problems a small project really has are consistent:

  • Nobody agrees what "done" means.
  • Work disappears for weeks and the client sees it only at the end.
  • New requests arrive constantly and the deadline silently moves.
  • Decisions live in chat and nobody can find them later.

The rhythm below addresses exactly those four, and nothing else.

Written scope and backlog

Write the scope down in plain language before building: the goal, who uses the system, the main workflows, what is explicitly out of scope, and the assumptions you are relying on. It does not need to be long. Its job is to give both sides something to point at.

From the scope, build a backlog: a single ordered list of work items, each small enough to finish in a few days. Keep it in a shared tool that both sides can see, whether that is a board, a spreadsheet or an issue tracker. The tool matters much less than three habits:

  1. One list, one order. The top item is what happens next.
  2. The client decides priority; the developers decide estimates and technical sequence.
  3. Items near the top are detailed; items further down can stay rough until they get close.

Milestones and demos

Instead of fixed-length sprints with their full ceremony, many small teams work in milestones of about two weeks, each ending in something the client can see and use. A milestone is a set of backlog items chosen together, with a stated outcome such as "a customer can register, log in and book a slot on staging".

The milestone rhythm in practice:

  • Start: a short planning conversation to choose items and confirm the outcome.
  • During: work proceeds, with early builds on a shared test environment so the client can look at progress.
  • End: a demo of the working software, not slides. The client tries it, and you record feedback as new backlog items.

Shorter or longer works too; pick a length that matches how often the client can give meaningful feedback. The demo is the most valuable part: problems found in week two are cheap, and the same problems found at launch are not. If you are weighing how this fits with the contract type, see fixed-price vs time-and-materials contracts, since milestones work with either.

Acceptance criteria

What is an acceptance criterion?

An acceptance criterion is a specific, checkable statement about what must be true for a work item to count as done. It turns "build a password reset" into something both sides can verify.

For example, for a reset feature:

  • A user can request a reset by entering their email address.
  • The same confirmation message appears whether or not the address is registered.
  • The emailed link works once and expires after a stated period.
  • After resetting, the user is signed in or sent to the login page, as agreed.

Good criteria are observable, avoid vague words such as "fast" or "user-friendly" unless defined, and are agreed before work starts. Add the non-functional expectations that matter, such as supported browsers, accessibility needs and basic security handling. A work item is accepted when someone from the client side has checked it against the list.

Change control

Changes are normal; unmanaged changes are the problem. A lightweight control process keeps the conversation friendly:

  1. Capture it. New requests go on the backlog, never straight into someone's current task.
  2. Size it. The developers give a rough estimate and describe the effect on the plan.
  3. Decide it. The client chooses: swap it for something of similar size, add it and move the date or budget, or defer it.
  4. Record it. Write the decision down so scope stays traceable.

Handling changes mid-milestone

Protect the milestone in progress. Urgent defects and genuine emergencies can interrupt, but other changes wait for the next milestone start, when the backlog is reprioritised anyway. This keeps the team focused and keeps the demo promise. If something truly must come in now, agree which item leaves.

Communication cadence

Pick a small, predictable set of touchpoints and stick to it:

  • A brief written update weekly: done, in progress, blockers, decisions needed from the client.
  • A short call when a decision or discussion needs voices rather than text, with notes sent afterwards.
  • One place for decisions, such as the tracker or a shared document, instead of searching through chat history.
  • A named contact on each side, with a stated expected response time, so blockers do not sit unseen.

When a team works across time zones, favour written updates and recorded demos over meetings that suit only one side. If you are choosing who to work with, what matters most when choosing a development partner includes how well their communication habits fit yours.

Retrospectives

A retrospective can be fifteen minutes at the end of a milestone: what helped, what got in the way, and one or two changes to try next time. Write the outcomes down and review them at the next one. For a small team, skip the ritual and keep the habit; the value is in actually changing something.

Do small teams need sprints?

Not necessarily. What they need is the underlying discipline: a prioritised list, regular short cycles, visible working software, agreed definitions of done and managed change. Call it sprints, milestones or something else; use whichever words your team understands.

Putting it together

Begin with the written scope, an ordered backlog and a two-week demo, then add only the practices that solve a problem you actually have. If you want to discuss how a project could be structured, see our software development overview or get in touch.

Frequently asked questions

Do small teams need sprints?

Not formally. Small teams need the discipline behind sprints: a prioritised backlog, short regular cycles that end in working software, agreed definitions of done and managed change. Milestones of about two weeks with a demo at the end deliver those benefits without every planning and review meeting a full framework brings.

How do we handle changes mid-milestone?

Protect the milestone in progress. Put new requests on the backlog, have the developers size them, and let the client decide at the next milestone start. Genuine emergencies and urgent defects can interrupt, but agree which item leaves in exchange, and write the decision down.

What is an acceptance criterion?

It is a specific, checkable statement of what must be true for a work item to count as done, such as an emailed reset link working once and then expiring. Good criteria are observable, avoid vague words like fast, and are agreed by both sides before work begins.

Related articles

🚀 Start Now