Managing Magento Projects by Viacheslav Kravchuk from Atwix

1,996 views

Published on

The presentation about philosophy, framework, tools and love that are needed to Manage Magento Projects.

Published in: Business, Technology
  • Be the first to comment

Managing Magento Projects by Viacheslav Kravchuk from Atwix

  1. 1. Viacheslav  Kravchuk   from  Atwix Managing  Magento  Projects
  2. 2. About  me
  3. 3. Rudolf  Clausius
  4. 4. Second  law  of     thermodynamics: Rudolf  Clausius
  5. 5. Second  law  of     thermodynamics: The  entropy*  of  the     universe  tends  to  a     maximum Rudolf  Clausius *entropy  ≈  disorder  ≈  chaos
  6. 6. First  law  of  Magento   project  management: Rudolf  Clausius
  7. 7. First  law  of  Magento   project  management: The  disorder  of  the     Magento  project     tends  to  a  maximum Rudolf  Clausius
  8. 8. Analyse Verify Plan Execute
  9. 9. ASAP!!! A-­‐A-­‐A-­‐A! SH*T! WTF???
  10. 10. What  will  save  us?
  11. 11. What  will  save  us? • Philosophy  +  Framework
  12. 12. What  will  save  us? • Philosophy  +  Framework   • Proper  Tools
  13. 13. What  will  save  us? • Philosophy  +  Framework   • Proper  Tools   • Love
  14. 14. Progressive  JPEG Formalised  by  A.  Lebedev
  15. 15. Normal 30% 70% Progressive
  16. 16. Benefits: • Client  sees  progress   • Developers  get  early  feedback   • UX  proven  (or  not)  early   • Changes  are  welcome!
  17. 17. Framework
  18. 18. Scrum
  19. 19. ?
  20. 20. Team     backlog
  21. 21. Project  ader  project Sprints: 1 2 3 4 5 6
  22. 22. Sprints,  focused  on  projects Sprints: 1 2 3 4 5 6
  23. 23. Mixed  sprints Sprints: 1 2 3 4 5 6
  24. 24. Scrum-­‐buf?
  25. 25. Kanban
  26. 26. Kanban We  need  a  board!
  27. 27. Story   Queue Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  28. 28. Story   Queue Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  29. 29. Story   Queue Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  30. 30. Story   Queue Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  31. 31. Story   Queue Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  32. 32. Story   Queue Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  33. 33. Story   Queue Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  34. 34. Story   Queue Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  35. 35. Story   Queue Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  36. 36. Story   Queue PE CE Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  37. 37. Story   Queue PE CE Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  38. 38. Story   Queue PE CE Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  39. 39. Story   Queue PE CE Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  40. 40. Story   Queue PE CE Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  41. 41. Story   Queue PE CE Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  42. 42. Story   Queue PE CE Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  43. 43. Story   Queue PE CE Develop-­‐   ment Teshng Deploy-­‐   ment Done!
  44. 44. Tools
  45. 45. Conhnuous  integrahon
  46. 46. 1-­‐click  deployments
  47. 47. Our  Phing  scripts: github.com/Atwix/phing
  48. 48. Our  Phing  scripts: github.com/Atwix/phing • changes_deployment.xml   • server_changes.xml
  49. 49. changes_deployment • • • • pull  latest  changes  from  repository   backup  modified  files  on  server   merge  branches  of  Git  repository   deploy  changes  to  the  server
  50. 50. server_changes • compare  files  from  the  latest   deployment  with  files  on  the   remote  server
 • push  any  changed  files  on  the   remote  server  into  a  separate  Git   branch
  51. 51. What’s  next?
  52. 52. #NoManagers
  53. 53. Daniel  Pink.  Drive.
  54. 54. Purpose Autonomy Mastery Daniel  Pink.  Drive.
  55. 55. Thanks  for  inspirahon Aleksey  Krivitsky www.krivitsky.com
  56. 56. Thanks  for  inspirahon Aleksey  Krivitsky www.krivitsky.com
  57. 57. Thanks  for  inspirahon Aleksey  Krivitsky www.krivitsky.com Rudolf  Clausius
  58. 58. Thanks  for  listening! @slkra

×