Agile Magento projects on a fixed budget @ Meet Magento Poland

Meet Poland - Agile_LargeMeet Magento Poland is a conference focused on eCommerce, the Magento platform and its ecosystem. Our senior solutions’ architect Sebastian, recently attended the Meet Magento conference in Poland to deliver a talk about Agile Magento Projects on a fixed budget. Read his thoughts below.

Blog - image - Meet Magento Poland - image 8

When considering the migrations and upgrades from Magento1 to Magento2, it is important to focus on a minimum viable product (MVP) rather than a complete rebuild of the original site. An agile project structure supports this approach and creates a relationship based on trust between the agency and client, as the process is so collaborative. A waterfall contract, on the other hand, is about protection of the parties involved and places a large emphasis on a fixed scope. It’s important to bear in mind that requirements for projects always change, so a fixed scope rarely happens for larger projects. Once the scope changes, all sides of the iron triangle are affected. Using a fixed budget and a number of story points with a focus on delivering an MVP, allows the project to evolve and can accommodate changing requirements and needs without ongoing budget discussions.

Why Agile?

In an agile mode, good ideas are not perceived as a threat – they’re encouraged as they help a project evolve and learn. In a typical waterfall project, which is set up for clearly defined project plans, a disruptor like a great idea can’t be accommodated. With an agile approach, changing requirements can be easily incorporated as the approach is so collaborative and caters for many touchpoints – any uncertainties at the start of the project can be compensated for during the project. The agile model is supported with a clear set of events, which require ongoing customer collaborate with their product teams. This ensures that every stage is clearly streamlined towards the development of a viable MVP, focused only on the shopping and transactional flow of an eCommerce site.

Benefits for the agency:

For the agency, benefits of agile stack up. Planning time is reduced, so development can commence quickly. With clearly defined touchpoints between the customer and product owner, the deliverables are turned over faster as there is constant feedback. The developers are empowered through the use of SCRUM and foster a collaborative and creative environment. Risks and client frustrations are also reduced in this approach as the client is involved throughout the entire process and can see their product come together.

Benefits for the client:

The benefits look very positive for the client too. Not only is the client able to see the progress of the project quickly and in a predefined rhythm, there is a large focus on collaboration with the project teams, which encourages open conversations and trust. The agile approach allows for scope changes without budget impacts, so great ideas are welcome. The client is always able to align the backlog with their urgent business needs, so the project becomes quite literally, agile, as it re-prioritises. And with so much ongoing testing throughout the project, there is a shorter UAT time at the end, saving the client some budget to put towards developing the MVP.

What you can get rid off in an agile project

The agile approach cleans up a few areas, so by adopting this model you can say goodbye to some annoying aspects of the project. Long phases of technical design and documentation are no longer required at the start of the project. And the client can rest assured that unwanted features that seemed like a good idea at the start of the project don’t have to make it to the end. There is no need for ongoing scope and budget discussions once the project has been signed off. The user acceptance testing phase at the end of the project is significantly reduced due to ongoing testing and sprint reviews throughout the course of the project. You and the client get to see the product come together, so there’s no more big bang releases at the end of a long project. Nor is there a need for a long handover at the end.

Blog - image - Meet Magento Poland - image 12

Conclusion

An agile approach is a great way to approach an upgrade from Magento1 to Magento2 when the focus is specifically to develop an MVP and get to market fast. A short time to market is crucial for a lot of customers, and the agile model supports this urgency.

Contact us or call us on 1300 624 368 for more information about MVP on Magento 2.

Sebastian Klett
Solution Architect – Balance Internet

SebatienPhoto

We’d love to work
with you
enquire now enquire now
OR CALL US
1300 624 368