Trello as a task board for Scrum Team – Part 2

And so, the Scrum team started using Trello as their information radiator. One major point of discontent was that it was difficult to see the tasks associated with the story.

One major point of discontent was that it was difficult to see the tasks associated with the story. Tasks were captured as checklist items on the story card, but it is not easily viewable on the task board. One need to open up the card just to see the tasks. While this can be slightly mitigated through the use of “Next Step for Trello” extension, we still faced with the challenge of identifying which team member is working on which task and the task status.

Till Trello starts to introduce horizontal swimlanes, it will not be a good option for a team needing to clearly see the story and tasks association and status.

My first attempt in using Trello as a taskboard for Scrum Team

Trello is free to use and is easy to setup. On top of its existing functionalities, I had included a few extension that I found useful for the taskboard.

  1. Scrum for Trello (Available for Chrome, Safari and Mozilla) –
  2. Card Color Titles for Trello (Available for Chrome, Safari and Mozilla)  –
  3. Ultimello (Chrome only) –
  4. Next Step for Trello (Chrome only)  –

The above extensions are all available on Chrome, some on Safari and Mozilla. So we might have to use Chrome browser in order to enjoy the extensions.


Scrum for Trello will allows us to capture and display the estimated story points for each card and also the total story points on the list.

Scrum for Trello

Card Color Titles for Trello will allows us to see the label text on the card when it’s on the list.

Card Color Titles for Trello

Ultimello has a tons load of features. For now we are using it to help show the number of cards on the list.


Next Step for Trello allows us to view the checklist in the card when it is on the list.

Next Step for Trello

Starting a new Scrum Team


  1. Have a team name. An identity for the team goes a long way.
  2. Identify all Scrum team members, role, skillsets, contact information and working hours. Especially useful for distributed team
  3. Conference number and participant code (usually for distributed team)
  4. Taskboard URL (if not using a physical board)
  5. Source code URL and access
  6. Working Agreements (at least 3 not more than 7)
  7. Team Values (at least 3 not more than 7)

Product Owner

  1. Availability of Product owner. Identify slot of time where PO is or not available.
  2. Will the PO attend the daily standup meeting?
  3. What should the team do if the PO is not available for sprint planning, review, question or extend period of time (vacation, sick leave etc)


  1. Sprint length
  2. Sprint start date
  3. Sprint Planning (day/time/location)
  4. Daily standup meeting (time/location)
  5. Sprint review (day/time/location)
  6. List of important stakeholder to be invited for sprint review
  7. Sprint retrospective (day/time/location)
  8. Backlog grooming/refinement (day/time/location)
  9. Identify important milestones for the project


  1. Definition of Done
  2. Definition of Ready
  3. Story point baseline
  4. Estimation scale (Fibonacci or power of 2 or etc)

The above activities can be considered as part of sprint zero. It should not be taking more than 2 days if the relevant parties are available. Once the above activities are completed, it is time for the Scrum Master and the Product Owner to prepare the prioritized backlog and have a product grooming session with the team before the actual sprint begin.


  • Sprint zero should also cover the technical setup of the necessary tools and environment
  • You might also want to include a half day Scrum training for the team if the team is new to Scrum