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.

Refactorisation de code : comment l’intégrer à sa roadmap Produit ?


Published on


Pourquoi le faire & quels sont les impacts sur le mobile ? Videdressing nous fait un retour d'expérience sur son projet de refonte technique de ses briques de paiement & cycle de vie de la commande.

Talk par Jérôme Joly - Product Manager @VideDressing

Published in: Marketing

Refactorisation de code : comment l’intégrer à sa roadmap Produit ?

  1. 1. How the product team prioritized a technical project to optimize the business @jolyjerome
  2. 2. Why and How to prioritize a refactoring project “A Product Manager always pays his debts”
  3. 3. Who are we?
  4. 4. Key numbers Describe platform (Desktop, MWS, IOS, Android) Mobile Platform: - 60% traffic,
  5. 5. Product & Tech Organization ● 2 teams (product & tech) working on the same floor, 1 common spirit ● Agile organization: ○
  6. 6. Why should we refactor the code?
  7. 7. plateforme hét Each platform had his own payment module!
  8. 8. Statement
  9. 9. What is the scope of the refactoring?
  10. 10. How can we prioritize?
  11. 11. Explain executive team & stakeholders we will not release big feature for the next 9 months
  12. 12. ● Stop or report other projects ● Task force dedicated during 9 months ● Don’t solve bugs on legacy ● Decrease momentarily the quality of service to improve it afterwards Impact
  13. 13. Progressive activation of Means of Payment ● Depending on the business impact and the risk incurred, we have prioritized the deployment of payment methods by platform ● Think about Feature Flipping & “feature flooring” at the beginning of the project
  14. 14. 2016 2017 Q3 Q4 Q1 Q2 Q3 Q4 Desktop (50%) Mobile web (20%) App IOS (25%) App Android (5%) CB 3X & 4X (22%) Paypal (23%) CB 1X (50%) Wallet (5%)payment method: Launch Roadmap
  15. 15. Results ● 95% of orders are now processed on the new system - bug free - easy to track/reconciliate ● Very positive impact on Customer Care contact rate ● Enabler for Mobile platforms better performance - From 40% to 50% of mobile contribution in sales - Allows mobile-first strategy as the platforms are now upgraded ● The user/order lifecyle is now readable from the inside, not only developers
  16. 16. Final State Machine
  17. 17. What we have learned?
  18. 18. ● Postponing information to board/exec team on platform state ● Take too much time to decide to launch the refactoring ● Spending too much energy to solve bugs instead rebuilding ● No unified & shared documentation on business process (the process draw was the first “release” of the project) and kill some old myth about our process ● Even if stakeholders were involved for project scoping, we did not involved them enough/on a regular basis once the project was in development Mistakes
  19. 19. 5 rules to respect - Involve stakeholders - Stay Focus and protect the team - Don’t feed the monster (Legacy) - Evangelize new FSM (Final State Machine) - Make Code Review
  20. 20. Q&A