Tell me more ×
Project Management Stack Exchange is a question and answer site for project managers. It's 100% free, no registration required.

I'm exploring Trello as a Kanban tool, and am hung up on how to track story points with it. This isn't something that Trello natively supports, so I've been re-purposing labels to carry this information.

This has a couple of significant short-comings. For example:

  • There's currently a limit of six labels, so I can't carry the entire Planning Poker sequence.
  • It makes it hard to color-code blocked or pull-ready tasks unless I leave red and green unused, further limiting my available labels.
  • There's no obvious way to automatically calculate story points or WIP without digging into the API or writing an external utility.

How can I effectively track story points with Trello without creating side-effects as outlined above?

share|improve this question
1  
This question is better suited to a support site for the software product. Reopened based on discussion on meta meta.pm.stackexchange.com/questions/393/… – Mark Phillips Jul 16 '12 at 22:16
@MarkPhillips This seems on-topic based on the tag wiki at pm.stackexchange.com/tags/pm-software/info, which says: "Questions with this tag should be about a real, actual problem faced by a project manager using a specific software program used in project management." I think the question should be re-opened. – CodeGnome Jul 16 '12 at 23:28

1 Answer

The way we solved this problem was to use Scrum for Trello Chrome extension. Yes, that means that anyone viewing Trello as a Kanban tool needs to do so via Chrome, but in our group that wasn't a problem -- your mileage may vary.

At the card level, the extension adds the ability to assign point value to the card:

Scrum for Trello - card view

At the list level, the extension shows the points for each card, and also calculates points for the list (for us, list == sprint):

Scrum for Trello - list view

This allows us to continue to use labels as labels, and eliminates the need to program against the API just to visualize points.

We only use points to guide us during planning (we plan up to a certain number), and as a check at the end of the sprint (how many did we accomplish). We do not spend any more time than that (e.g. simple notation) calculating velocity or doing anything more with the numbers. Therefore, the simple use of the extension to display the numbers, without the ability to export or report on these numbers, works perfectly for us. Again, depending on your group and your needs, your mileage may vary.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.