Graham Ashton


Founder of @agileplanner and author of @nestacms. Collector of bikes. I tweet several times a day on web development (primarily Ruby and JavaScript).

Hi Marc.

I'll explain how iterations work first.

At the start of an iteration you choose the cards that you want to work on, scheduling them by dragging them out of your backlog into the current iteration.

The cards you choose will appear on the Kanban board.

Once the iteration is over, Planner will prompt you to make sure that all your cards are in the correct columns, before letting you archive the ones that you've finished (i.e. the ones in the right-most column on the Kanban board).

You get to choose whether cards that you didn't complete stay on the Kanban board for the next iteration, or get put back in the backlog (some teams prefer the latter approach).

In other words, Planner automates the bit that requires discipline in Trello.

Planner also keeps all your cards that were completed during an iteration together. For teams that like to use estimates this means Planner can track your velocity for you (there's a graph).

The other thing that's significantly different to Trello is the way conversations are handled.

Once a Trello card has accumulated a lot of comments it can take a while reading through them all to find the answers you need.

Planner let's you start a separate discussion for each topic, so you can jump straight the information you need. Planner's discussions are a little like email threads, but they're also accessible from the card.

Let me know if you've got any more questions!


P.S. We can import from Trello, so you'll be able to try it out easily. :-)
@jankeesvw Hi Jankees, thanks!

Yes, you can use estimates.

I'm focusing on a simple and flexible as interface, so Planner doesn't mind whether you use ideal days, points, or T-shirt sizes (S, M, L).

If you use numbers, Planner will add them up.