Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Scrum Board Setup Tips and Tricks

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

I’d like to share with you some tips and tricks for setting up a scrum board I usually share with my clients. The bottom line is that too many tools have too many features that support old ways of thinking. Let’s look at the various items one by one.

Subtasks

Like the human tailbone, subtasks were once useful but are now mainly a source of pain. When we worked in Waterfall we measured progress with completed subtasks, but in agile when stories are short, subtasks are a burden.

A burden for developers who need to mess with subtasks using the ALM tool.

This a burden for managers who measure progress using a burndown chart that usually relies on subtasks estimation. That’s a burden because burndown charts may time tell an incorrect story (all work done but nothing is working) – progress should be measured by “done” stories, usually a burnup chart.

Using subtasks should be a choice given to developers. If you find it useful then use it. I prefer just discussing the work to be done with the other people working with me on a story. If needed we can write it down on a whiteboard, but usually, there is no need to write it down as the story is so short. We just do the job.

Showing subtasks on a scrum board takes the focus from stories getting done to subtasks. It makes the scrum board too clattered and worse of all it lets people focus on their specific job and not on the story getting done. Bad subtasks! Bad!

Swimlanes 

Another evil thing is swimlanes. Second only to subtasks.

People usually need swimlanes because there is too much information on the board. That’s indeed a problem. Many times it will be … subtasks! If it isn’t subtasks it may be either the stories are too small or the team is too big. Or maybe something else.

The idea is we need to see why are there too many items on the board and handle that problem.

The big problem with swimlanes is that it distracts you. When you have swimlanes it is difficult to see what is now in progress. This is because usually there will be items in the “to do” column which will make the swimlane too wide to see all the items in one column.

Your focus is on the things that are now in progress and that’s what you need to see.

Many times there is a swim lane per team member. This will hint that we are trying to make sure people are utilized. Like the manifesto would say, it is important to make sure people are utilized but it is more important to get stories done.

Sometimes team members ask for a swimlane per developer. This tells us that people really care only about what they need to do and not about the team. This brings us to the next item:

Story Assignee

Almost all tools allow one person to be assigned to a story. (Leankit allows many). If you want to assign more people you can use subtasks. However, we already discussed subtasks and the conclusion was quite clear.

We will usually need to assign more than one person. In many places, at least one developer and one QA will be assigned. More than that, we will be happy if people can swarm on stories – having several people working on one story is fun and contributes to teamwork and thus very effective.

So, what do we do?

Many tools allow the addition of custom fields. For instance, Jira. I usually recommend clients working with Jira add a custom field called “assigned team members”. The field type should be multi-select. You will need to manually add the list of all team members. Once you do that you ask the tool to present the information on the card on the board and suddenly – voila! You have a strong scrum board where you see the people involved in every story. That’s great.

Last but not least – Columns

Most tools start with the standard “To Do – Doing – Done” columns + a backlog. (read here about the critical difference between backlog and to-do). That’s great! Why touch it? Please don’t.

Many teams will add a “Test” column. And a “pull request” column. And there are more.

The problem with these additional columns is that they are good excuses for things getting stuck. If there is a “dev” column and a “Test” column it means it is really all right to finish dev (I’m done!) and QA can be done later. Reminds you of subtasks? correct, it is similar.

If the sprint is only two weeks long and stories are short, there should be no reason for these additional columns. Just get done with the story – and please no stories! Remember we already have the names of all involved people on the card – just get it done with.

Conclusion

A scrum board should be very simple. There is a list of stories to do. Some are in progress, some are already done. We know who is working on what. That’s it. Don’t let fancy features distract you.

You may be interested in one of our Agile Up! workshops where we help you use popular Agile ALM tools such as Jira and TFS more effectively.

Subscribe for Email Updates:

Categories:

Tags:

Built-In Quality
Agile Games
Video
Agility
Agile Games and Exercises
IT Operations
Webinar
Software Development Estimation
Sprint Retrospectives
Test Driven Development
ALM Tools
Jira admin
Introduction to Test Driven Development
Accelerate Value Delivery At Scale
Agile Community
Scaled Agile Framework
Lean Budgeting
Agile Israel
Self-organization
Manage Budget Creation
Achieve Business Agility
ART Success
Agile Israel Events
Agile Contracts Best Practices
Nexus vs SAFe
Presentation
SPC
Elastic Leadership
Code
Scrum and XP
Release Train Engineer
Managing Risk on Agile Projects
ARTs
Reading List
The Kanban Method
Change Management
agileisrael
Agile Release Planning
Spotify
Artificial Intelligence
Kanban 101
Continuous Deployment
LeSS
Lean and Agile Principles and Practices
Nexus and SAFe
QA
SAFe DevOps
Scrum.org
Kanban Basics
Limiting Work in Progress
Legacy Enterprise
User stories
Software Development
speed @ scale
Sprint Iteration
Scrum Master Role
Applying Agile Methodology
Agile for Embedded Systems
Coaching Agile Teams
Professional Scrum with Kanban
Agile Product Ownership
Program Increment
Atlaassian
Continuous Delivery
ATDD vs. BDD
Nexus and Kanban
Sprint Planning
Certified SAFe
Lean Agile Basics
Professional Scrum Master
Entrepreneurial Operating System®
Lean Agile Leadership
Pomodoro Technique
Games and Exercises
Kaizen
Jira
Agile Outsourcing
Lean-Agile Budgeting
A Kanban System for Software Engineering
Operational Value Stream
Advanced Roadmaps
Principles of Lean-Agile Leadership
Large Scale Scrum
An Appreciative Retrospective
lean agile change management
Kanban
LPM
Effective Agile Retrospectives
Atlassian
Lean and Agile Techniques
Nexus
Business Agility
Scrum
Lean Agile Organization
predictability
Agile and DevOps Journey
Nexus Integration Team
SAFe
Agile Techniques
Agile Development
ROI
System Archetypes
Value Streams
Risk Management on Agile Projects
GanttBan
Planning
Frameworks
Amdocs
AgileSparks
Rapid RTC
Lean Agile
Perfection Game
Scrum With Kanban
WIP
Lean Software Development
Jira Cloud
RSA
chatgpt
Professional Scrum Product Owner
LAB
Slides
Kanban Kickstart Example
Releases Using Lean
RTE
Agile Exercises
Agile in the Enterprise
Scrum Values
Implementation of Lean and Agile
Introduction to ATDD
Lean Risk Management
SA
Product Management
Scrum Primer
The Agile Coach
Lean Agile Management
Agile Basics
Systems Thinking
Kaizen Workshop
Certification
ScrumMaster Tales
ATDD
Continuous Improvement
Managing Projects
Agile Testing Practices
Quality Assurance
Legacy Code
Agile Project
Tips
Agile Release Management
TDD
Implementing SAFe
Agile India
Jira Plans
Kanban Game
BDD
Agile Marketing
System Integration Environments
Agile Program
Scrum Master
Agile Assembly Architecture
Iterative Incremental Development
Continuous Planning
AI Artificial Intelligence
Agile Product Development
Enterprise DevOps
Agile
What Is Kanban
Daily Scrum
Story Slicing
Product Ownership
Acceptance Test-Driven Development
PI Objectives
Agile Project Management
Hybrid Work
NIT
Agile Delivery
SAFe Release Planning
Process Improvement
Lean-Agile Software Development
Agile Mindset
Risk Management in Kanban
speed at scale
Development Value Streams
Covid19
EOS®
System Team
Scrum Guide
AI
RTE Role
Continuous Integration
Tools
DevOps
Risk-aware Product Development
Engineering Practices
PI Planning
Lean Startup
Agile Risk Management
Portfolio for Jira
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart