Very cool!
I assume you've tried Pivotal Tracker at some point too? I'd be interested to know what you like/dislike about your new workflow compared to Pivotal.
I assume you've tried Pivotal Tracker at some point too? I'd be interested to know what you like/dislike about your new workflow compared to Pivotal.
However my main gripe with Pivotal was always two things: 1) Strict adherence to a Scrum methodology (forcing me to use a certain set of columns, etc) and 2) The UI. It frankly drove me nuts. The small text fields, small text areas and lack of wiki-style formatting. Anything longer than a few words was impossible to grok.
We flirted with trying it out about the time we adopted Trello but enough people had bad past experiences, like mine, that we never gave it a try.
Thanks for replying!
In addition, how do you track velocity?
From the description it doesn't look like they're running in sprints, but deploying as stories get completed, so cycle time would be the thing they would track. No idea if Trello can do this out of the box. They also explicitly said that they're not doing project estimates - so they wouldn't need to track velocity in any case.
If it were me I might be interested in visualising the flow somewhere - more of a tool to help spot problems as to make estimates any more accurate - but I'm a fan of just doing that with a whiteboard as part of running the project.