🪃
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
  • Why Kanban?
  • Resources

Was this helpful?

  1. Agile Development

Kanban from the start

PreviousEngineering PlaybookNextDaily Stand-up

Last updated 3 years ago

Was this helpful?

We're using the Kanban framework as a baseline when starting or initializing a project.

Why Kanban?

  1. Start lean and with minimum required processes.

  2. Encourage leadership at all levels

  3. It does not overhaul existing workflows and processes but emphasizes small gradual changes.

  4. It is easy to adapt depending on the team's proposed changes. It is possible to adopt a hybrid with scrum, or gradually to SAFe, make a strict path using DAD, and etc.

Resources

https://hygger.io/blog/how-users-see-kanban