Nexlab IT Solutions
Let’s talk
Delivery guide 01 · 4 sections

A dedicated team or a project delivery agreement?

Start with who will manage the work, how much is known and how often priorities change.

At a glance

4 decisions to settle before the work starts.

  1. 01Start with ownership
  2. 02Separate unknowns from commitments
  3. 03Agree how changes are handled
  4. 04Questions to bring to the first call
Choose by ownership and certainty
Your roadmap
Priorities change often

Dedicated team

Your product owner guides the backlog and decisions.

Outcome and scope are defined

Project delivery

Both sides agree milestones, acceptance and handover.

The commercial model follows how the work will be owned and how much is known.
Section 01

Start with ownership

If your product team manages the backlog and makes technical decisions, an embedded engineering team may be a useful fit. If you need someone to take responsibility for a defined piece of software, discuss a project delivery arrangement. In either case, name the people who can accept work and approve changes.

  • Who manages the backlog?
  • Who makes technical decisions?
  • Who can accept work and approve changes?
Section 02

Separate unknowns from commitments

A feature list does not always describe the whole job. Existing integrations, data quality and user permissions can change the effort involved. Write down what is known and what still needs investigating. A focused assessment can help resolve those questions before agreeing the build.

  • Existing integrations
  • Data quality
  • User permissions
Section 03

Agree how changes are handled

Ask how a new requirement affects the backlog, budget and delivery date. A useful proposal explains the assumptions behind the estimate and how changes will be reviewed. For an ongoing team, agree how priorities are set and how progress is discussed.

  • Effect on the backlog
  • Effect on the budget
  • Effect on the delivery date
Section 04

Questions to bring to the first call

  1. Q1Who owns the roadmap?
  2. Q2Who reviews the code?
  3. Q3What is the first useful release?
  4. Q4Which people or systems could delay it?
  5. Q5What will your team need at handover?

Answers to these questions are more useful than choosing a commercial model by name alone.

Take this to your next meeting

The short checklist.

Everything this guide asks you to settle, in one place.

01

Start with ownership

  • Who manages the backlog?
  • Who makes technical decisions?
  • Who can accept work and approve changes?
02

Separate unknowns from commitments

  • Existing integrations
  • Data quality
  • User permissions
03

Agree how changes are handled

  • Effect on the backlog
  • Effect on the budget
  • Effect on the delivery date
04

Questions to bring to the first call

  • Who owns the roadmap?
  • Who reviews the code?
  • What is the first useful release?
  • Which people or systems could delay it?
  • What will your team need at handover?
Keep reading
Delivery guideWhat to prepare before connecting business systemsRead the guide
Delivery guideWhat a useful software handover should includeRead the guide
Have a project in mind?

Apply this to your project.

Tell us about your current setup and the decision you need to make. We can work through the practical details together.

Discuss your project