Tag Archives: Workflow

About project and process workflows.

Showing Due Dates in local times

Many of our users work in globally dispersed teams; our own team is spread out between Seattle and India.

With multiple timezones, particularly when they are widely spaced apart, commitments like “I will get this done today” become a little tricky to understand.

If someone in India says “I will get this done today”, is that India time or Seattle time? Well, that depends upon where you are, when you log into Kerika.

Kerika automatically factors in differences in timezones when showing due dates: someone who commits to getting something done “today” in India is actually committing to get it done by 11:30AM Pacific Standard Time, now that the US is in Daylight Savings Mode.

So, the due date is shown in a way that’s relevant to the user’s local time: our Seattle folks see an Indian’s commitment like this

Local time due date
Local time due date

These timezone differences automatically adjust for Daylight Savings Time: there’s nothing you need to do to see when a commitment is actually due.

Except, perhaps, notice that the item is now overdue, as indicated in red in the example above…

Introducing Planning Views: a whole new way to view your Kerika Boards!

We are delighted to introduce Planning Views, a very innovative, very unique way to view your Kerika Task Boards and Scrum Boards!  (Yes, it goes way beyond what simple calendar views, like those you might get from other tools, work :-))

Let’s start with your familiar view of a Kerika Task Board or Scrum Board, which we will start calling the Workflow View from now on:

Example of Workflow View
Example of Workflow View

 

There’s now a simple drop-down that appears on the breadcrumbs, letting you switch to one of the Planning Views:

Selecting a View
Selecting a View

 

Your new viewing choices include:

  • Next 3 days: this will show you everything that’s Due Today, Due Tomorrow, Due the Day After, and beyond
  • Next 3 weeks: everything that’s Due This Week, Due Next Week, Due the Following Week, and beyond.
  • Next 3 Months: everything that’s Due This Month, Due Next Month, Due the Following Month, and beyond.

Planning Views provide a date-oriented view of your Task Boards and Scrum Boards: a Planning View takes your cards and rearranges into time-oriented columns.

Here’s an example of a Next 3 days view:

Example of 3-day View
Example of 3-day View

 

Our Workflow view got neatly (and quickly!) pivoted to arrange all the cards in terms of when they are due:

  • All cards without any due date are shown first, in the Not Scheduled column.
  • Next, any Overdue cards are always shown in a special column by themselves, so they can be easily rescheduled.
  • Beyond this are columns for Today, Tomorrow and the Day After.
  • And finally, there is the And Beyond column, which summarizes all the cards that have due dates beyond the day after tomorrow.

Here’s the same board, but viewed in terms of the Next 3 weeks:

Example of 3-week View
Example of 3-week View

 

Switching between these views is super-fast, and these views update in real-time: if a due date for any card is changed by anyone on your project team, no matter where they are located, this change is instantly reflected in your view.

The Next 3-months view is an even higher-level view of the board:

Example of 3-month View
Example of 3-month View

 

All these views support smart drag-and-drop of cards: if you drag a card across, or up/down a column, the Due Date is automatically changed to reflect the new date.  As you move the card, the new date is shown in orange so you know exactly what will happen next:

Smart drag and drop
Smart drag and drop

 

Since your Planning Views aggregate cards that may be in different columns on your Workflow View, we made it really easy for you to see at a glance where each card is in terms of your workflow:

Where cards are in your Workflow view
Where cards are in your Workflow view

 

Navigating forward and backward in time is also easy, as is jumping to “today’s view” if you have navigated too far into the future:

Navigating the Planning Views
Navigating the Planning Views

 

As you navigate forwards or backwards, the “And Beyond” column magically adjusts to show you just what’s out of your current view!

Planning Views work just as well with Task Boards (if you are using Kanban) and Scrum Boards (if you are using Agile).

Check out Planning Views — it’s exactly the kind of great design and innovation that you have come to expect from Kerika…

Kerika @ Kerika: How we use our own product

We are often asked how the Kerika team itself uses Kerika, and we freely share this through demos we have done in person for potential customers and at various events. For those who we haven’t met in person, here’s a blog post instead..

1. Kerika runs on Kerika.

Pretty much everything we do, from the smallest, tangential effort to our main product development is done using the Kerika software.

(It shouldn’t surprise you to hear that, given that we are a distributed team ourselves — spread out between Seattle and India.)

2. No email, limited phone calls

In fact, we gave up using internal email back in Dec 2013. (Email sucks, and Kerika is the smarter alternative to spam.)

Because our team is spread out over 10,000 miles, we do occasional phone calls, using Skype or Google Hangouts, to discuss product strategy, but we don’t have daily phone calls as a matter of routine.

We have a phone call only when there is something substantial to discuss, never to catch up on routine status. In other words, all our phone conferences are about interesting topics, like “What do you think about this idea…?” or “I met a customer today who brought up this problem…”; never about “Where are you with Task X?”.

Kerika keeps us in perfect sync across these 10,000 miles on all matters of routine status and project management, so our phone calls are all strategic in nature.

3.  Scrum for Product Development

We work with a 2-week Sprint Cycle for the most part, although we have occasionally deviated from this — never with great results, so sticking to the cycle is usually a good idea!

We capture all of our product ideas and feature requests in one large Scrum Board, which we call, simply, Product Planning.

This board organizes our ideas into various buckets, like Valuable for Enterprises and Valuable for Individuals:

Product Planning buckets
Product Planning buckets

You might notice that the Backlog column is relatively small: only 54 items. That’s because not everything in the other buckets is ready to go into the Backlog, either because a feature isn’t well defined enough, or it isn’t considered important enough to deal with in the short-term.

(We have a lot of ideas that sit and gestate for months, even years!)

It’s also worth noting that the Trash contains 62 items: this means we reject as many ideas as we pursue!

4. A Shared Backlog

As ideas for various features get prioritized — and, more importantly, defined clearly enough to be analyzed in detail by our developers — they get moved to the Backlog.

This backlog is shared by all the individual product development Scrum Boards:

Product Planning process
Product Planning process

(And, by the way, the screenshot above is from a Kerika Whiteboard that we use to map out our product planning process.)

Each Sprint is organized as a separate Scrum Board, pulling items from the common Backlog.

As items get done (or not, as the case may be), the Backlog slowly shrinks over time.

But, as ideas for new features gets firmed up on the Product Planning board, this keeps feeding more stuff into the Backlog. So, the net result is that our Backlog has remained the same size for years: about 50-60 items.

We have been doing this for a while now, and are currently wrapping up Sprint 55, with each Sprint taking at least 2 weeks, and several taking 1 month to complete.

Here’s an example of one of our Scrum Boards:

Scrum Board
Scrum Board

5. Kerika’s Smart Notifications

So, if we are a distributed team that doesn’t use email, and not that much phone either, how do we keep up with what’s happening? The answer is: Kerika’s smart notifications help each of us easily keep track of changes taking place across literally hundreds of cards each day.

Here’s an example:

Smart notifications
Smart notifications

At a glance we can tell that this card has

  • Moved
  • Has a new due date
  • Has new attachments
  • Has new (unread) chat messages
  • And, unfortunately, needs rework :-(

These smart notifications replace dumb email with a much more efficient mechanism for keeping everyone on the same page.

6. The Development Process

If we open up one of these cards, we can get a glimpse of the Kerika development process. Let’s start with the chat thread on this card:

Example of new chat
Example of new chat

This chat shows a typical interaction between a junior developer and a technical lead: after writing the code for a particular feature, the developer has passed it on to the tech lead for code review.

The code review itself is attached to the card, as an attachment:

Adding code review to a card
Adding code review to a card

For each feature we develop, our engineers create a small work plan that outlines their design thinking.

This design/work plan is a critical artifact for good software development: it ensures that people can review the work more easily and effectively, and it also provides a reference for the future — if ever a bug is found in this particular feature, we can go back to the work plan to see where the design flaw may have originated.

The code review is typically very short, and attached (in this case) as a Google Doc:

Example of code review
Example of code review

 

7. Card History

Each card in Kerika keeps track of its own history, which makes it easy for a distributed team to keep track of everything that happened. Frequently, a number of changes may have taken place on a single card during a workday, and someone who is 10,000 miles away is also about 13 hours away in terms of timezones, so the history feature is useful for understanding all the changes that took place when you weren’t looking.

History of the work
History of the work

 

So, that’s a typical card, on a typical board. And, in a typical 2-week Sprint Cycle, our development team handles 175-200 cards!

We love Kerika, not just because we have built it, but because it makes our distributed team so very effective!

Linking images on a canvas to external websites

One little-known feature of Kerika’s Whiteboards: if you have an image (picture) on a canvas, you can also add a link to a Website, so that anyone clicking on the picture would be taken straight to that website.

(It’s one of several little-known features that we hope will become well-known, with our recent redesign of the Canvas toolbar; we have built too many really cool features that not enough people are aware of!)

One common use of this feature is to create an external-facing page that includes a logo: you can add the logo’s image to your canvas, and then point that logo to your company’s website.

It’s simple: just select the image, and then click on the “Link to website” button on the Canvas toolbar.

Link image to website
Link image to website

Change Shape: a new feature

We finally got around to adding a feature to the Canvas that we have wanted for a while, but somehow never got around to building: now, with a single click, you can change a shape on a canvas, whether it is in a Whiteboard project or attached to a card on a Task Board or Scrum Board:

Change Shape
Change Shape

Here’s why you might need this: often when you are first creating a process flow diagram, you might use shapes — rectangles, ellipses, diamonds — in an arbitrary or careless way, which is just fine because at that time you are trying to be creative rather than meticulous.

But, as the canvas takes shape and matures, you might want to go back and standard the use of particular shapes (even if you don’t strictly follow the old conventions for drawing flowcharts, which we don’t either).

This new function makes it easy for you to select a bunch of shapes and change them all to a new shape. Previously, you had to create a new shape and put it in place to replace the old shape, which was pretty inconvenient when you had a bunch of nested canvases and a bunch of curved lines connecting all the shapes.

Easy, now.

Free Box accounts don’t support direct downloading of files

When you add files to your Kerika+Box projects, either as attachments to cards on Task Boards or Scrum Boards, or on canvases and Whiteboards, these get stored in your Box account.

If you have a premium (enterprise) version of Box, you can directly download these attachments, instead of having to go through Box’s preview display first: just hover over an attached file, and you will see a “download” button appear:

Directly downloading files from Box
Directly downloading files from Box

This works fine for enterprise users of Box, but if you are using the free version of Box, you will see a Box error page, like this:

Box download error
Box download error

Keeping track of status changes in Card History

We are starting to realize that a card’s status, e.g. “Ready for Review,” “Needs rework,” etc. is pretty important not just in terms of what they show about a card’s current state, but also in terms of its history.

Previously, we weren’t tracking changes to a card’s status as part of the card’s history; without our latest release, that’s now a feature, so if you are wondering who put a card “On Hold”, you can just open the card’s History and Kerika will tell you:

Card status in history
Card status in history

 

Kanban in a Can: Capture, Visualize and Optimize your Everyday Processes

At the Jan 12, 2015 meeting of the Washington State Lean Practitioners Community of Practice meeting, organized by Results Washington at the Department of Labor & Industries in Tumwater, Arun Kumar presented Kanban in a Can: Capture, Visualize and Optimize your Everyday Processes.

Here’s the presentation on Slideshare (although most of it was actually a demo!):

The meeting was attended by dozens of Lean experts representing a huge variety of state agencies in Washington!

Lean Practitioners meeting
Lean Practitioners meeting

Viewing your Kerika canvas like a regular Web page

Did you know that any Kerika canvas, whether on a standalone Whiteboard or attached to a card on a Task Board or Scrum Board, can be viewed as a regular Web page by folks who have been given access to the board?

Kerika automatically creates a version of your canvas that can be viewed without the Kerika application: you can get this version by using the Project Info dialog, or, more simply, by just changing the “m” in the canvas’s URL to a “c”:

Web page version of Canvas
Web page version of Canvas

Every Kerika page has a URL of the form “https://kerika.com/m/…”

The URLs are randomly generated and unique: every card, every canvas, every board has a unique URL.

The first part of the URL is always of the form kerika.com/m/… There’s no special reason for using the “m”; it’s just part of Kerika’s history.

But if you change the “m” to a “c”, like in the example above where “https://kerika.com/m/SRXk” becomes “https://kerika.com/c/SRXk”, then you can view the Web page version of the canvas.

In the Web page version there are no buttons or other indications of the Kerika software: it looks and works just like a regular Web page.

Of course, security is not compromised: you cannot view the Web page version of a canvas if you aren’t permitted to access the Kerika canvas itself.

How long things stay in the Clipboard

When you copy or cut an item on a Kerika board — a set of cards, or may be some things sitting on a Canvas — these objects are placed in a special Clipboard that sits on the Kerika server, not in your browser.

This is important to note for several reasons:

  • Because the Clipboard is on the server, you won’t lose the items if your network connection breaks before you have a chance to paste whatever you cut.
  • The Clipboard will hold on to the items for 20 minutes, to give you time to think about where you want to put them. (And, to recover from any network problems you may have experienced.)
  • If you don’t paste something that you had previously cut, the Clipboard “releases” it back to where it was originally, after waiting 20 minutes to go by while you ponder. But, if you are impatient, you can reverse your cut action sooner simply by clicking on the cut items, which continue to appear in a faded (greyed-out) appearance on your board.
  • Because the Clipboard is on the Kerika Server, other team members won’t see the change until you actually do the paste. So, for example, if you have cut some cards from a Task Board or Scrum Board and haven’t pasted them yet, your project team members will continue to see the items on the old board until you complete the paste.
  • And, finally, here’s a great feature, thanks to the Server Clipboard: one of your team members can be making changes to a card while you are in the process of cutting-and-pasting it, and those changes aren’t lost. That’s because the object is stored on the server rather than your browser, making it possible for your team members to make changes even as you are in the process of doing a cut-and-paste.