This downloadable ecommerce replatforming checklist is a step-by-step guide for ecommerce platform vendor selection and implementation agency (systems integrator) RFP process. Benefit from 16+ years’ experience in delivering ecommerce projects.
In this replatforming checklist you’ll get:
- Step-by-step actions for your ecommerce replatforming project
- Good practice insights to boost your project management expertise
- A structured checklist to evaluate your current approach & identify gaps
Prefer a download? Get your copy of the 26-page checklist.
This checklist gives you a set of standards against which to evaluate your own project set-up and delivery, helping you ensure you’ve applied the right discipline and attention to detail to help drive a successful outcome.
For practical ‘how to’ advice, you can use my 10 part ecommerce replatforming video masterclass series.
checklist aligned with project stages
It pays to have an over-arching set of principles for your replatforming project and capabilities that need to be satisfied within the project team. To help ecommerce teams plan for a business critical project, I’ve translated my multi-project experience into a structured checklist to cover 10 sequential stages for project delivery.
For each stage, you’ll find a checklist and a summary explanation of what is required. Each stage has an accompanying masterclass video, which is free to watch. Use the quick links if you want to fast track.
- Project set-up & governance.
- Project budget & scope.
- Project management essentials.
- Business requirements capture.
- Platform selection.
- Building a TCO cost model.
- Platform due diligence.
- Partner selection RFP.
- Partner due diligence.
- Risk analysis and mitigation.
stage 1: project set-up & Governance
Put essential controls in place from the outset. It’s important to ensure your project has a clear structure, with a board-level sponsor appointed to ensure it gets the buy-in needed from across the business, as well as ensuring external providers take it seriously.
The age-old saying, ‘Act in haste, repent at leisure’ applies here. Think carefully about the guiding principles for your project, and ensure that decisions made at this stage are agreed unanimously, are realistic and achievable.
|1||Appoint board level Project Sponsor.|
|2||Appoint senior stakeholder with ecommerce experience as Project Owner.|
|3||Define and agree the project goals and objectives.|
|4||Define success outcomes and how they will be measured.|
|5||Define KPIs to measure success and benchmark where applicable.|
|6||Define the project stakeholder groups and individual stakeholders.|
|7||Define the project governance structure and process.|
|8||Agree if Steering is required and which stakeholders will be on the Steering Group.|
|9||Define reporting mechanisms and frequency.|
|10||Define escalation path and responsibilities.|
|11||Define communication requirements, processes and tools.|
|12||Create a governance charter for the project and distribute to stakeholders.|
stage 2: project budget and scope
With a clear structure in place, you now need to define the parameters for the project.
Start with budget. Identify all the cost streams applicable to the project, get the maximum amount signed off with the Project Sponsor and Finance Director, and communicate this to the project team. Ensure you build-in contingency to cover unforeseen expenses or minor scope creep; even with smart planning projects can incur additional cost.
Next define the scope of the project. Think about what must be delivered for phase 1, and what else you want to be included in scope but which can be deployed in later releases. This will be your reference point to help stakeholders focus on what’s most important.
|1||Define project cost streams e.g. initial build, licensing, hosting etc.|
|2||Agree and sign-off realistic budget for each stream with Sponsor and Finance Director.|
|3||Document which budget pots each cost stream is allocated to, and who owns the pot.|
|4||Agree a contingency budget to cover project scope creep or unforeseen issues.|
|5||Create a high-level definition of the project scope.|
|6||Agree prioritisation criteria for scope items e.g. MoSCoW.|
|7||Review scope with key stakeholders and refine to create an approved scoping document based on the agreed prioritisation criteria.|
|8||Get scoping document approved and signed-off by Project Sponsor.|
|9||Review project phasing and define your MVP (minimal viable proposition) version of the project scope.|
|10||Use prioritisation criteria to define priority order for non-MVP scope items.|
|11||Flag high-level requirements in the scope that need further business case justification.|
|12||Work with appropriate stakeholders to assess business case for each requirement.|
|13||Make recommendation to Steering and Project Sponsor based on the outcome of business case assessment.|