We’ve refined and evolved our eCommerce replatform project process over 12+ years, dozens of project launches, and many (painful) lessons learned.
1-4 Weeks
We formally transition the project from Sales to Delivery. We ensure that any information gathered during Sales is documented in the project’s Monday.com space and handed over to the Project Team, including Project Overview, Goals, Scope, Timeline, Budget, and Risks.
We set the project’s collaboration foundation, including environments setup and team communication tools.
We bring all Project Team members up to speed with all the project information documented in Monday.com, answer any initial questions, and make necessary updates.
We refine the overall Project Plan and decide on a detailed plan for the upcoming Requirements Gathering Phase, including a list of meetings with agendas and required attendees from the Client’s project team.
We align with the Client on the project’s Vision, Scope, Timeline, and Risks we want to stay ahead of, and we’re ready to dive into the upcoming Requirements Gathering phase.
Business and Data Requirements for multiple topics and areas, including multiple websites/brands/markets, customer, product catalog, pricing, inventory, orders, one-time data migration.
UX/UI Requirements for multiple topics and areas including branding, customer experience, and UX features and functionality for all standard eCommerce webpages: homepage, category listing page, product listing, and search results, product details, shopping cart, checkout, my account pages.
Technical Requirements for the systems integrations and other non-functional requirements.
Data and Business Flows & Rules including Systems of Record, the One-Time Data Migration Diagram, the Ongoing Data Flows Diagram, Business Flowcharts, and Business Entities.
UX & Visual Design, including an Element Collage, a Global Style Guide, and mid-fidelity wireframes for both navigation and buyer flow pages.
Technical Design, including the Systems Integrations Architecture Diagram, the Point-to-Point Systems Integrations Specifications, any Platform Extensions Technical Design, and any relevant technical POCs.
Product Data Modeling, including entities, attributes, and relationships.
QA Testing Plan, including the testing types, tools, and approaches.
We set up the development environments and the CI/CD processes. We coordinate with the platform partners to provision the platform environments and with the Client to get access to the back-office Client’s Test & Staging environments.
We refine the overall Project Plan based on the new information discovered during the Requirements Gathering phase. We decide on a detailed plan for the upcoming Solution Design Phase, including a list of meetings with agendas and required attendees from the Client’s project team.
2-8 weeks
6-24 weeks
We refine the Solution Design deliverables and find resolutions for open items, needs, and blockers.
We do development work to customize, extend, and integrate the platforms. We do QA Testing to ensure adherence to expected quality standards. We perform multiple code deployments and platform configurations in the Client’s Staging and Prod Environments.
We make adjustments and improvements to ensure the website can support heavy traffic per the Client’s expectations.
We do ongoing informal progress reviews with the Client to ensure we’re going in the right direction, and formal Milestone Client Demos & Training Sessions & Documentation centered around customizations of the platform to enable the Client to start the UAT and Content Entry.
We closely manage the project’s scope, timeline, and budget. We track open items, needs, blockers, and risks.
We support the Client during UAT & Content Entry, and we review and prioritize the UAT feedback.
Final deployments, content and data entry, Client UAT, and Launch!
We perform the final Production environment configurations, code deployments, and QA testing.
We clean up test data and perform the final Data Migrations, and we support the Client with the latest content entry activities.
We ensure the Client has the support they need to finalize the end-to-end UAT, and we review and prioritize the UAT feedback.
We execute an extensive cutover plan in the days leading up to the launch date, and we launch the new website!
2-4 weeks
Two-week Sprints
We follow an Agile methodology with 2-week Sprints starting every Tuesday to continue making improvements and enhancements.
We sort all tasks in the order of priority based on the Client’s needs and any dependencies
We document requirements for the upcoming development tasks
We gather information from the Client and review UX & Visual Design Deliverables needed for development
We gather information from the Client and review Tech Design Deliverables needed for development
Questions & Answers sessions with the Project Team to clarify and refine the requirements
We select the tasks that will be included in the next Sprint based on the Backlog Prioritization and the Sprint Capacity.
We do code development and Multiple releases to the Integration environment where we perform QA Testing.
We perform three releases to Pre-Prod on Monday, Wednesday, and Friday of the second week of the Sprint with the highest-risk items, current Sprint UAT feedback fixes + low-risk items, and current Sprint UAT feedback fixes, respectively.
We train the Client on the new functionality and provide support during the UAT process.
