Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1

Howdy team, I've set-up two workflows:

For tasks and sub-tasks which tend to be individual contributor, one and done type of activities, we'll use the following very simple flow:

That is you can use the status to keep track of where you are on a task or sub task, but no one else is dependent on this (or likely to check it).

For stories and bugs on the other hand where we'll need to think about delivery in a more holistic fashion, so we'll use the following flow:

Roughly speaking, it’ll look like the following:

  1. At sprint planning, we'll assign an owner and set the status to "To do" (if it isn't already)

  2. When you pick up and start working the story, you (the owner) should transition it into "In progress"

  3. When you're ready to check the code in, you'll make a pull request, put it in QA, and assign it to Craig

  4. If the story meets all the acceptance criteria and passes integration testing, Craig will set it to "In Review". Otherwise, he'll add comments on how it failed to meet requirements, set the status to "In Progress" and re-assign the story back to the original owner

  5. At sprint review, we'll walk through all stories in "In Review" status

  6. I'll then set them to "Done" (if they meet requirements) or I'll set them back to "To do" or "In progress" for a future sprint if they don't

  • No labels