Jira Workflow

Download:

The Jira workflow uses the following columns:

Open

That work through a board with the following columns:

Open

• To Do - Cards that have not been refined and are not yet ready to be worked on.

• Refinement has 2 statuses:

  • Refinement - Cards that are currently being refined by a project owner.

  • Refined - Cards that have been refined, but not yet pointed.

• Ready - Cards that are pointed and ready for development.

• In Progress - Cards under active development

• Review - Cards that are being reviewed by a peer.

• QA / UAT

  • QA - Cards that are being reviewed by the QA team.

  • UAT - Cards are being reviewed by the customer or someone who speaks for the customer

• Blocked - Work that is blocked and waiting to immediately start when unblocked.

• Done

  • Done - Work that has been officially completed and released to prod.

  • Canceled - Work that was decided to not pursue.

Open

Unless otherwise instructed, you should focus on completing your cards to the “right” of the workflow first, and only working on cards to the “left” of your rightmost card if you are blocked.

For example, if you have a card that is in QA or Review, you should remind and/or schedule time with the people who might review that card to help see it across the finish line. You should also attempt to review other people’s work at your earliest convenience. You don’t need to stop what you are doing to review someone else’s work, but trying to review within a day of being asked for review is a good benchmark.

The following walks through what to expect as cards transition between columns.

When a Product Owner determines they need to get a story ready for development, they will update the story’s status to REFINEMENT and assign themselves. This can happen at any time, but often happens during https://wiki.at.bitovi.com/wiki/spaces/BITAPP/pages/471957620 .

Assigned To - Product Owner

The Product Owner has added enough detail to the card to communicate what needs to be done. The detail needed is documented in the https://wiki.at.bitovi.com/wiki/spaces/BITAPP/pages/472580235 . Ultimately, the engineering team will decide if it’s Ready for development in the next phase. The refined story may be assigned to a team member for them to review and estimate in the next step.

Assigned To - (optional) a team member to estimate.

During refinement meetings, the project manager will review cards with the team. If the team is able to estimate the work, the card will be pointed using the https://wiki.at.bitovi.com/wiki/spaces/BITAPP/pages/114983127 and moved into READY. Sometimes, if there’s a particular person well suited to the card, the card will be assigned to an individual.

Assigned To - (optional) The team member expected to do the work

Cards that are unassigned can be picked up by any developer. Cards at the “top” of the column should be chosen first (unless there’s a particular reason to choose lower cards). Once development has begun, it should be moved to the IN PROGRESS column.

Assigned To: The team member doing the work

Initial development is complete once the:

• acceptance criteria is met, and

• the https://wiki.at.bitovi.com/wiki/spaces/BITAPP/pages/114983160

have been met.

Once development is complete:

• Link to the PR in the Jira story

• Move the card to Review

• If known, assign the story to the developer who should review the story. If not known, assign to the project manager and tell them to find a developer to review.

Assigned To - A peer for review or project manager

If you are code-reviewing a story, make sure the code appears to meet the coding standards of the project and the definition of done. If it does:

• MERGE the Pull Request (The approver “owns” code quality)

• Move the card into QA

• Assign the card to the QA practitioner, or leave empty for the product owner to assign.

Assigned To - QA practioner

Test that the code you wrote is working in the QA environment against the acceptance criteria. As part of the pull request (and the definition of done), the developer should list any impacted areas that need a regression test.

If things are still working:

• Move the card into UAT

• Assign the card to the product owner

Assigned To - Product Owner

• Check if things are working in staging.

• If they do, push to prod [LINK TO DEPLOYMENT]

• Check that it works in Prod, then mark as DONE

For a wide variety of reasons, a story might not be completed. When this happens, mark it as Canceled

Assigned To - (optional) Product Owner