Where the design becomes a working store
This is the sixth step of how we run a Magento project. The build happens here, in two-week sprints with a demo at the end of each, code review on every pull request, automated tests and continuous integration. It is the longest phase, and the one where you can watch the store come together week by week.
Building it, in the open
Everything up to now has been planning. This is where the engineers turn the design and the plan into a real Magento store running on staging. It usually takes eight to fourteen weeks for a new store, longer for a replatform or an enterprise build, and we share a precise sprint plan once the planning phase is done.
The thing that keeps a build on track is discipline, not heroics. We work in a steady cadence and you see real, working code every week rather than a status update that says it is nearly done.
How we engineer
Led by the engineering team. These practices run on every project, not just the big ones.
Two-week sprints
A steady rhythm of sprint planning, a demo at the end, regular retros and daily standups. You see working code every week, not at the very end.
Code review on every pull request
Every change a developer writes gets read by another senior developer before it reaches staging. It catches bugs and inconsistencies early, while they are cheap to fix.
Automated tests and CI
Unit, integration and end-to-end tests run on every push. Continuous integration catches regressions before they land in the main branch.
Continuous deployment to staging
Every merge to the main branch deploys to staging on its own, so you can look at the latest progress whenever you want without asking anyone to push it for you.
What you have at the end of Phase 6
You get a fully working Magento store on a staging URL that your team and stakeholders can test daily, a test suite with coverage you can actually look at, technical documentation covering the architecture decisions, integration points and how to set the environment up, and access to the source control and the CI pipeline.
You own the code from day one. There is no point at which it is locked away from you.
Common questions about this step
How long does development take?
Roughly eight to fourteen weeks for a new store, and fourteen to twenty-two for a replatform or an enterprise build. We share a precise sprint plan after the planning phase.
Do you write tests?
Yes. Unit, integration and end-to-end tests on the critical flows, running on every pull request through CI. We share the coverage reports with you.
Can our own developers work on the code?
Yes. Plenty of clients have in-house developers work alongside us. The same code-review standards apply to everyone.
What if a sprint slips?
We raise it at the next demo with the cause and a plan to recover. Slips happen on real projects; hiding them is what actually sinks them.
Want a build you can watch progress
Tell us what you are building and we will set up a technical review. You will come away with an estimate and a clear sprint plan.