March 12, 2018

Kanban to manage Complex/ Quick Moving Situations

Is this you? That is, does the question below, which I answered on a technical forum recently, describe a situation you might be facing or may have faced in the past?
March 8, 2018

Fika Stories 1 – Help! Our Kanban Died!

In this 2-part series, we are honored to publish a couple of blog posts by (2016 Brickell Key award winner) Christophe Achouiantz, Kanban thought-leader, consultant and coach. Written in the “Fika-style” (read on to understand what that is!), Christophe takes on the all too common problem that teams implementing Kanban (or any other process change initiative for that matter) face – the sense of “doom” that Kanban is not working for them because of resistance they face. In this first part, Christophe explains why that is a good thing!
March 2, 2018

Kanban = Continuous Delivery? Not Necessarily

Here’s is another question that I recently answered on a discussion forum –
February 21, 2018

Extending Portfolio Kanban with Enterprise Services Planning

Transformation approach using the enterprise services view, balancing system demand with capability, planning and prioritization using a visual decision framework, using decision support analytics like probabilistic forecasting and cost of delay.
February 19, 2018

The Difference Between The Kanban Method and Scrum

Introduction
February 12, 2018

The Yin-Yang of Productivity

This year’s Nobel for Economics has gone to the Behavioural Economist Richard Thaler. Richard is a Distinguished Professor at the Chicago Booth Business School. His big work is the influence of clues and society on individual decision making and actions.
February 7, 2018

Scrum or Kanban for Application Support teams?

Recently, there was an interesting problem posed on a project management discussion board. The questioner asked -
January 29, 2018

Scrum and Kanban Revisited

Introduction
January 21, 2018

How do you “do” Scrumban?

In a recent post on a technical forum, a Dev manager had the question (paraphrased here) - My organization wants to operate in a Kanban way but maintain the structure of sprints and burn down charts to keep track of progress. Is it ok to do? Is Scrumban the correct methodology? If so, what is the best way to implement it?