Kanban and sprint boards serve very different purposes which are important to understand so that you create a board that is a fit for your needs.



Similarities?


Both Sprint and Kanban boards:

  • are used to visualise work as it progresses through the workflow, keeping all team members in the loop on work in progress and what’s to come. 
  • encourage work to be broken down into manageable tasks - placing a high value on continuous improvement and optimising work and the process. 
  • Use POINTS and IMPACT for better prioritisation, management, and planning of the work to be done.


'Points' of effort

The complexity the delivery team feels is associated with the task. The higher the score, the more complex the task.



'Impact' for business

The amount of business value stakeholders attribute to the task. The higher the score, the more valuable to the business.






Differences?


Sprint Boards

Kanban Boards


Sprint boards limit the amount of time allowed to accomplish a particular amount of work by means of time-boxed periods called sprints

Sprint boards place a heavy emphasis on schedule. Each sprint has a start date and an end date. Before a sprint, each task in the Backlog is allocated the appropriate points of effort and impact. Tasks are then prioritised (between the delivery team and their stakeholders) and then added to the board at the beginning of each sprint. Any tasks added to the sprint should be completed by the end of the sprint for the sprint to be considered successful.


The on-going tracking of ad-hoc activity, through a defined process, to completion.

Kanban boards are not time-boxed. A Kanban board will continue to flow for as long as needed, with new tasks being added as required, and completed tasks being archived as they are completed.








So which one should you choose?


It all depends on your team and what you are trying to achieve:

  • If your team needs to track on-going, ad-hoc work that is subject to change, Kanban is probably a better option. 
  • If your team is structured and by the book, delivering packaged outputs towards an end goal then Scrum/Sprint works well. 

The scope and depth of the execution required also helps determine which is the better option. Kanban works best with smaller pieces of work and team task tracking, while Scrum/Sprint helps deliver larger pieces of work on time.


Our recommendation is to become familiar with both options and then experiment, analyzing your needs and capabilities for the type of board that works best for your team.