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

Improving Optimization?

Improving Optimization? The traditional steps of Optimization: 1. Eliminate 2. Automate or 3. Delegate What if we added a missing element? Simplify. Before automating a convoluted workflow or delegating a tangled task, strip away the unnecessary. Make processes leaner...

read more

Unit tests for Dataverse plugins?

Unit tests for Dataverse plugins? I must admit, I almost never write unit tests for Dataverse plugins. Plugins are often quite simple, testing them in isolation is not particularly useful. Often you only test a couple of if-statements. Unit tests don't bring a lot of...

read more

New Dynamics 365 browser extension

New Dynamics 365 browser extension I'm trying out the new -Power Roles- extension and it looks very promising. You browse to a Dynamics 365 (or Power Apps) app and then you press -record-. It will then monitor all the action you do in the app and propose which...

read more