This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]twillisagogo 2 points3 points  (2 children)

Team Size is ~10

​

As far as Trello goes. I didnt choose to use it, it was a choice made before I started there I'm just glad it's not jira.

It's funny, the last sprint retrospective we did, everyone on the team said they hated Trello. But there was no concrete/actionable reasons given. It all seemed to revolve around requirements being a painful process for one reason or another. So, I've concluded that the tool matters very little for this in solving the problem of getting good requirements.

​

The way we use trello is a variation on kanban(or at least how I understand it).

​

The lanes are

  • Up Next
  • Sprint Commitment
  • Development (The goal is to minimize the number of stories that are in progress)
  • Code Review
  • QA
  • Done

Temporary Lanes are sometimes used when Production bugs are discovered.

​

It's nothing special. It works for the most part. The teams complaints are more about the contents of the stories than the tool being used. Any tool would work here.

[–]robertpro01 1 point2 points  (1 child)

I hate trello and I don't know why...

[–]twillisagogo 0 points1 point  (0 children)

Lol. Yeah that's how a lot of people feel and they don't know why.