Switching project management tools may seem like a daunting task. Your team has to adjust to new terminology, workflows, and routines. We get it, and we're here to help!
The goal of this post is to outline the most important concepts to grasp early on to help ease the transition. We'll run through the key differences and similarities between Clubhouse and Jira so your team can focus on your work, not the tool.
Stories in Clubhouse are the equivalent of Issues in Jira; both are the main work entity within their respective systems. At their core, they function the same (assigned to an Owner, moved through statuses to completion, etc.), but differ in name and categorization.
In Jira, "Story" is one of the many available Issue Types, but in Clubhouse, the term "Story" represents the general-purpose work unit. In Clubhouse, we've simplified Story Types to represent common software team use cases: Feature, Bugs, and Chores. In addition, Clubhouse Stories have built-in Task-level functionality so you can split your work into smaller pieces.
Workflows in both Jira and Clubhouse define a series of States a unit of work (e.g. Clubhouse Story) can move through to completion. However, in Clubhouse, Workflows are naturally linear and open; no need to design a complex set of transition rules between States.
In addition, we've built a simple Workflow editor so you easily create and customize Workflows to support how your various teams work. A Story's Workflow is not dependent on the Story Type (unlike Jira), which makes it easier to standardize Workflows across your Organization. But this doesn't mean Clubhouse Workflows aren't powerful; you can still automate Workflow State changes with your VCS tool to streamline the deployment process.
In Jira, Boards are a distinct entity that require manual mapping of Workflow Statuses to Board columns. In Clubhouse, Workflows States and Kanban board columns are the same. In fact, we do not have a concept of a "board" entity within Clubhouse; the columns on the Stories page are naturally the Workflow States of the selected Workflow.
This is a key feature that allows Clubhouse to become the collaborative hub for your teams work; all teams and views are working from a centralized location. You can quickly toggle the Workflow on the Stories page to reveal another set of Workflow States without having to create a new board.
Clubhouse Spaces are the closest equivalent to Jira Boards. Spaces let you save and share a filtered view of the Stories page with your team. This is a simple way to create a common view of your Stories Kanban view for stand-ups, prioritization meetings, or general development efforts.
In Jira, Projects are the highest-level container; all of your Stories, Workflows, and Epics sit within an overall Project. However, in Clubhouse, Projects are an open-ended entity that categorize Stories within a Workflow.
A Clubhouse Project belongs to a specific Workflow, so the Project that is assigned to the Story determines the Workflow. Projects don’t move through a series of Workflow States; they represent open-ended categories of work. You can think of Clubhouse Projects as a flexible container to help you organize your Stories. To start, we recommend setting up your Projects as functional teams (e.g. Frontend or Backend) or product components (e.g. Web App and API Server).
Both Jira and Clubhouse have the concept of an Epic for a collection of Stories (or Issues) that represents a larger initiative or deliverable. However, Clubhouse Epics are a distinct object within Clubhouse, rather than an Issue Type like Jira, which allows your team to manage work at a higher-level.
From the Epics page, you can quickly view progress of Epics and click-in to view Story-level detail. In addition, Epics can contain Stories from different Workflows and Projects, which makes them a flexible tool for cross-functional collaboration.
In Clubhouse, the level above Epics is called Milestones, which is a "collection of Epics" analogous to Initiatives in Jira. Similar to Epics, Milestones are a distinct object within Clubhouse, rather than an Issue Type. Milestones are often used to represent time, such as a quarterly roadmap.
In Jira, you must configure your Project to either Scrum or Kanban methodology. Within Clubhouse, you do not need to choose nor configure; the tool naturally supports the way your team works.
If you use Scrum or Sprints, you can enable our Iterations feature to manage your work in time-boxed periods. If you prefer a Kanban approach, you can adjust your Workflow States and prioritize Stories from the Stories page. If you want to use both, you can filter on your Iterations from the Stories page. And if you have a different development approach, Clubhouse's elements are flexible enough to adapt to your team's needs.
Any successful product or feature launch involves collaboration across all teams to move from ideation through execution. Clubhouse's intuitive and flexible design will bring all departments into the platform to ensure your team isn't working in a silo.
Here are some ways non-technical teams use Clubhouse:
Clubhouse Write is a knowledge base tool that is currently in private beta. Write allows for free form documentation, ideation, and collaboration in an easy-to-use editor. Now when you're working on an Epic, or Iteration, or Story, all the relevant information is easily accessible and collected right at your fingertips. No more wasting time searching for documentation or asking to be given permission to access a document. Sign up here to request access and receive updates about the private beta.
We are actively working on a Jira importer to help transfer your data from Jira to Clubhouse. If you are interested in testing with our team, please send us a request here. In the meantime, you can use our API to transfer data.
We've covered the essential concepts for a successful transition from Jira. Clubhouse is full of powerful features, workflows, and tips that aren't covered here, so we'll leave you with a few more resources:
Feel free to reach out to our support team or get in touch at email@example.com - we're here to help!