We need access to your Trello account
We need access to your Trello account in order to import your boards into Kerika. We will use this access only for importing your boards.
The access will last only 1 hour and we will not be able to make any changes to any of your Trello boards.
If this is OK, please continue to Trello's authorization screen.
{{title}}
Tags
Scrum Boards
The easiest way to build an Agile team
See at a glance what's going on
Scrum Boards can use a shared Backlog of cards.
An agile approach to Agile
This means you can set up your Scrum project the way you want: adopt and adapt Agile to make it work in your organization. (After all, every organization is different, so why would one size fit all?)
Share a Backlog across multiple boards
You can share a common Backlog of user stories across multiple Scrum Boards:
- In a traditional Scrum model, each project iteration ("Sprint") could be set up as a separate Scrum Board: when you start a new Scrum Board, you can decide whether to use an existing Backlog, or start a new one. Each Sprint can pull or push user stories (cards) from the same Backlog.
- Kerika's flexibility lets you work in other ways as well: for example, you could have two teams set up to work in parallel (at the same time), pulling cards from the same Backlog.
Learn more about how to share a Backlog across multiple Scrum Boards.
Switch between Backlogs, if you like
You can have as many Backlogs in your account as you like – because you can have as many boards in your account as you like :-)
And what's really cool about Kerika is that you can pull items from several different Backlogs into the same Scrum Board!
Here's how it's done: just click on the Board Settings button on the top-right of any board and you change the Backlog you are going to use on your Scrum Board.
And, as you can see, you can also easily switch from Scrum to Kanban, and back again, with a single mouse-click!
Cards can contain ideas or specific work items
Inside each card on a Scrum Board you can capture your ideas and specific work items, large or small.
Every card has a unique URL, and you can use the URL as a direct reference from anywhere else (in Kerika or outside). This makes it easy to create dynamic links between cards, canvases and boards.
Cards can contain tasks
You can add tasks to each card, to track all the little things (and big things) that need to get done before that card can be considered "done".
Each task can be assigned to any Team Member — or several Team Members — and each task can be scheduled separately.
Kerika makes sure that dates and assignments are rolled up to the card level, so when you look at a board you can easily see when the card is really due, and everyone working on every task on that card.
Cards can contain chat
You can chat about your ideas or tasks, right on the card itself.
These conversations can get pushed to you as emails, if you like, and they remain forever connected to the card making it easy to retrieve even months after a Scrum iteration (Sprint) has finished.
Check out this video on how chat works in Kerika.
Cards can contain content
You can attach content to every card on a Scrum Board:
- From your laptop: files are shared automatically with everyone on your board team.
- From your Intranet, even a SharePoint site.
- From anywhere on the Web, including videos, blogs, pictures, etc.
It's easy to see the history of a card
Scrum Boards can be private, or shared
Each iteration (Sprint) can be set up as a separate Scrum Board, with it's own team and privacy settings.
Each board can have several Board Admins, and these can then invite others to join as Team Members or Visitors.
Tags makes it easy to manage large boards
Tags and color coding makes it easy to filter your view of large boards: we have seen some large teams work with boards that contain over a thousand cards at a time!
Custom workflows
Every Scrum Board can have its own custom workflow, and if you want to capture your organizations best practices or standard methodologies, that's super-easy with Kerika's Templates feature.
Every user can create a personal library of process templates that can be used to start new boards faster.
Work-In-Progress Limits
WIP Limits are great if you want work to get "pulled" as people become free, rather than work having "pushed" onto people before the people ready.
WIP Limits as "soft": Kerika doesn't stop you from exceeding a column's WIP Limit, but it does provide a clear, visible warning to everyone that a bottleneck is about to form.
Board Admins can easily see bottlenecks appear, and intervene to help manage the upstream flow of work.
Process templates
Templates can include both workflow (the set of columns that make up a Task Board, representing the steps or phases of the project), and cards (the tasks for the project).
Every user can build as many templates as they like, and share them with others or keep them private.
Here, for example, is a template that can be used to use Google's Design Sprints. (It's one of the many templates that Kerika provides: we keep adding to our collection, to make it easier for our users to get work done faster!)
Synch up with your Calendar
Kerika makes it super-easy to have all your Due Dates appear in your Apple, Microsoft, or Google Calendar.
(Here's an example of how you can synch up with your Google Calendar.)