Refactoring is not a Backlog Item

by Jan 25, 2023

Refactoring is not a Backlog Item.

Occasionally I see refactoring items on the backlog. This is very strange to me because it means you are externalizing development details to stakeholders. Stakeholders don’t care about these things.

What then happens is the negotiating with stakeholders which is even weirder. Stakeholders are looking at you with no clue what you are talking about. They need to approve something that’s gibberish to them.

Refactoring should be part of every Backlog Item. Just like every backlog item has analysis, implementation, and testing: it also has refactoring.

Refactoring should be your daily work. Don’t ask permission to be a professional.

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

5 reasons NOT to automate.

5 reasons NOT to automate. This might sound odd coming from me, a staunch advocate of automation. However, beware! If you're handling a process for the first, second or third time, don't rush to automate it immediately. Patience is key. Why? 1️⃣ Automation works best...

read more

Justifying marketing is hard.

Justifying marketing is hard. Generating awareness and traffic is hard to quantify. What is the ROI for marketing? The reason is the distance to the sale transaction. How further away how harder it is to quantify. Conversion is the closest to a sales transaction. They...

read more

Be a T-shape developer

Be a T-shape developer I always advocate developers to specialize when they are becoming senior. But don't lose track of the rest of the playfield. So be broad, know a lot of technologies and areas, but also go deep into one or more. That is a T-shaped developer. Why...

read more
Share This