Break down a work into subtasks

The great agile team prepare how to implement business requirements. The agreements on an approach are build in the sprint planning meeting when business requirements are broken down into multiple tasks, i.e.:

  1. analyze,
  2. add a new database table
  3. add CRUD stored procedures,
  4. a new form,
  5. validations,
  6. test A,
  7. test B,
  8. acceptance

The tasks are implemented later during the sprint and typically are assigned to team members. The types of tasks are agreed within the team as part of the Definition of Done. Very often the team even agree on colors of task cards so they can easily recognize the type of work that needs to be done.

Kanban board

Some agile teams use just business requirements and put them into some state (to analyze, to develop, to test, to accept), however, we found out, that if your team is not mature enough, this approach doesn’t increase collaboration and communication inside the team, especially planning part. During the sprint, such a team very often realize many aha moments because of missing communication during the planning meeting.

How ScrumDesk supports tasks?

Kanban board in ScrumDesk has four columns very similar to the picture of the physical board above:

  1. the first column contains backlog items (user stories, defects, etc.),
  2. To-Do column contains tasks that need to be done,
  3. In progress all tasks which team members work on,
  4. and finally Done column holds completed tasks.

Start - kanban board

Every task card can have different color either set manually or predefined by type of task. ScrumDesk kanban board is therefore very similar to physical kanban board.

< Plan enough to accomplish. Velocity.Content | Task types and Definition of Done >