Adobe Commerce and Magento Open Source Development

Our team is ready to work with you…

Our internal team are highly skilled and experienced individuals, which include Adobe Commerce certified back-end and front-end developers and solution specialists.

Discovery

We will work with you initially to understand whether the project will be run as an Agile or a more traditional waterfall build.

Agile

• We would start breaking down the requirements into stories/tasks, group them into epics and begin detailing them with specific requirements, questions and use cases. This would form the backlog, which would then be reviewed and prioritised based on:
• MoSCoW analysis to determine MVP and base priority
• Complexity, with complex tasks being prioritised
• Dependencies, with tasks that have more dependent tasks being prioritised
• We would then estimate the tasks (we work in hours or t-shirt sizes rather than story points, to fit in with the wider operational structure of the studio), identify how many sprints are available ahead of the deadline (minus project initiation, UAT, launch, etc.), and use this as a basis to understand how many resources would be required to deliver the project.

Waterfall

• We would write a complete technical specification and use this as the basis for estimation of the effort required to deliver the project.
• Once the scope of work had been defined, we would prioritise tasks using the same approach as above (MoSCoW, complexity, dependencies).

Considerations

• Agile: greater flexibility, less lead time to start development, costs based on Time and Materials (by sprint)
• Waterfall: fixed-cost and fixed-scope, lead time required to define deliverables, costs based on deliverables