Thanks! I wanted to avoid optimizing. When I started working on it (before Trello came out) I wanted something really general purpose with no forced workflow, etc. I could customize it but that's not what I really wanted to build so I've resisted.
It uses backbone.js models/views, Jquery UI, and some Twitter Bootstrap JS.
I'm trying to remember why I didn't like Trello, and IIRC I didn't like how it looked/worked after you had 10+ cards per column. Perhaps optimize for people that have many cards? I don't know if having many cards happen in the Scrum process though...
It uses backbone.js models/views, Jquery UI, and some Twitter Bootstrap JS.