🪃
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
  • Working Agreement
  • General
  • Communication
  • Backlog Management
  • Code Management

Was this helpful?

  1. Agile Development
  2. Team Agreement

Working Agreement

Working Agreement

A working agreement is a document that describes how we work together as a team and what our expectations and principles are.

General

  • We work as one team towards a common goal and clear scope

  • We make sure everyone's voice is heard, listened to

Communication

  • We add all documentation to the project repository

Backlog Management

  • We follow the Definition of Ready when we move it to To Do

  • We make our work visible through work

  • We assign ourselves a task when we are ready to work for it. and move it to In Progress

  • We follow the Definition of Done when closing cards

  • If add a sub-task card, we make sure it matches the acceptance criteria of the user story, to avoid scope creep.

Code Management

  • We follow the git flow's naming of branches

    For example:

    feature/add-add-user-api-endpoint

  • We merge through PRs

  • We treat documentation as code and apply the same standards

PreviousTeam AgreementNextDefinition of Ready

Last updated 3 years ago

Was this helpful?