Guiding rules for choosing a reliable Magento development partner
This document provides guidance on choosing a reliable Magento development partner. It recommends checking if developers track bugs, use Agile techniques, source control, continuous integration, unit testing, documentation, internal wikis, source code agreements, attend conferences, read programming books, comment code well, and have good references. Quality, price and time form a triangle where you can only optimize two. Magento projects are more sophisticated than average PHP projects due to Magento's features and large ecosystem. Quality is measured by experience and development maturity. Specialization in areas like payments, shipping, products, and checkout is important. Coding standards and experience with extensions and templates should also be checked.
Guiding rules for choosing a reliable Magento development partner
- 1. Guiding rules for choosing a reliable Magento development partner by Dmitry Martsinkevich
- 2. Let’s pay once again! Clients with “redevelopment” requests Large & small scale projects ecommerce.aheadworks.com/
- 3. General advice - do they track the bugs report - do they use Agile and Scrum technics - do they use SVN - do they have continues integration - do they write unit tests - do they document the projects - do they use internal wiki for complicated projects - what kind of agreement about source code do they use offer - check if they attend conferences - do they read programming and management books - do they comment their source code well - do they have good customer’s references - … ecommerce.aheadworks.com/
- 4. Quality triangle Quality Price Time ecommerce.aheadworks.com/
- 5. Quality triangle Quality Choose two Price Time ecommerce.aheadworks.com/
- 6. How does Magento differ? Compared to an average PHP project on any other platform ecommerce.aheadworks.com/
- 7. - more sophisticated system - modern programming technologies used - e-Commerce system (selling function) - high competitive market with many “satellites” companies developing platform add-ons ecommerce.aheadworks.com/
- 8. Quality triangle Magento situation Quality Price Time ecommerce.aheadworks.com/
- 9. How to measure quality ? Quality = Experience + Development approach maturity ecommerce.aheadworks.com/
- 10. 1. Compare your Magento project to developer’s specialization Here at aheadWorks, we classify Magento projects using the following categories: - Payments - Shipping - Product data - Visual enhancements - Checkout ecommerce.aheadworks.com/
- 11. 2. Check the coding standards You might experience problems when developer rewrites core Magento source code. How to avoid? - check the extension code??? - check the extension forums for problems with 3rd party solutions ecommerce.aheadworks.com/
- 12. 3. Check developer’s extensions and templates experience - Number of products - If they developed extensions similar to the ones used in your project - Magento partners network ecommerce.aheadworks.com/
- 13. Additional but not so important - Extensions and projects on old Magento versions ecommerce.aheadworks.com/
- 14. Additional but not so important - Number of certified developers ecommerce.aheadworks.com/
- 15. Additional but not so important - Support’s quality during the pre-sale stage ecommerce.aheadworks.com/
- 16. Thank you! If you have any questions or need help with Magento developer, we would be glad to consult you! Drop me a line: Dmitry Martsinkevich martinkevich@aheadworks.com