A Kanban-Based Project Management System
Saying Kanbanara has one Kanban board is a little simplistic as in fact the cards that get displayed in the columns can be in one of 57 different formats depending on which aspect of a card you wish to zero in on. The available card formats are Tabbed, Absenteeism, Activity, AffectsVersion, Attachments, Attributes, Avatar, Blockages, Bypass Reviews, Capitals, Children, Class Of Service, Comments, Co-Owner, Co-Reviewer, Cost, Creator, CRM Cases, Customer, Days In State, Deadline, Deferrals, Difficulty, Emotions, Escalation, External Reference, FixVersion, Focus, Hashtags, Identifier, Iteration, Last Changed, Last Touched, New, Owner Unassigned, Questions, Reassignments, Recidivism, Recurring, Release, Reopened, Resolution, Reviewer, Rules, Scope Creep, Search, Severity, Similars, Status, Subteam, Test Cases, Time, Today, Velocity, Votes, Yesterday and Internals.
A card placed on the kanban board can be of any one of nine types - epic, feature, story, enhancement, defect, task, test, bug or untracked. Such cards can be chained together with a simple parent-child relationship. Although a parent can have many children, a child can have only one parent.
Where a card is missing an attribute so as to fail to display any useful information on a particular kanban board format, the card will still appear but as a placeholder, thereby reminding the team member to not forget about such a card!
To cope with its use on small screens or at standup, the font size of each card on the kanban board can be changed from minute through normal to huge.
In addition to the kanban board itself, Kanbanara has also been developed around a global filter bar that allows you to select what cards actually get displayed on your kanban board, be they for a particular project, team member, release, iteration or card type, to mention just a subset of the available options. Should you see a number above a particular filter setting, this tells you how many cards are being filtered out as a result of this setting.
Even though you have the full width of the screen at your disposal, the filter bar additionally allows you to select a range of states to be displayed, allowing you, for example, to hide Backlog and Closed as required, thus giving more room to those columns containing cards you are actually interested in.
Should a card be owned by two owners or under review by two reviewers, Kanbanara supports a staggered state where one of the owners or reviewers has moved the card forward in the workflow and is now waiting for the other to follow suit - Such cards will appear in a special waiting section within a kanban board column.
Kanbanara is SAAS-ready in supporting fully isolated projects. An individual user can be a team member in any number of projects and they will only ever be able to see those projects which they created or to which they have been invited.
In addition to the Kanban board itself (including projections), your cards can be visualised in a number of ways such as list view, standup, backlog sorter, timeline, activity stream, diary, time sheet, wallboard, release kickoff and retrospective.
Next action or deadline dates can be individually assigned to a card. The Today kanban board is particularly useful in isolating those cards requiring your attention today (or indeed yesterday). The Tomorrow kanban board is equally useful in highlighting those cards requiring attention tomorrow and during the next few days. Such cards can also be displayed per day on the Diary page.
Drag and drop is fully implemented on both the kanban board and the backlog sorter, allowing you to not only drag a card from one state to another, but also changing its priority, and in the case of the backlog sorter, a card's severity also, as required.
Kanbanara features an extensive search facility that not only allows you to search within a particular card attribute but will also automatically ignore certain filter bar settings to maximise the chances of finding a match. There is even a search-specific kanban board that allows highlighting of the current search phrase, should a match be found, on any card displayed.
Each card can be assigned up to two owners and up to two reviewers, thereby assisting with either pair programming or pseudo team members such as the current incumbent of the service support liason role.
As all cards will eventually end up in the closed state one way or another, unless of course deleted, the number of cards displayed can be restricted to those cards closed in the last five years right down to those closed within the last hour.
The filter bar makes it easy to switch between releases and/or iterations, be it the previous, current or next one.
One card per project can be assigned expedite status, whereupon it will appear in its own expedite swimlane at the very top of your kanban board. Its progress across the board will also be assisted by avoiding going into any buffer columns!
The settings for a given project can be restricted by allocating one of four roles - project manager, deputy project manager, team member or guest - to a given team member.
Global Work-In-Progress limits can be assigned to a project, easily overridden by personal ones (if allowed by the project) should a user wish. Should your Work-In-Progress limit for a particular state be reached, the system may automatically hold a card in a buffer state until spare capacity allows it to be moved forward. Your personal Work-In-Progress limits can be easily amended via the buttons at the top of each kanban board state column, either being set to a specific value or to unlimited. Should a state's Work-In-Progress limit be reached, a message to that effect will be shown between the cards at the appropriate point.
Kanbanara supports both priority and severity, each to four levels, thus giving one of sixteen levels of urgency and importance to an individual card ranging from critical-critical, through high and medium, down to low-low.
The most important cards in any state, those with critical or high priority, are automatically shown towards the top of the kanban board. Within each block grouping cards together of the same priority, such cards are additionally sorted by severity with the critical and high ones again towards the top.
When assigning a reviewer to a card, the reviewer's names are placed in order of least busy to most busy, with a card count after their name, thereby allowing the least busy team member to be more likely chosen. When a card reaches the QA/Testing state, the owner and reviewer effectively switch roles, with the reviewer requested to work on the card and the owner a passive observer. As a reviewer, you can see what work is heading your way as such cards appear as ghost cards - greyed out in the states preceding QA/Testing.
Any card can be viewed in JSON format, not to mention a project itself, your session or your personal filter settings.
Any card on your kanban board can be hidden for up to seven days into the future. Such cards will then no longer appear on today's kanban board. However, you can project your kanban board upto seven days into the future, whereupon any hidden cards normally visible by that date will reappear.
With regard to metrics, Kanbanara possesses quite a few such charts - Abandoned, Bugs and Defects, Burndown Chart, Completed, Cumulative Flow Diagram, Division of Labour, Emotions, Recidivism Rate, Tags and Throughput.
The Standup page features a cut down version of the kanban board and allows the person in charge to either step through each team member or each significant card in turn. Each card selected is then displayed towards the bottom of the screen, in both kanban board and list view formats, along with its children if any.
Should you wish to use Kanbanara as your personal kanban tool, setting a card's bypassreview attribute allows a card to bypass the reviewer-centric columns (if any).
A card can be blocked by a team member explicitly setting it as such. To such a block can be additionally added a date upon which the card will be automatically unblocked. A card can also be automatically blocked by its children if the parent and children get out of step as regards their states.
Should you decide not to work on a particular card for a short while, it can be deferred at any point in your workflow. It will then appear in the Deferred section towards the bottom of the column it is currently in. Its state will be unaffected.
Should a team member get absolutely stuck with a particular card, a stuck setting can be enabled by entering text describing how they are stuck and what assistance they require, whereupon such a card will appear on everyone else's kanban board in the same project thus allowing help from a colleague in the shortest possible time.