Kanban
At OKP4, we are using Kanban as our agile methodology because it offers a visual representation of our work progress, helps us in prioritizing tasks and allows us to continuously deliver new features, which leads to increased efficiency and faster time-to-market.
Kanban fundamentals
✭ Pull-based system
✭ Visualizing the workflow
✭ Limiting Work in Progress
✭ Measuring and managing the flow
✭ Continuous learning and feedback
Our Kanban boards
Product board 📝
| BACKLOG | TO DO | SPEC IN PROGRESS | MOCKUP IN PROGRESS | MOCKUP TESTING | VALIDATED | CLOSED |
|---|---|---|---|---|---|---|
| tasks that have been proposed but are not yet prioritised | tasks that are prioritised but not yet started | task specs that are currently being worked on | task mockups that are currently being worked on | task mockups that are done and being tested | tasks that are validated and waiting for development | tasks that are completed and closed |
Dev board 💻
| BACKLOG | TO DO | IN PROGRESS | IN REVIEW | TO TEST | VALIDATED | BLOCKED | EPICS | CLOSED |
|---|---|---|---|---|---|---|---|---|
| tasks that have been proposed but are not yet prioritised | tasks that are prioritised but not yet started | tasks that are currently being worked on | tasks that are currently in code review | tasks that are finished and ready for testing | tasks that are validated and waiting for development | tasks that are blocked and cannot be worked on for some reason | tasks that represent a major theme, broken down into smaller issues | tasks that are completed and closed |
Management board 🧑💼
| BACKLOG | TO DO | IN PROGRESS | REVIEW | CLOSED |
|---|---|---|---|---|
| tasks that have been proposed but are not yet prioritised | tasks that are prioritised but not yet started | tasks that are currently being worked on | tasks that are finished and ready for review | tasks that are completed and closed |
IT & DevOps board ⚙️
| BACKLOG | TO DO | IN PROGRESS | TESTING | BLOCKED | CLOSED |
|---|---|---|---|---|---|
| tasks that have been proposed but are not yet prioritised | tasks that are prioritised but not yet started | tasks that are currently being worked on | tasks that are currently being tested | tasks that are blocked and cannot be worked on for some reason | tasks that are completed and closed |
Definition of Ready ✅
There is a certain criteria a user story must pass in order to be ready for development. A user story that is ready to be developed at OKP4 must have:
- title, description, and value statement
- acceptance criteria (scenarios)
- mockups (for all devices and themes)
- labels added
- US presented to DEV team (refinement meeting)
- attachment to an epic
- estimation (planning poker meeting)
- external dependencies if applicable