Over the years of my working experience, I have faced the fact that the way development process is organized differs greatly from company to company. At the same time, if we take the development of extensions as a separate subject it may seem to be a short-term activity, which has no particular nuances. In practice, it turns out that the development of an extension is not at all that simple. I want to talk about how we have organized the process of extensions development at our company, and give some recommendations on how to optimize the development process so that to reduce costs and improve your product quality. My report covers the following aspects of the development process: - getting prepared for development: what idea to choose and what to do next - role separation within a team - tools - development of an extension - testing - differences in approaches for Magento and Magento 2 All practices are divided into groups, so listeners can choose those of them that will harmoniously fit into their workflows.

2. Igor Bondarenko
Process organization of the Magento
modules development.

3. About Myself
• 10 years in IT
• 2 years in Magento
Development
• Head of Business
Development in Neklo

4. What would I talking
about?
• How to choose an idea
• Selecting a tools
• How to prepare a team
• Development processes
• Advises to developers
• QA and Testing
• How to release an extension

5. Assign choosing of
ideas to the business
development team

6. After choosing the idea,
calculate the economic
feasibility of extension
development

7. Do NOT delegate
choosing of the idea to
developer

8. The idea is chosen, it's time to start developing. But
before you start designing, you must define the tools

9. Self-developed tools
• Mageinstall
• Cloud VM Server
• “Custom Store”
• QA Test Scripts

10. Available for all tools
• VCS
• Developer Toolbar
• Log Popup
• Turn Developer Mode On
• Setup Issue Tracker

11. Formation of the team.
Use narrowly skilled
professionals.

12. Working with a team of 2
or more people
• Select Team lead
• Split Magento Versions
• Tasks decomposition
• Assign tasks to skilled person

13. Team of one developer
• Start working with minor Magento versions
• Develop extension sequentially:
• Backend
• Admin part
• Frontend

14. What about Magento 2 ?

15. The speed and cost of
development will not change

16. Start extensions
migration form the
simplest solution

17. Next slide will be a
boring slide for
developers only.

19. How to provide compatibility
with third-party extensions?

20. What should developers
team do?
• Use integration through events
• Do not use Rewrite
• Use frontend integration life
hacks:
• Layout substitution
• JS Injection

21. What should QA team do?
• Test on “working” Magento
• Test compatibility with top
rated extensions
• Do NOT test compatibility with
all of extensions

22. • Code Review
• Use Code Style
• Pair Programming

23. Testing of extensions

24. Key points of
testing process
• Stop development until the end of
first QA iteration
• Switch project during first
iteration of testing
• Starting from the second iteration
of testing start to work in parallel
with the QA team

25. Test Automation
• Tests should be written by QA
Team
• Don’t use complex
frameworks:
• Short-term activity
• Skilled QA
• Negative ROI

26. What to use for test automation?
Use Selenium IDE or SpiderTest:
•Powerful test recorder
•Testers should not have
programming skills
•Developers could use any
programming language
•Lightweight scripts
•Easy to attach scripts to defects
•Free tools

27. Ready for release?
But don’t you forgot nothing?

28. Forgot to test readiness
for loading in Magento
Connect
• Build a package
• First load and wait for
approve, then promote
• Test installation file per
file

29. Key success factors
• Perform business analysis
• Using high-quality and thoughtful
tools
• Using narrowly skilled
professionals
• Don’t forgot testing

30. Thank you for attention!
Skype: igor.bondarenko1
E-mail: igor.bondarenko@neklo.com