Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

JIRA StatusDescriptionAssignee/Actions
DraftPO is defining the user story. Not ready for the team to review.

Assignee: PO (or Back-end Lead for back-end stories)

  • Requirements to be finalized and added to story/bug
  • Story/bug to be updated according to the templates
OpenReady for development team to groom.

Assignee: None

  • Story/bug to be reviewed and discussed on Backlog Grooming
  • Requirements to be clarified
  • Acceptance criteria to be understood
  • Estimation to be added
In ProgressDevelopment is in progress

Assignee: Developer

  • Requirements to be turned into working software
  • Acceptance criteria to be met 
  • Tests to be added/updated to ensure 80% coverage
  • Dev verification to be done
  • Critical defects to be addressed
BlockedDevelopment is blocked

Assignee: Developer/PO

  • Blocker to be linked in JIRA via "is blocked by" (if any)
  • Comment to be added to clarify what the blocker is (in case there is no blocking story)
In Code ReviewPR is done and Code Review is in progress

Assignee: Developer

  • PR to be reviewed by other developers
  • Comments to be addressed
  • 2 approves of a PR are preferable
  • PR to be merged
In ReviewPR is merged and updates are ready for review

Assignee: Developer

Assignee: PO

(or Back-end Lead

 or Unassigned/Developer (for back-end stories)

Back-end Story/Bug: the API Tests should be run from master branch or a branch with prepared PR to make sure no regression introduced and new tests meet Acceptance Criteria. If all is okay, the PR is approved and merged to master.
    • UI stories are checked and accepted by PO
    • BE stories are dev verified by implementer and unassigned with a comment proving dev verification is done.
    • BE stories checked and accepted by any available developer and should be assigned to a dev as soon as they are picked up for final verification and acceptance.
  • Story to be closed if requirements are met and it conforms to the definition of done
.
  • Story to be reassigned back to developer (implementer) In Progress in case the requirements are not met
with a comment.
  • Additional stories to be created in case additional requirements/updates are identified while review
.
ClosedStory is accepted by PO and closed

Assignee: PO (or Back-end Lead for back-end stories)

  • Updates can be demonstrated on System Demo

...