We use the kanban board to track our engineering tasks and stories. We are currently using a workflow like this:
TODO -> IN PROGRESS -> CODE REVIEW -> UAT -> READY FOR DEPLOY -> DEPLOY (resolution)
This worked great but lately we've had a number of very large features that cannot be deployed until all the work is completed. In these cases using a DEPLOYED column no longer makes sense.
We have been using stories to track deployable features but often the tasks linked to the story are not ALL finished within a single sprint so the feature is not deployed. Although the tasks for that sprint have been finished, they appear to not be finished when the sprint is closed. This makes it hard to track how much work any given engineer has completed in a sprint.
To keep solutions open ended, I'll just outline our goals:
Open to anything that can accomplish these goals.
Thanks!