Imagine the Possibilities, We'll Bring Them to Life!

Project Delivery · 04 Nov 2026

Project changes: turn new requests into clear delivery decisions

New requests are normal in a project. A demonstration may reveal a missing step, or a business priority may change. Delivery becomes difficult when those requests enter the work without a shared decision about time, cost and what moves aside.

Give a change enough detail to discuss

Replace “add reporting” with a specific user task: who needs the report, which question it answers, which records it uses and how often it is needed. Ask what happens if it waits. This helps distinguish a launch requirement from an improvement that can follow later.

Make the trade-off visible

For each proposed change, record the purpose, affected work, dependencies and open questions. Have the delivery team assess effort and uncertainty. Then ask the accountable business owner to choose whether to replace another item, adjust the plan or defer the request. An estimate is a basis for a decision, not evidence that a change has been approved.

The principles behind the Agile Manifesto encourage responding to changing needs, delivering working software regularly and reflecting on how the team works. Frequent review is useful when it leads to explicit decisions and updated expectations.

Define acceptance before the demonstration

For an illustrative approval feature, acceptance might require an authorised approver to accept or reject a request, record a reason and make the outcome visible to the requester. Also discuss missing information, duplicate submissions and access restrictions. A demonstration of one successful click does not cover the whole workflow.

  • Who confirms that the result meets the need?
  • What examples will they use to review it?
  • Which exceptions must the release handle?
  • What remains outside this release?

Keep one decision record

Store the agreed scope, acceptance notes and changes where both the business and delivery team can find them. After a meeting, capture the decision, owner and date. Avoid leaving approval scattered across private messages and separate documents.

At each review, inspect completed work against the agreed examples. Update the remaining plan using what the team has learned, including unresolved dependencies and support work.

Takeaway: welcome useful changes, but give every commitment an owner and a visible trade-off. Project management adds value when everyone can explain what is being delivered, why it matters and how it will be accepted.

Topics: Project management, Scope, Delivery

Sign in to comment or rate this insight.

Back to insights

Built for ambitious local businesses

Give your business a place to grow online.

Turn interest into orders and enquiries with an online presence built around your business.

  • Shisanyama: menus and online ordering
  • Architecture practices: portfolios and project enquiries
  • Graduation gown sellers: product catalogues and online sales
  • Perfume businesses: collections and online storefronts

Let’s plan the right website or e-commerce experience for your next step.