When to schedule a Node refactor around feature work
Refactoring sprints fail when they compete with immovable release dates. Teams we work with in South Africa often face December code freeze and February budget renewals—plan around those anchors.
After a review, not instead of one
Without a ranked backlog, refactor work drifts into taste debates. Schedule implementation only once findings are agreed with product leadership.
Bundle by risk, not by folder
Three modules that touch payouts matter more than renaming a utils directory. Align sprints to incident history and compliance deadlines.
Keep a feature lane open
Pairing works when one squad member continues small tickets while two others refactor with us. Zero feature throughput invites cancellation pressure.
Measure with on-call signals
Pages triggered, queue age, and duplicate transaction counts should move after a sprint. Vanity metrics like lines deleted rarely convince finance.
Our engagement path shows how review and sprint weeks connect.