InnerWeb
Skip to main content

Stage acceptance on an artifact: a scenario for a logistics centre

A protocol of acceptance stating that the work was performed in line with the contract proves nothing, because it does not say what the manager actually saw and checked. Acceptance on an artifact means each of the three stages ends with a concrete, working element that can be run and tested. The scenario concerns a logistics centre and is a deployment concept, not a description of a completed project.

3
months and three stage acceptances
Source: offer, deployment schedule
2
system administrators on the client side
Source: offer, deployment assumptions

Situation: three months and three acceptances

The manager of a logistics centre orders a system for handling external companies, carriers and visitors on the warehouse premises. He has three months to go live, because the peak season starts in the fifth week of the fourth month. The deployment is divided into three stages, and payment and further work depend on the acceptance of each one.

The risk is known from experience: a stage ends, the contractor reports readiness, and the manager has no way to check what exactly he received. Only weeks later does it turn out that a function exists on the test server but not in production, or that it works on sample data rather than on real companies.

Three stages and three artifacts

The standard deployment takes 3 months in three stages, and each ends with the acceptance of a specific artifact. An artifact is something that can be run, clicked and checked, not a document stating that something was done.

  • Stage I: a working training module. The manager logs in as a trained user, completes the training and sees the recorded result.
  • Stage II: an accepted test permit. The manager goes through the whole permit workflow from request to closure and accepts it as a user.
  • Stage III: production launch. The system runs on live traffic from external companies, not on test data.

Split of the three-month deployment into stages (example)

Split of the three-month deployment into stages (example)Donut chart of three deployment stages of 4 weeks eachStage I: training module: 4 weeks (33.3%)Stage II: test permit: 4 weeks (33.3%)Stage III: production: 4 weeks (33.3%)12weeksStage I: training module4 weeks (33.3%)Stage II: test permit4 weeks (33.3%)Stage III: production4 weeks (33.3%)
Source: Example calculation: three months in three stages, equal stages of 4 weeks assumed

Stage I in practice: configuration and the training module

In stage I the instance, zones, gates, roles, company import, site map and training module are configured. The list is long, so the artifact for acceptance is a single final element: the training module, running on the configured instance with roles and companies from the import.

This way the manager does not accept an abstract configuration stage. He accepts something that proves the instance exists, the roles work and the companies have been imported. If the training does not open for an external company, it means some part of the configuration is incomplete.

Stages II and III: test permit and live traffic

The test permit in stage II is not a checklist but a full workflow: request, approvals, issue, closure. The manager himself performs the approver role and checks whether notifications reach the right people.

In stage III the offer assumes that final tests are run on live traffic from external companies, not on test data. This requires organizational readiness on the centre's side: at least 2 system administrators must be appointed and trained before the first carrier is admitted to the system.

How to record acceptance in the protocol

A good stage acceptance protocol consists of three statements: the name of the artifact, the date and time of the check, and the full name and function of the person who checked it. A screenshot or an extract from the system event log is attached to the protocol. It contains no general wording about compliance with the contract, because such wording does not settle a dispute if the artifact does not work.

It is also worth recording what is not accepted at a given stage, for example integrations with other systems planned for stage III. The boundary between stages is then clear, and the vendor cannot treat the acceptance of stage I as consent to the scope of stage III.

Conclusions for the logistics centre manager

Acceptance on an artifact shortens disputes, because the answer to the question 'is it done' is visible on the screen. With three stages in three months the manager has three checkpoints and three moments in which he can halt the project if the artifact does not work. If the vendor cannot name the artifact for its stage, the stage is either too big or too vaguely defined.

Video

Frequently asked questions

What is an acceptance artifact?

It is a working element of the system that the manager can run and check, for example the training module or a permit carried through from request to closure.

Are final tests run on test data?

No. According to the offer, final tests are run on live traffic from external companies, which is why the purchaser must have administrators ready before launch.

How many administrators does the purchaser need?

The offer assumes at least 2 system administrators on the client side, so that the work does not depend on one person and holidays can be covered.

Plan the stage acceptances

Write to us and we will name the artifacts for your site together and agree who checks them. We will show a sample three-stage schedule.

Let's talk