Skip to main content
Legia

Apps & Software

The Agile Method in Custom Application Projects: What It Means for the Client

A vendor using the agile method does not work alone until the application is finished. Here is what you need to prepare as a client: who decides, which meetings to attend, and how changes are handled in the contract.

SEO and Content Specialist

6 min read

A hand sketching an app screen flow on paper

Short answer: in a custom application project, the agile method means the application is built in short cycles and you receive a version you can try every few weeks. The consequences for the client: you need to appoint one decision maker (the product owner), attend every review of results, order feature priorities, and agree in the contract how changes are traded against time, cost, or other features.

Many application project proposals now mention “the agile method”. Clients often read the term as the vendor’s internal business. In fact, the agile method in an application project shifts part of the work to the client: decisions must be made more often, feedback must be given faster, and the contract needs to be written differently. This article does not cover the general definition and stages of agile, but what you need to prepare before signing a project that uses it.

What agile actually promises

Agile is a set of software development values set out in the Agile Manifesto (2001). Its four values put individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. The manifesto stresses that the items on the right still have value; the items on the left are simply valued more.

Two of its twelve principles concern the client directly. First, working software is delivered frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale. Second, business people and developers must work together daily throughout the project.

Scrum is one framework for putting those values into practice. Its official guide, the November 2020 Scrum Guide, sets out its roles, events, and artifacts. The terms in this article follow that guide.

Illustration: web application

Product owner: who you appoint

The product owner is the person accountable for maximising the value of the product, including setting the product goal and ordering the list of work (the product backlog). The Scrum Guide states three things that matter for the client:

  • The product owner is one person, not a committee. They may represent the needs of many parties, but the final decision rests in one pair of hands.
  • Anyone who wants to change the list of work must convince the product owner, rather than ask the developers directly.
  • The product owner’s decisions must be respected by the entire organisation.

In a custom project, this means you need to appoint someone who understands the workflow being digitised, has the authority to decide without waiting for a board meeting, and has the time. A common mistake is appointing staff without authority, so every question from the developers waits weeks for a superior’s approval. If the vendor provides a representative who handles this role day to day, still make sure there is one decision maker on your side.

The meetings you need to attend

Scrum divides work into sprints, fixed-length cycles of one month or less. Each sprint has events with clear time limits.

EventPurposeClient involvementTime limit (one-month sprint)
Sprint planningDecide what is worked on in this sprintThe product owner attends and explains prioritiesMaximum 8 hours
Daily scrumDevelopers align their daily workNot required; this is a developers’ meeting15 minutes
Sprint reviewInspect the sprint’s results and decide the next adjustmentsThe product owner and key stakeholders attendMaximum 4 hours
Sprint retrospectiveThe team improves the way it worksThe Scrum Team, including the product ownerMaximum 3 hours

For shorter sprints, the events are usually shorter too. The sprint review is the meeting you can least afford to miss. There, the work is shown to stakeholders, and the list of work may be adjusted to meet new opportunities. According to the Scrum Guide, work that does not meet the definition of done cannot be released, or even presented at the sprint review. So what you see there should be parts that can genuinely be used, not half-finished screens.

Backlog and priorities: the decisions in your hands

The product backlog is an ordered list of everything needed to improve the product, and its contents keep evolving. The order determines what is built first, so that order is essentially a business decision.

A few habits that help the client:

  1. Start with a clear requirements document. Agile does not remove the need for a requirements document; the document becomes the starting material for the backlog. A guide is in the article How to Write a Requirements Document Before Building an Application.
  2. Order by value, not by who asks the loudest. Features used every day by many people usually come first.
  3. Mark what must exist before launch. The rest can follow once the system is in use and real feedback has been gathered.
  4. Review the order after every sprint review, not only at the start of the project.

Changes midway and their effect on the contract

Agile welcomes changing requirements, even late in development. But welcoming change is not the same as adding work without limit. Time and budget remain limited, so every addition has to be traded for something: another feature is moved back, the schedule is extended, or the cost goes up.

The Scrum Guide says scope may be clarified and renegotiated with the product owner while a sprint is running, provided no change endangers the sprint goal. If the sprint goal becomes obsolete, the sprint can be cancelled, and only the product owner has the authority to cancel it. In a custom project, rules like these need to be written into the contract, because they affect cost.

Contract modelWhat is fixedWhat can changeSuits
Fixed scopeFeatures, price, and schedule agreed at the startOnly through a formal change requestRequirements that are already clear and rarely change
Time and materials (per sprint or per working hour)Rates and team compositionThe work itself, following the backlogRequirements that are still evolving, with a client who supervises actively
Fixed budget, flexible scopeBudget ceiling and scheduleWhich features get in, ordered by the product ownerClients who want cost certainty but are ready to choose between features

Whatever the model, make sure the contract answers four things: who has the authority to approve changes, how their impact is assessed, when additional work may start, and how it is billed.

How Legia does it

In the Web Application Development service, the system is built in stages and handed over for you to try every 2 to 3 weeks, so the direction of the work can be corrected before it goes too far. What is asked of you at this stage is time to try it and give feedback. Before development starts, you approve a clickable prototype. If requirements change midway, the change is recorded as a separate request, assessed for its impact on time and cost, and agreed before it is worked on; no additional work is done first and then billed at the end. A breakdown of time per stage is in the article How Long Does It Take to Build a Web Application?, and other services in this pillar are on the Applications & Software page.

Frequently asked questions

Does agile mean no requirements document is needed?

No. The Agile Manifesto puts working software over comprehensive documentation, but still recognises the value of documentation. A concise requirements document actually speeds up building the initial backlog.

Does the client have to join the daily meeting?

No. According to the Scrum Guide, the daily scrum is a 15-minute event for the developers. What matters for the client are sprint planning and the sprint review, along with a willingness to answer developers’ questions quickly.

How long is one sprint?

The Scrum Guide sets a maximum of one month. The length is kept fixed so that the rhythm of reviews and decisions can be planned.

Is the cost of an agile project harder to predict?

It can be, if the scope is left open without a budget limit. The fixed budget, flexible scope model gives cost certainty, provided the product owner is ready to choose which features get in.

Sources

Category Apps & Software

Keep reading

Related articles

All Articles