Skip to main content

Standard approach for tracking half-done features in Azure DevOps [Resolved]

We practice Scrum (SAFe) and use Azure DevOps to track features and PBIs. The team is unsure of how to handle features which have been started but not finished at the end of a program increment.

Half the team wants to move the feature back to the program backlog, but we then lose the ability to report on effort already spent on the feature, and the fact that our forecasts were wrong.

The other half of the team wants to clone the feature...which polluted our backlogs.

Is there any standard way to do this? I’d like an approach that doesn’t confuse new team members if possible.

Question Credit: Kye
Question Reference
Asked July 9, 2019
Posted Under: Programming
1 Answers

Your Answer