Build
Build
The Build phase is where the main body of work gets done to prepare the system for launch based on the signed off requirements.
The Build phase itself involves a sign off process, which involves the customer confirming that the system has been set up in a way that meets all of the requirements for launch. Other outputs of the build phase include a Test Plan, which is a fairly basic document with instructions to the customer on what should be covered in their testing, both before launch, but also prior to future upgrades.
| Deliverables |
|---|
| An OrderFlow instance, configured by us to meet agreed requirements, running in our laboratory environment |
| An Offsite Handover, during which we do an end to end run through of every operational process |
| Sign-off on all processes, integrations and paperwork in scope for launch |
During the Build phase, we will contact you when required for further input on individual pieces of work, and also keep you informed of progress during the weekly project call. However, there will be no formal handover of work while the build phase is in progress.
Almost all of the time spent during the the Build phase will be off site. It will not be physically delivered into the customer environment after a formal handover and sign-off process.
OrderFlow Build Instance
The key deliverable in this stage is an instance of OrderFlow that can be verified as meeting requirements for launch.
The table below makes it clear what the Build Instance would entail.
| System Area | Typical Salient Features |
|---|---|
| eCommerce Integration | End to end integration with your test eCommerce platform |
| Courier Integration | Integration with the test intance/account for all of your couriers |
| Locations | Your actual warehouse locations, some of which will be physically represented in our lab environment |
| Products | The product catalogue obtained from your eCommerce system |
| Courier Selection | Rules applied according to launch requirements |
| Picking Batch Selection | Rules applied according to launch requirements |
| Handhelds | Verification using one of the actual handheld scanner |
| Paperwork | Despatch notes, product, location and user labels as required for launch, using customer's label stock |
| Workstations | Complete setup of a single packing workstation using actual thermal and/or A4 laser printer |
| Printing | Verified printing of all paperwork using customer's thermal printer (or identical copy) |
| User Roles | System set up with launch users, appropriately restricted by role |
In addition,the Build Instance will be configured so that all warehouse processes, including Goods In, Putaway, Picking, Packing, Despatch and Returns are configured as per signed off requirements in the manner intended for launch.
Offsite Handover
Once we are confident that OrderFlow Build Instance is suitably configured to meet all signed off requirements, we will arrange for an Offsite Handover.
The Offsite Handover take places in our laboratory environment, and involves just the key customer staff members involved in the project. During the handover, we do a walkthrough of all of the integrations, processes, and outputs.
Typical tasks that would be covered during the Offsite Handover:
| System Area | Typical Tasks |
|---|---|
| eCommerce Integration | Verify import of products into OrderFlow from test eCommerce instance, verifying field level detail of data received |
| Verify import of orders into OrderFlow | |
| Courier Integration | Verify integration with each courier (using test account), with successful validation and label generation for each service |
| Verify integration for all services handling international shipments | |
| Verify end to end flow of address information for each interaction | |
| Verify physical printing of label for each supported service | |
| Courier Selection | Verify the courier selection rules used to select each service, against stated requirements |
| Picking Batch Selection | Verify the courier selection rules used to select each service, against stated requirements |
| Goods In and Putaway | End to end verification of receipt and putaway process, with appropriately role restricted users, and use of handheld where appropriate |
| Picking and Packing | End to end verification of picking and packing process, with appropriately role restricted users, and use of handheld where appropriate |
| Printing | Verify the physical printing and contents of despatch notes, for each test shipment packed |
| If not using handheld terminals | |
| Verify examples of location, product and user labels to be used for launch | |
| Despatch | Verify any manifesting and despatch process using imported shipments |
| Labelling | Verify that aspects of labelling in preparation for onsite handover day |
As preparation for the day itself, we will create a Test Plan. This is a simple document describing at a high level the tests that will be carried out during the Offsite Handover.
In each area, the outcome of the handover/verification will be recorded against the signed off requirements. Any outstanding issues raised against existing requirements will be noted and resolved as part of a follow up.
Additionally, if new or changed requirements are identified at this point, new tickets will be raised in the customer's 'Support' project, as per the Change Control process. For each of these, a decision will be taken on whether the new requirement should be brought into scope for launch, with the obvious consideration of the potential affect on the launch date.
Why an Offsite Handover?
Customers may be asking why the main formal handover against requirements is done through an offsite day. In order to make most efficient use of everyone's time, it is critically important to have the customer's full attention during the requirements gathering and verification process.
In practice, we tend to find that can be quite difficult at the customer site; without the pressure of an imminent launch, it is very easy to become distracted by more immediate problems.
With an offsite day, you get opportunity focus fully on the OrderFlow implementation project, allowing for much more rapid progress in preparing for launch.
Allow a full day for the Offsite Handover, with an early morning start!
Handover of further pieces of work required for signing off the OrderFlow Build Instance will be done incrementally in the days following the Offsite Handover.
Customer Sign-off Notes
Customer sign-off on the OrderFlow Build Instance will need to take place before it can be delivered to the customer environment, which takes place during the testing phase, described next.