When I say redefine the project I mean make an honest decision as to what needs to be completed and what needs not to be completed, and then just finish according to what has been decided.
Lingering work, unfinished projects, are damaging to team productivity. It is better to turn a page and focus on a new task rather than have a dozen of them 90% complete and still occupying everybody's attention.
I try to set explicit success criteria for any task I create (ie Jira ticket). The task is either done or not done and success criteria are reference.
But this is bit more difficult on scale of whole projects.
I agree with that. Project with vague names like “improve speed” or “make it look beautiful” can go on forever! It’s better they are broken into incremental projects “use bootstrap theme” which can be considered done and then if there is an opportunity to decide to stop working on this kind of work and switch to something else.
With software you are never done so you have to decide to be done!
Lingering work, unfinished projects, are damaging to team productivity. It is better to turn a page and focus on a new task rather than have a dozen of them 90% complete and still occupying everybody's attention.
I try to set explicit success criteria for any task I create (ie Jira ticket). The task is either done or not done and success criteria are reference.
But this is bit more difficult on scale of whole projects.