Skip to main content
Enterprise Agile Planning Image

This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.

Last Updated Apr 05, 2008 — Enterprise Agile Planning expert

ScrumWorks with a Physical Taskboard

Enterprise Agile Planning

In a discussion group, someone recently wrote:

From the very beginning, the PO has been very insistent that we use an electronic tool, despite the fact that everyone is co-located. I have resisted from the very beginning, because the Team feels that the physical Task Board and burn-down chart are working great. I believe that the PO is focusing solely on her desire for an electronic tool to enable her to more easily maintain the Product Backlog, to readily identify which user stories have been accomplished and which have yet to be completed, and allow for reporting. We’ve bandied about the idea of using [x product] or [y product], but the Team is reluctant to replace our physical Task Board.

The physical taskboard is clearly the best tool for this team. I use taskboards to teach Scrum, and recommend them for co-located teams.

ScrumWorks Pro has a “print to cards” feature for this situation.

You can keep the Product Backlog in ScrumWorks, then print cards after the Sprint Planning Meeting, so your team can use the taskboard during Sprint execution. During Sprint execution, your team members may realize getting the Product Backlog Items (PBIs) done requires additional tasks they didn’t think of. These can be scribbled on blank cards on the physical taskboard.

At the Sprint Review Meeting, your Product Owner can mark PBIs done in ScrumWorks if they meet the acceptance criteria. We’ll measure your rates of velocity, scope increase, etc. with nice graphs and reports you may need for her business stakeholders.

ScrumWorks was designed for Scrum from the very beginning, by people who get Scrum.

Unlike another tool I recently saw a team struggling with, ScrumWorks does not attempt to measure percent done on a PBI according to task status. In Scrum, a Product Backlog Item is only “done” when it’s proven to meet the acceptance criteria, typically at the Sprint Review Meeting.

Also ScrumWorks does not attempt some of the anti-Scrum nonsense of other tools.

Software Process Mentor (and Scrum Trainer, and ScrumWorks programmer)

Download the PDF version: ScrumWorks with a Physical Taskboard blog

More from the Blog

View more
Jul 27, 2021 Becomes First to Achieve FedRAMP Moderate “In Process” Status for Enterprise Agile Planning Solution

Enterprise Agile Planning, the leading AI-driven DevOps value stream delivery, and ma ...
Read More
Jun 21, 2021

How Agile can be implemented effectively across the organization

Enterprise Agile Planning
Just a few decades ago, a “disruption” was seen as an undesirable thin ...
Read More
May 31, 2021

Agile change management processes are key to delivering software faster

Enterprise Agile Planning
With its emphasis on delivery value faster, agile product management s ...
Read More
May 03, 2021

Bringing the agile planning approach to your whole business

Enterprise Agile Planning
The events of the last 12 months have demonstrated that the only sure ...
Read More
Contact Us