Cayzen Technologies organized a Lunch & Learn Agile event at the Harbor House at Percival Landing in Olympia, Washington, featuring Arun Kumar, CEO of Kerika.
Arun’s topic was Implementing Lean across Distributed Teams, and we would like to specially thank Mayra Pena from Cayzen who organized the event:
Arun Kumar & Mayra Pena
The event was attended by folks from Washington State’s Employment Security Department and Department of Health, among others, and there was a lively discussion.
Here are the slides from that presentation:
If you would like to see the sample Kerika board that featured in the demo, go to https://kerika.com/m/H51M
We are thrilled to announce a great new feature: Work-In-Progress (WIP) Limits for Kanban Boards and Scrum Boards.
WIP Limits are a very helpful tool when you are working in a true Kanban style: where work gets “pulled” as people become free, rather than work getting “pushed” onto people before the people ready.
To understand the difference between “push” vs. “pull”, think back to that famous episode of “I Love Lucy” where Lucy and Ethel take up jobs at a chocolate factory, and quickly find themselves unable to keep up with all the work that’s getting pushed onto them:
This is a perfect example of the perils of “push”: as the chocolate gets prepared upstream, the work becomes ready even though the people aren’t ready for the work.
If you push work on to people who aren’t ready to take it on, you will quickly have disastrous results. (It’s funny only when it’s on TV and it involves Lucy.)
At the very least, you will have an imperfect understanding of what each person is actually doing, if people upstream in the project’s workflow simply push work downstream as soon as the upstream folks are done with it.
A pull model is different: people “pull” work and assign it to themselves when they are ready.
Each person typically has a small number of items they are juggling at any time: it may be as few as two items, depending upon the complexity of the work, but it is rarely as few as just one item.
(You nearly always want to have one “background” task ready to be picked up whenever your “foreground” task gets blocked for any reason.)
When a person is able to take on a new task, she can “pull” a card from the column to the left of her on a Kerika board.
Here’s a simple example, reflecting the workflow for a software project:
WIP Workflow Example
This project includes people with different roles: designers, developers and QA, and each group has determined it’s own WIP limits, based upon the team’s capacity and velocity.
In this particular example, we can see that the Planning & Design and Deployment columns have currently exceeded their WIP limits (and, in the case of Deployment, by a large margin!)
When this happens, Kerika alerts you to the condition by showing the affected columns with red text in the column headers:
Example board with WIP exceeded
WIP Limits as “soft limits”: Kerika doesn’t stop you from exceeding a column’s WIP Limit, but it does provide a very clear, visible warning to everyone that a bottleneck is about to form.
When bottlenecks start to form, the Project Leader should intervene and help manage the upstream flow so that the WIP Limit can come back to its acceptable amount.
WIP Limits originated in Kanban, but Kerika lets you use them for Scrum Boards as well!
To use WIP Limits, click on the Project Info button that’s at the top-right of the Task Board or Scrum Board:
In both cases, it turned out that the Google Apps Admin had previously authorized Kerika only for a subset of their Google Apps domains, i.e. for an Organizational Unit (OU).
Even when the OU has been set up to override the master settings of the domain, Google seems to be giving us an error (specifically, our server is told by Google’s authorization server that “domain policy checking failed” — this is the check that we do to see if the Google Apps domain is authorized.)
The simple fix is to authorize Kerika for the entire domain rather than a subset of users.
Naturally, our users wonder if this means they need to license all of the users registered within their entire Google Apps domain: the short answer is “No” — you need to license only those people who are actually using Kerika.
So, don’t worry about getting stuck with a big bill simply because you authorized the use of Kerika within a large Google Apps domain: all you are doing is making it easy for your colleagues to try out Kerika.
If they try out Kerika and like it, we can talk about licensing then…
The announcement by CERT yesterday that there is a vulnerability in the Bourne Shell (more commonly known as “bash”) wasn’t great news for anyone running any variant of Unix, which includes Linux and MacOS.
There are a number of variants of Linux out there, which makes things a little harder whenever a vulnerability is announced: you have to make sure your particular variant of Linux is patched quickly.
Luckily, this problem was fixed as fast as the notorious Heartbleed bug: within a couple of hours of the report of Shellshock, Amazon and Google (and, most likely, every other cloud services provider out there) started installing patches, and so the Software-as-a-Service (SaaS) world got back into good shape very quickly.
In our own case, we use Ubuntu Linux, and they were equally swift in issuing a patch for Shellshock which we installed yesterday.
That’s true only in a literal sense: the vast majority of Mac users don’t ever use the Terminal program to access the shell, and a lot of permissions on Macs are locked down by default (and most users never bother exploring all their administrative privileges).
But, in a practical sense this bland statement from Apple understates the actual risk faced by Mac users: a significant majority of startups use Mac for their software development, which means a critical set of Mac users are still sitting exposed!
The sooner Apple fixes this bug, the better is will be for the startup world.
Since our last released, when we upgraded our integration with Google Apps Marketplace to use the OAuth 2.0 protocol, a number of folks have written in to ask about how they should install and authorize Kerika for their premium Google domains (i.e. Google Apps for Business, Google Apps for Nonprofits, etc.)
Here’s a step-by-step guide for the Google Apps Administrator in your organization:
First, login to admin.google.com with your Google ID. Your screen will look like this:
Google Admin Console
On the right side of the screen, you will see a link for Google Apps Marketplace, in the area marked Tools:
Go to Google Apps Marketplace
When you click on the “Google Apps Marketplace” link, you will be presented with a search box that looks like this:
Searching for Kerika
Type in “Kerika” in the search area, and you will find us!
Adding Kerika
Once Kerika shows up, click on the blue “Install App” button:
Installing Kerika
Click on the blue Continue button, and you will be asked to authorize Kerika for your Google Apps domain:
Authorizing Kerika
And that’s it! Your final confirmation message will show:
All Done
And at this point Kerika will have been authorized for your entire Google Apps domain. Individual users will be able to sign up without going through any of this hassle.
If you have any difficulties or questions with this, please email us at support@kerika.com
I will be presenting on Implementing Agile across Distributed Teams at the Lunch & Learn Agile event on October 2, 2014 at the Office of the CIO for Washington State.
The event is being organized by Cayzen Technologies; if you are interested in attending, please contact Mayra Pena.
Ben Vaught, from the Washington State Office of the CIO, and I had the pleasure of presenting at the state’s Office of Financial Management’s Fall Forum last week, held over two days at the Thurston County Fairgrounds in Olympia.
Ben talked about the use of visual processes as part of the Washington Business One Stop initiative he has been working on for a while, and towards the end of his talk he showed some pictures of the WIKISPEED garage in Lynnwood, where I first met Ben and Michael DeAngelo, Deputy CIO for the state.
My talk was supposed to have been on Visual Management in government and administrative processes, but seeing pictures of the old WIKISPEED garage, which used to be covered with stickies on all walls (including the massive garage doors!) before the team adopted Kerika to knit together their global community of volunteers, was a wonderful throwback moment!
When it came to my turn, in addition to showing the use of Kerika for cross-agency GIS projects, such as those led by Joy Paulus, I was also able to show examples of Kerika in use by Sherri Hrubi, Danica Ersland and Melissa Wideman, who all work together in OFM’s HR Division.
Several other people presented, including Irene Hill and her design team from the Department of Licensing, Howard Cox from the Department of Enterprise Services, and Eric Gardner from OFM’s Forecasting Division.
Between the hours of 9AM and 11AM PST, Google’s authentication service — which we used to sign in users of Kerika+Google — kept having problems that affected people at random.
It was a tough morning for us, dealing with the flood of “504 System Timeout” errors coming back from Google, and feeling helpless that we couldn’t provide the kind of high-quality user experience that is at the core of the Kerika brand.
The problems finally went away by themselves, but a total of 31 Kerika users were affected and we are reaching out to each of them individually to apologize for the inconvenience, and explain what happened.
This is one of those situations where Kerika cannot do anything to fix the problem: if you signed up as a Kerika+Google user, when you try to login to Kerika you are automatically redirected to Google’s authentication service, which then comes back to Kerika to give us your identity information.
Then, we use the identity information to log you into the correct Kerika account.
Normally, all this happens really fast: you click on the Sign In button at Kerika, Kerika redirects your browser to Google, Google responds immediately, and within a couple of seconds you are logged into Kerika.
It all happens so fast and smoothly, 99.999% of the time, that most people are completely unaware that their browser was even redirected to Google in the first place — it’s something you might notice only if you have a very slow WiFi connection, and you are paying close attention to your browser’s status bar.
But every once in a while, Google won’t respond when you get redirected there by Kerika. In that case we retry again several times, and then finally Kerika does a “timeout”: it gives up.
(This problem has happened before, and as software developers ourselves, we are, of course, very sympathetic to other software companies that experience occasional bugs and hiccups, but Google can be irksome in their lack of transparency.)
This happens so infrequently that we didn’t really have any special code in place to tell users why they were not able to login, but that’s going to change starting tomorrow: if Google’s servers are not responding fast enough, we will show a special page to the user explaining what’s happening, so they understand the situation better.
Between 9AM and 11AM Pacific Standard Time, Google’s authentication service threw up about about 60 errors, which gave many of our users a rough ride.
The problem was that Google’s authentication servers were timing out repeatedly, showing errors like this:
Request URL: https://kerika.com/authcallback/google?code=XXXXXXXX
Request Method: GET
Status Code: 504 Gateway Timeout
There isn’t anything we can do in this situation to help our Kerika+Google users, unfortunately, since Google’s authentication service needs to be up and running in order to log in to Kerika.
The silver lining in this cloud, for now, is that this is a relatively rare occurrence.
