A new feature is overdue and has been drastically underestimated due to unexpected technical debt. Nevertheless, your most important stakeholder insists on “finishing it” because so much effort has already been invested. How do you deal with that?
Agile Manifesto fourth principle says to adapt to change over executing a plan in the first place. If a project is late, it probably has lost some of its original value to the organization and its customers. In this case, re-evaluating its benefit before pouring more resources into it is a necessity.
If the project still delivers value, I would probably go for it. Keep in mind that there is always competition from the other investment opportunities comprising the Product Backlog. However, continue building it merely because of the prior investment means that the stakeholder has fallen for the sunk cost fallacy.
**Hit the link to send your queries to us about this question, our experts will reach out to you at the earliest!