Sprint planning for various teams using various statuses

[Rita Bagdi]

Hi All,

There is a use case we need help with. We have a workflow containing several different statuses, each for a different responsible/assignee. We plan in 2-week sprints and in many cases a task goes through 2-3 statuses during this period, but it does not reach the final status by the end of the Sprint. (Keeping many statuses in the same task is an industrial requirement)

Our problem is that even an activity for a certain status is completed - the task will not appear as completed in reports.

In following statuses what should we do with the original and remaining estimates?  Has anyone have solution for this use case? 

Thank you,

Kind regards,

Rita

[Nic Brough -Adaptavist-]

So we need to be very clear about what you are doing.

It's fine to have a load of different status, but my first question is "why are you not reaching the 'done' status by the end of the sprint"? 

The whole point of a sprint is that you commit to delivering a set of work-items by the end of it.  If you do not, you have failed to meet (part or all of) the sprint goal, and you must spend time working out why you have failed.  You should only be failing to reach the final status when something you cannot predict happens (for example, Dave falls ill, howling bug needs fixing in production, etc). 

So, why are you failing the sprints regularly?

(We'll come on to the estimates later, they're not really relevant until you've fixed your estimation and sprint processes)