GenFrontier homeScope a project
Menu
Filed under
Deliver toProject sponsors, operations and IT leads who have to commit to a go-live date

Project planning for logistics software

A dated plan with named owners on both sides, every outside dependency on the calendar, and a cutover date chosen around your peak season rather than through it.

Scope a project
services / project-planning
A long curving line of standing dominoes, with the first domino at the start printed red and just beginning to tip

A signed requirements document says what to build. A project plan says when, by whom, in what order, and what happens when a date slips. Project planning is stage 3 of an engagement, after we walk the process and write the requirements, and before anything is built. The plan is a document you keep, and you can hold us, or any other vendor, to it.

From requirements to phases

We start from the signed requirements and group them into phases that each put something usable in front of your team. A typical order is one lane or one site first, then the next process, then the customer-facing pieces: for example, inbound tracking for one supplier group, then cycle counting, then customer status. Each phase carries its own acceptance tests, copied from the requirements, so “done” has the same meaning for both sides.

Each phase gets an estimate with its assumptions written beside it. When an assumption turns out wrong, the plan says which dates move.

What the plan contains

Milestones with dates. Requirements signed, build cycles, partner tests, user acceptance testing, cutover rehearsal, go-live and the end of hypercare.

Owners on both sides. Each milestone names one person: your process owner, your IT contact, your EDI coordinator, or our project lead. A milestone with two owners has none.

Dependencies outside the build. These are what usually move a go-live date, so they go on the calendar first:

  • Trading partner EDI testing. Partners run their own onboarding queues, and each 856 or 214 map is tested against the partner’s guide before it carries live data.
  • Hardware. Scanners, label printers, label stock and any Wi-Fi work have order and delivery lead times of their own.
  • Access and environments. Test copies of your ERP or WMS, user accounts, VPN access and sample data.
  • Master data cleanup. Items, units of measure and locations that must be corrected before testing means anything.

Test windows. Integration testing with each system and partner, then user acceptance testing run by the people who will use the system, using a written UAT test plan. The windows are booked into your team’s calendar, not just ours.

A cutover date chosen around peak season. We plan backwards from your calendar: peak season, month-end close, physical inventory counts and large promotions are blocked out. Go-live lands far enough before the next peak to leave room for hypercare and a few weeks of normal running.

Risks and a rollback plan. The risk register lists each risk with its likelihood, impact, owner and response. The rollback plan states the go/no-go criteria, the point after which rolling back costs more than fixing forward, how to return to the old process, and how transactions entered in the meantime are reconciled.

Example (fictional). A distributor whose peak runs from October to mid-December signs requirements in January and plans a spring go-live for receiving and cycle counting.

Milestone Date Owner Depends on
Requirements signed January 8 Client process owner Two review sessions held
Scanners and label printers ordered January 12 Client IT Device specification approved
Partner EDI testing starts (856) January 26 Client EDI coordinator Partner test slot confirmed
Devices on site, Wi-Fi checked February 16 Client IT Delivery from the reseller
User acceptance testing March 1 to 12 Receiving and inventory leads Build complete, test data loaded
Cutover rehearsal March 18 GenFrontier project lead UAT signed off
Go-live March 29 Steering group Readiness check passed
Hypercare ends April 23 GenFrontier project lead Open issues below agreed level

The cadence of demos and status reports

The plan fixes how you will see progress, so nobody has to ask:

  • A demo of working software at the end of each build cycle, usually every two weeks, using your data and run by the people who will use it.
  • A written status report each week: what was done, what is next, risks that changed, and decisions needed from you, each with a date.
  • A phase gate at the end of each phase, where the acceptance tests are run and the sponsor signs off or sends it back.

When the plan changes, it is re-baselined openly. The old and new dates stay visible, with the reason.

How it fits the rest of a project

Requirements analysis and project planning together form the Scope and plan engagement, a fixed-scope first phase described on our engagements page. If you build with us, the plan becomes the schedule for stage 4, Build and integrate, and stage 5, Test and cut over. If you take it elsewhere, it gives another vendor a schedule and a set of dependencies to quote against.

What we need from you

  • A sponsor who can make go/no-go decisions.
  • Your operating calendar: peak season, closes, counts, holidays and blackout dates.
  • Contacts at each trading partner that will be tested.
  • Your procurement lead times for devices and the name of the person who places the orders.
  • An honest view of what else your team is doing in the same months. Before go-live, use the go-live readiness checklist to confirm the plan’s assumptions still hold.

Scope your project.

Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.