🎟️Kanban board and ticket flows

All about Jira Kanban Board and Ticket Work Flow.

Kanban Board

• WIP (Work in Progress) limits

  • forces people to get things "done"

• reduce the amount of work "nearly done"

• optimizes process flow

• avoid bottlenecks

• pull system

Development Board

QA Board

• To Do

  • Cards that should be worked on.

  • These are the cards that were moved from Back Log because they have clear the laid out requirements.

  • To do epic cards are already gone through a grooming session

• In Progress

  • Currently, working on.

  • Merged PRs are being tested by developers

• Ready for QA

  • If the devs finished testing their merged PRs.

• QA In Progress

  • Cards that are currently being tested.

• Failed

  • Cards that were failed to comply with the given acceptance criteria

• Done

  • Cards that successfully pass the acceptance criteria

  • Ready for release

Different Types of Jira Cards

• 🟣Epic

  • Should be a small atomic feature

• 📗Story

  • A function from a user's perspective that supports the Epic

  • A USER STORY is a way to explain the function from the user's perspective

  • Title should be in this format: <User><Action><Story/Feature>

  • User story Example:

  As a member, 
  	I want to have a validation of username in the login form, 
  	so that I could know beforehand that I had the wrong username format.

  It follows a pattern As a [persona] , [I want to ..] , [so that..]

  • Acceptance criteria are ALSO written here to eliminate the assumptions presented by a user story.

  • Acceptance Criteria Example:

  • If possible to format it in E2E Automation formatting

  GIVEN a username with no numeric characters
  WHEN a member tries to pause for 3 seconds
  THEN there is an error message under the username's text field,
  	"Invalid Username: No numeric characters"

  • Example for both User Story and Acceptance Criteria.

• 📘Sub-Task Card/Task Cards

  • A card for dev, usually this is like a technical implementation from a dev

• 🐞Bug

  • It should be created when a story card is already released.

  • If possible, make it as a child card under the Epic. Don't just link it.

  • It should not be linked on the story cards.

  • Sample Format

• 💡Defect Card

  • It should be created under a Failed Bug card/ Story card.

  • If possible, make it as a child card under the Epic. Don't just link it.

  • It should not be linked on the story/bug cards.

• ♨️Hotfix

  • A critical priority card that needs more attention.

  • It ignores most of the columns/status

  • It ignores most of the development processes