Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Igor Bondarenko
Process organization of the Magento
modules development.
About Myself
• 10 years in IT
• 2 years in Magento
Development
• Head of Business
Development in Neklo
What would I talking
about?
• How to choose an idea
• Selecting a tools
• How to prepare a team
• Development processes
• ...
Assign choosing of
ideas to the business
development team
After choosing the idea,
calculate the economic
feasibility of extension
development
Do NOT delegate
choosing of the idea to
developer
The idea is chosen, it's time to start developing. But
before you start designing, you must define the tools
Self-developed tools
• Mageinstall
• Cloud VM Server
• “Custom Store”
• QA Test Scripts
Available for all tools
• VCS
• Developer Toolbar
• Log Popup
• Turn Developer Mode On
• Setup Issue Tracker
Formation of the team.
Use narrowly skilled
professionals.
Working with a team of 2
or more people
• Select Team lead
• Split Magento Versions
• Tasks decomposition
• Assign tasks t...
Team of one developer
• Start working with minor Magento versions
• Develop extension sequentially:
• Backend
• Admin part...
What about Magento 2 ?
The speed and cost of
development will not change
Start extensions
migration form the
simplest solution
Next slide will be a
boring slide for
developers only.
How to provide compatibility
with third-party extensions?
What should developers
team do?
• Use integration through events
• Do not use Rewrite
• Use frontend integration life
hack...
What should QA team do?
• Test on “working” Magento
• Test compatibility with top
rated extensions
• Do NOT test compatibi...
• Code Review
• Use Code Style
• Pair Programming
Testing of extensions
Key points of
testing process
• Stop development until the end of
first QA iteration
• Switch project during first
iterati...
Test Automation
• Tests should be written by QA
Team
• Don’t use complex
frameworks:
• Short-term activity
• Skilled QA
• ...
What to use for test automation?
Use Selenium IDE or SpiderTest:
•Powerful test recorder
•Testers should not have
programm...
Ready for release?
But don’t you forgot nothing?
Forgot to test readiness
for loading in Magento
Connect
• Build a package
• First load and wait for
approve, then promote
...
Key success factors
• Perform business analysis
• Using high-quality and thoughtful
tools
• Using narrowly skilled
profess...
Thank you for attention!
Skype: igor.bondarenko1
E-mail: igor.bondarenko@neklo.com
Igor Bondarenko - Process organization of the development modules specific to Magento 2
Igor Bondarenko - Process organization of the development modules specific to Magento 2
Upcoming SlideShare
Loading in …5
×

Igor Bondarenko - Process organization of the development modules specific to Magento 2

301 views

Published on

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.

  • Be the first to comment

Igor Bondarenko - Process organization of the development modules specific to Magento 2

  1. 1. Igor Bondarenko Process organization of the Magento modules development.
  2. 2. About Myself • 10 years in IT • 2 years in Magento Development • Head of Business Development in Neklo
  3. 3. 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
  4. 4. Assign choosing of ideas to the business development team
  5. 5. After choosing the idea, calculate the economic feasibility of extension development
  6. 6. Do NOT delegate choosing of the idea to developer
  7. 7. The idea is chosen, it's time to start developing. But before you start designing, you must define the tools
  8. 8. Self-developed tools • Mageinstall • Cloud VM Server • “Custom Store” • QA Test Scripts
  9. 9. Available for all tools • VCS • Developer Toolbar • Log Popup • Turn Developer Mode On • Setup Issue Tracker
  10. 10. Formation of the team. Use narrowly skilled professionals.
  11. 11. Working with a team of 2 or more people • Select Team lead • Split Magento Versions • Tasks decomposition • Assign tasks to skilled person
  12. 12. Team of one developer • Start working with minor Magento versions • Develop extension sequentially: • Backend • Admin part • Frontend
  13. 13. What about Magento 2 ?
  14. 14. The speed and cost of development will not change
  15. 15. Start extensions migration form the simplest solution
  16. 16. Next slide will be a boring slide for developers only.
  17. 17. How to provide compatibility with third-party extensions?
  18. 18. What should developers team do? • Use integration through events • Do not use Rewrite • Use frontend integration life hacks: • Layout substitution • JS Injection
  19. 19. What should QA team do? • Test on “working” Magento • Test compatibility with top rated extensions • Do NOT test compatibility with all of extensions
  20. 20. • Code Review • Use Code Style • Pair Programming
  21. 21. Testing of extensions
  22. 22. 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
  23. 23. Test Automation • Tests should be written by QA Team • Don’t use complex frameworks: • Short-term activity • Skilled QA • Negative ROI
  24. 24. 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
  25. 25. Ready for release? But don’t you forgot nothing?
  26. 26. 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
  27. 27. Key success factors • Perform business analysis • Using high-quality and thoughtful tools • Using narrowly skilled professionals • Don’t forgot testing
  28. 28. Thank you for attention! Skype: igor.bondarenko1 E-mail: igor.bondarenko@neklo.com

×