Introducing js scrumboard

js scrumboard¬†allows you to make a task list and print it out on a sheet of paper. This post is it’s first introduction. It’s open sourced, you can find it on GitHub. The name makes it clear it’s written in JavaScript I guess ;-). Anyway, lets start with a screenshot!

Screenshot of js scrumboard
Screenshot of js scrumboard

A scrum board is usually used in agile methods like Scrum and Kanban, to visualize the task list taken on in the current sprint.

Why did I create js scrumboard?

  • Because I was creating images like this by hand.
  • With js scrumboard you start a sprint with a clean, organized and readable board. You’re not dependant on programmer handwriting from the start ;-).
  • It will have empty spots for when the team realizes new tasks need to be done before the user story will be complete.
  • Press print in your browser; it will make the best use of a sheet of A4 paper using a print style sheet.

How does js scrumboard fit into our work flow?

Before taking on a task, we make an estimation using planning poker. The list of tasks we get from the planning poker goes into a excel sheet. Since this list is already available digitally I make the start of the scrum board from there. If you don’t have it in a digital form yet, you’re probably very quick in typing.

If you use a whiteboard as your scrum board, there is a big chance that it’s magnetic. So you can make it digitally in js scrumboard, print it and put it on the board. If you don’t have magnetic possibilities some tape might do :).

Because this is just about making a list transition from digital to the analogue world, it’s not bad that this list is not stored anywhere. From the moment I press print the paper version is the leading version. Should a lot of changes occur, it might be back to the drawing board.

At the daily scrum we use it with a pen to write the names of the persons taking responsibility of the task. A name means “in progress” and a check mark or a curl means “done”. You could also use markers which would give an even better indication.

The scrum board should be in a central location, where you also perform your scrum. In our case it’s in the coffee corner, so every time someone gets a cup of coffee they see the board.

Why not use a purely digital solution?

Doing it purely electronic does not make sense (to me). A scrum board has the most use during the daily stand-up. If you use a digital board, you have to update the board after every stand-up. This means that you’ll forget to add tasks, forget to mark tasks as done, or the board will be out of date in some other way. Even if you do it correctly, it requires a lot of attention. For me scrum is not about administration.

So if you use some digital way, that’s fine. We’ll just respectfully agree to disagree.

Anyway, if you’re interested, make a clone. I’d love to get some feedback on this from other people. I’ll put a demo online somewhere next week.

One thought on “Introducing js scrumboard

  1. I don’t. It would be an overkill in my precojt as I don’t have control over the entire process. All I control is coding. We still want to reduce WIP (no unfinished code) and we still want to have small tasks but we would do Kanban we would have trivial 3-column board (to-do, coding, coding complete).

Leave a Reply

Your email address will not be published. Required fields are marked *