3 ms·
We've been using Clubhouse for about two weeks, having transitioned from Asana, which we found lacking in many respects. (Before then, we used Trello, which we
by atombender 11y ago
We've been using Clubhouse for about two weeks, having transitioned from Asana, which we found lacking in many respects. (Before then, we used Trello, which we also found to be not fit our workflow very well.)
So far, Clubhouse has been working really well. They are emulating the Slack aesthetic pretty hard, and that's not a bad thing. It's pretty responsive and well designed. I find the story card view friendlier than Trello's.
Clubhouse is really a clone of PivotTracker, and I don't mean that as a criticism. They even use the same terminology (points, stories, epics, workflow) and categories (bug, chore, feature). However, there's less of a focus on iterations, and the UI is decidely smoother from my perspective.
There are some features I'd like. For example, I would like their Slack integration to PM me personally about changes; Clubhouse can currently post updates to a Slack channel, but monitoring all the story activity is just not an option when you're on a team working on many different things.
There are also some rough edges in the UI. You can save your story view as a workspace, but if you alter anything (e.g. hide an epic), you have to save it under a new name, then remove the old workspace. I expect stuff like this to improve over time.
- Joe8Bit 11y agoAFAIK 'points, stories, epics, workflow' are generic 'agile' terms rather than specific to one particular tool.
- lobster_johnson 11y agoThey are, but if you look at Clubhouse's UI there are exact analogues to almost all of Pivotal's UI. Didn't Pivotal invent some of these terms, too? I could be wrong.
- kschrader 11y agoWe tried to use rather generic agile terms. Here's a reference to most of the same concepts on the Jira site, for instance: https://www.atlassian.com/agile/delivery-vehicles/ https://www.atlassian.com/agile/delivery-vehicles/ (I've worked with Pivotal on projects in the past and I worked at Thoughtworks for a while, so we're definitely using language that should be familiar to users that are familiar with the flavor of "agile" promoted by those companies.)