Skip to main content

Refactoring for sale

Among the technical list given by Mikael Boman in his post dedicated to product owners, "Practice #4: Refactoring" is for sure, the most difficult to agree with. Version control system, Continuous integration, Automated testing are concepts around tools, consequently their deployment has a visual, understandable, palpable result, so there is no worry justifying their costs.

If you don't get the Practice #6: Collective code ownership, wait for a few years until developers leave your company and then you will get it.

Simple design:
While the indicated article focuses on product owners, the simple design concept is obvious to many of us, but developers could feel it as a bridling of their creativity. While we all need to establish a software knowledge culture, where ideas around code design and patterns are understood, we face a dilemma when it comes to asking for simple creation. I didn't find a good way to recommend, but practices like pair programming and code review can mitigate the ugly and the glittery code. A developer conversation while looking at the code, will free the product from the lack of conception or avoid the all "design patterns" in one "software product" idea.

Previous to entering into the agile/lean world, I didn't find a proper solution to justify a moment to improve the code. Then, based on Lean concepts, I felt desperate because spending time on refreshing the code could be understood like a waste. But the only reality resides in understanding the technical debt and the product complexity.
Some people will argue the refactoring must be embedded in the development tasks and will state that concerned developers will perform this activity by themselves. But such behaviour could hide the iceberg from the product owner or give him a great argument to play the ostrich.
Refactoring must be understood, and the product owner must commit to spring cleaning the code.
If some tasks related to code refactoring are present in the product backlog, it means:
  • Developers have an understanding of the code, so the concerned component is not something anybody would touch anymore due to its ugliness, but only a huge number of code lines that smell bad.
  • Product owner has stepped back, understood the complexity of the component and admitted the technical debt must be lightened,
  • The regression linked with the refactoring will be mitigated by guardrails, like unit tests or user scenario rechecks by testers. Because the testers will have to valid the refactoring tasks, they would have discussed the impact and the use cases affected by this work with the developers. They will not discover the regression nightmare later after a refactoring decided by the developer on his own.
Pragmaticmarketing: Six technical practices you should know about
Scrumalliance: The top six technical practices every Product Owner must know about
Wikipedia: Code refactoring
Wikipedia: Design pattern
Martinfowle: MF Bliki: refactoring
Theagileexecutive: Technical Debt: Refactoring vis-a-vis Starting Afresh « The Agile Executive
Infoq: Refactoring is a Necessary Waste
Agileinaflash : Agile: In A Flash


Popular posts from this blog

Wikipedia statistics

Statistics have been published about Wikipedia and Wikimedia ( PDF Here) . The first lines are: According to comScore, Wikipedia is the fourth most popular web property, world-wide. In June, it served 327 million unique visitors. Wikipedia is available in 266 languages. It is continually expanded by approximately 100,000 active volunteer editors world-wide. The English version alone contains more than 2.9 million articles. All language editions combined contain more than 13.1 million articles. Next to English, the largest Wikipedia editions are German (911,000 articles), French (798,000 articles), Polish (600,000 articles), and Japanese (587,000 articles). For more see the original document . Sources : Resource Shelf : Updated: Key Statistics About Wikipedia and Wikimedia Foundation (September, 2009) « ResourceShelf

Lancement de ProductTank Lyon

Mise à jour 05/05/2023 : Le COVID aura tué ma motivation d’essayer de relancer ce meetup. Peut-être que d’autres le feront.  ---- Tout d’abord, bonne année 2020. Je me suis investi ces dernières années dans les communautés/événements CARA Lyon, MiXiTConf, LyonDataScience et CaféDevOps sur Lyon, France. Ces activités m’ont permis de comprendre les experts de ces domaines, d’apprendre quelques notions fondamentales à travers leurs exposés et d’améliorer mes capacités d’échange avec eux. Product Manager depuis plus de 5 ans, je désire améliorer mes réflexes et compétences dans mon domaine. Le faire à travers des rencontres/meetup est ce que je préfère et j’aimerais retrouver la stimulation des communautés dans cette discipline. En cette année 2020, quelques Product Manager lyonnais, lançons, le meetup ProductTankLyon à Lyon, France. Le réseau ProductTank compte plus de 150 meetups dans le monde et profite des conférences, blog et podcast MindTheProduct. Inscrivez-vous ici , si vou

Learning about Data Science?

This is the end of a beautiful summer, and also one of the warmer recorded in France. I’m continuing my journey in the product management world and today I’m living in the product marketing one too. I will blog about this later. During this first half of this year, I read several articles on big data and started to understand how important the data science discipline is. Being able to define a direction/goal to search, collecting the proper data, then using a collection of techniques to extract something others can’t see - it sounds like magic. Also, when I listened to the Udacity Linear Disgression podcast episode “Hunting the Higgs”, I understood people with these skills can be better at solving a problem than the domain experts themselves. Katie Malone explained that in a competition to solve a particle physics problem, the best results came from machine learning people. Then I read the article about Zenefit on the vision mobile website : “Zenefits is an insurance compan