Shortcut

The perfect tool for software projects using Kanban

Kommentare: Clubhouse helps us manage agile software projects better than ever before. With other tools it feels like we are forcing it to try to accommodate our workflow, but with Clubhouse it feels like it was designed exactly for our use.

Vorteile:

Clubhouse brought us a new set of features and ways to organize stories and tasks that we didn't know we wanted/needed. We have always stuck with tools that were able to help improve our kanban based workflow rather than the simple project board tools like Trello that cater to everyone more than software/product development specifically. There are few tools out there that provide what we are looking for: the ability to organize and label stories with more granularity than a single label (estimates, types, project, priorities, epic, etc), and the ability to have reports like velocity and burndown charts.

Nachteile:

It is a very small thing, but it would be nice if we could adjust the color scheme of both things like labels beyond the default options, as well as adjust the overall interface colors.

Shortcut (previously Clubhouse) has been a great improvement for us.

Kommentare: Overall our experience has been great. Less has been falling through the cracks, and we're able to actively manage & prioritize our development with ease. The application is enjoyed by both the development team & the management team, so everyone is benefitting from our switch to Shortcut.

Vorteile:

1. The app is very easy to configure & set up. 2. The user experience is seamless & functionality is very self-explanatory. 3. There are multiple ways to configure each component, so you can set up the app according to what works best for you & your company. (No "one size fits all" model.) 4. The ability to set up different workflows for different departments has been a huge help for us.

Nachteile:

1. It's a little hard to envision how each of the components should be set up for your organization when you're first getting in there (i.e., projects, workflows, milestones, epics, stories), so we ended up changing the setup as we went along after the initial configuration. This wasn't necessarily a bad thing, as it allowed us to improve the way we currently did things. 2. The biggest issue we have now, after using the app for a while, is that stories do not populate into the Gantt charts, only epics. This means if we have one-off tasks that are added as stories, those do not pull into the report we'd like. For that reason, we have to set up an entire epic just to set up a single story, for reporting purposes. I think it would be great if you had the option to pull the Gantt reports at the epic or story-level.

Shortcut the Jira killer

Kommentare: Easy to get started with. Easy to use. Nice diagrams and overviews.

Vorteile:

It is extremely easy to use. Quick to setup and understand. VERY cost effective! The team behind Shortcut delivers new and exciting functionality often that really makes a difference.

Nachteile:

I have not idea to be honest. There are really no bad parts of Shortcut for what it is doing! Nice integrations and easy to use, not really something you can dislike.

While Clubhouse can do some things well, it is lacking in many areas

Kommentare: My experience with Clubhouse was not great to say the least. While the UI is promising, and the price per user is much lower than others, you get what you pay for. Like too many other project management apps, there is not enough focus on the time being tracked vs a budget for the project you are working on. The project layers overlap in a way that would be good if you were working on individual projects for a larger product, but not if you are working on individual projects geared towards individual clients.

Vorteile:

I think the best part of Clubhouse is the robust API that can allow a dev team to add or complement to the existing platform. Clubhouse seems designed for teams focusing on a product or a small portfolio of similar products or complimentary features. It does not seem designed for a consulting or agency style development shop.

Nachteile:

Clubhouse is lacking in a number of areas that should be expected features in agile project management software. Completion dates are buried, no project budgeting or hourly rates, no invoicing or adding expenses, time tracking, resource management, personal task lists, custom fields, dependencies. It also seemed overwhelming to get set up and running.

Rather lightweight and easy to use once you're used to it

Kommentare: I didn't like shortcut at first because I was used to Jira but it definitely grew on me over the past few years. I still lament the lacking integrations but they are not the most critical at this point. Thanks to the customization you get to have, it definitely presents some learning curves for newcomers. Teams need to set it up and onboard their users effectively for Shortcut to be as useful as it could be.

Vorteile:

Shortcut feels very lightweight and fast compared to some more popular alternatives like Jira. It satisfies our needs for product development tracking (but not discovery) very well. Writing stories, attaching information is easy and they intuitively turn into previews. The reporting function looks very comprehensive and powerful but we don't use it well enough. I also wished that we were using the engineering part better to integrate well with GitHub -- starting to try it out and it seems to work well.

Nachteile:

1. The integrations of shortcut with other commonly used software by product managers are lacking. We use shortcut in conjunction with productboard (for discovery) and notion (for company-wide documentation). The integrations with these two are quite useless to be frank. We cannot push a feature from productboard to shortcut as a feature, only as an epic, and also can't link it to an existing epic? In comparison, the jira integration seems so powerful we wish we were using that sometimes. 2. For people who are not used to using shortcut, it definitely has a learning curve as it could contain a lot of information and customization. 3. Features related to prioritization have been massively improved (just by adding that priority level) but its still painfully manual in the kanban view. Why can't I auto-sort stories by priority levels and then finetune their relative position? When I have 20-30 stories in a column it is almost impossible to drag and drop in an efficient manner. 4. Maybe it's just us not doing a good enough job onboarding our devs, but none of them realized that the most relevant view to them is if they go to "Stories" and then use a "Space" to filter down to the current iteration and team. I was abhorred to learn that they were mostly looking at "everything" for a long long time.

In Betracht gezogene Alternativen: Jira