🪃
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
  • Naming title guidelines
  • Writing a description guidelines

Was this helpful?

  1. Agile Development
  2. Card Management

Sub-task

PreviousHotfixNextDefect

Last updated 3 years ago

Was this helpful?

This is to further break down Story Cards into a fine-grained unit of work. This also serves as a guide for developers.

Naming title guidelines

Make the title imperative.

Example(s)

Add an GraphQL endpoint to update a pending item

Writing a description guidelines

It should define the purpose and the additional details for this task.

Example(s)

The item can be updated when the field, status, is PENDING.

The update would return an error message if the status is not PENDING.

1