If you select Scrum Board, you have the option of using an existing Backlog, or starting with a new Backlog.
A Backlog is a collection of user stories, organized as cards in a column.
These stories typically represent new product functions to be built, or business goals to be attained, but they could also represent bugs to be fixed or other work that needs to be done by a team.
An Agile team works in Sprints: project iterations of some fixed duration, typically 1-4 weeks long, and in each Sprint, some of the work in the Backlog is done. (In Agile terms, some of the stories are "delivered" in each Sprint.)
In Kerika, every user has an individual account, and each account can have as many Backlogs as you like — which means that a single Account can support several different projects at the same time: one Backlog could be for software development, another could be for Marketing initiatives, a third could be for Sales activities.
Let's start with a simple setup: Scrum Board A is set up to use a Backlog which contains several cards ("Card 1", "Card 2"... "Card 6")
The team working on Board A decides to pull Card 1 and Card 2 from the Backlog onto their Scrum Board: these can simply be dragged over from the Backlog column, which appears automatically inside Board A — and every other Scrum Board that connects to the same Backlog — and these cards can be dropped into one of the columns for Board A.
Board A, itself, could be organized with any number of columns, representing the workflow for the team. Here's an example:
In this example, Sprint 61 and Sprint 62 are two different Scrum Boards, that have the same real-time view of a shared Backlog.
While working in a Sprint, it's common for new user stories to be added to that Scrum Board: existing stories may get broken up into smaller stories, after further analysis, or new stories may be identified that are essential for the successful of the Sprint.
So, Board A could have not just the two cards the team originally pulled from the Backlog — Card 1 and Card 2 — it could also have several other cards that it added to its board during the course of the Sprint (shown here as "Card A3", "Card A4"..."Card A6").
Now, consider what happens in the second Sprint: this new Sprint can be set up as separate Scrum Board that connects to the same Backlog as the first Sprint.
In this Sprint, the team has decided to pull just one card ("Card 3") from the Backlog.
And, as with the first Sprint, it's possible that the team working on Board B also adds more cards to their Scrum Board, representing new user stories that were identified that are necessary for the successful completion of that Sprint. These show up as "Card B1", "Card B2" and "Card B4".
A common scenario with Scrum teams is that cards that get added to a Sprint need to get pushed back into the Backlog: perhaps some user stories were added that can't be completed in the current Sprint, or they are of lower priority and can be dealt with in a future Sprint.
Kerika makes it as easy to move cards back to the Backlog, as it to move them from the Backlog to a Scrum Board.
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 can 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!
Everything in Kerika is real-time: you are never looking at outdated information. As one Scrum Board pulls cards off a shared Backlog, this is instantly conveyed to every other Scrum Board that's using the same Backlog.
In other words: you will never have a problem with two Scrum Boards working on the same card at the same time, even when these Scrum Boards are sharing the same Backlog!