Achieve 'Done' status by end of the sprint

[Rajasekhar Maddela]

I'm sure this issue must've been addressed before but I would really love to hear your responses again - How do I ensure that by end of the sprint, I achieve both Dev & QC complete for all the stories that were committed during the sprint.

I have been brought into this project which has an inherent of issue lag. Although the dev seems to be fairly on track with few spill overs, the QC lags behind every sprint with most of their work spilling and eventually this has an overall impact on the sprint metrics. Although there's not much that can be done now for the remaining few sprints, I would want to try and ensure we achieve 'Done' status for the next phase of the project

I want to ensure we do the right thing right from the get go. Appreciate any inputs.

[Nic Brough -Adaptavist-]

It depends. 

If you want to run them as a single team, with a single board and velocity, then you're going to have to analyse the time in status, and essentially beat up the QC part of your team - they're underperforming and need help with that (often, more resource, but not always)

The other option takes the blame off the developers - split it into two boards, with the "done" column for developers becoming the "to do" column on the QC board.  Although this will still simply show you that the QC part is failing, it will allow you to measure better and hence report back to your product owners better.