🪃
Engineering Playbook
  • Engineering Playbook
  • Agile Development
    • Kanban from the start
    • Daily Stand-up
    • Collaboration
      • Mobile Designer X Mobile Developer
    • Backlog Management
      • Backlog Refinement
    • Card Management
      • Epics
      • User story
        • Collaboration experience with acceptance criteria
        • Proper acceptance criteria
      • Task
      • Bug
      • Hotfix
      • Sub-task
      • Defect
      • Columns
      • Card organization
      • Column Limit
      • Board Templates
    • Pull System Task Assignment
    • Retrospectives
    • Team Agreement
      • Working Agreement
      • Definition of Ready
      • Definition of Done
    • Agile Metrics
  • Github
    • Source Control
    • Merge Strategies
    • Versioning
    • Code Reviews
      • Author's Checklist
      • Reviewer's Checklist
  • Documentation
    • GraphQL as an API Doc
  • DevOps
    • Continuous Integration
Powered by GitBook
On this page
  • To Do / Selected For Development
  • In Progress
  • Ready For Acceptance Testing
  • Acceptance Testing In Progress
  • Acceptance Testing Failed
  • Done

Was this helpful?

  1. Agile Development
  2. Card Management

Columns

To Do / Selected For Development

These are priority cards moved from the Backlog and ready for development. The team should follow their own Definition of Ready.

In Progress

These are cards that are ongoing.

Ready For Acceptance Testing

These are cards ready to be tested.

Acceptance Testing In Progress

In this column, SQA will write an automation test and manually test the story card.

Shifting the Automated E2E Test to the left is recommended for every project.

Things the team should do before shifting-left testing:

  1. Make sure that all acceptance criteria are clear.

  2. SQA should collaborate what are the required backdoor variables to bypass real transactions.

  3. Developers should help QA with any inquiries from them during QA In Progress.

These are the things that you do not consider shift-left testing:

  1. No full-time Software QA Engineer (SQA).

  2. The story card is not automated test-worthy.

Acceptance Testing Failed

These are the cards that failed on testing.

Done

These are cards that passed the testing phase. These are cards that got tagged using Git. The team should follow their own Definition of Done.

PreviousDefectNextCard organization

Last updated 3 years ago

Was this helpful?