Justyna Walkowska

Product Managers' Eternal Battle with Refactoring

Is refactoring a black hole for development time? This talk shows how to measure its business value and make strategic roadmap decisions with your engineering team.

Product Managers' Eternal Battle with Refactoring
#1about 2 minutes

Defining refactoring beyond the strict technical term

The formal definition of refactoring is contrasted with its broader, common usage in development teams.

#2about 1 minute

The conflict between product and engineering over refactoring

Product managers often fear refactoring while engineers worry about becoming a feature factory without it.

#3about 2 minutes

Exploring five common approaches to handling refactoring

Five strategies for managing refactoring are presented, from allocating a percentage of time to making it a roadmap item.

#4about 2 minutes

Differentiating good and bad reasons for refactoring

Good refactoring is driven by clear needs like reducing risk, while bad refactoring is often motivated by chasing new trends.

#5about 2 minutes

How to measure the business value of refactoring

Refactoring must have a measurable business impact, such as reducing production issues or speeding up developer onboarding.

#6about 1 minute

Final advice for engineers and product managers

Engineers must articulate the business value of refactoring, and product managers must engage to understand the technical reasoning.

Related jobs
Jobs that call for the skills explored in this talk.

Matching moments

Featured Partners

Related Videos

Related Articles

View all articles

From learning to earning

Jobs that call for the skills explored in this talk.