Overview

Kanban In a Kan (KIK) is like a can of beans. We provide the basic structure that your organization can fill with whatever type of beans you want. Whether you choose French Cut Green Beans, Yellow Wax Beans, or Brown Sugar Baked Beans, KIK delivers a “kanned” Agile tooling solution in industry leading systems based on a standard Agile Kanban workflow that you then customize to fit your company’s unique place in the market.

We customize Jira to have a Level 3 Kanban Maturity Model value stream in a Product funding financial model. With the process and supporting tools as a baseline, we then listen to what aspects of the overall solution need to be modified to meet your organization’s specific needs. We then tweak the “kanned” solution to provide a customized fit-for-purpose solution around people, processes, and tools that can continuously mature and evolve with your organization.

Agile Teams can use Scrum in a larger Kanban context. Upstream workflows that Product Owners manage, such as Epics and Features, do not follow typical Scrum processes. They do utilize Kanban boards to visualize the upstream work status and manage customer expectations. With Scrum Off the Shelf (SOS), Agile Teams that still want to execute Scrum on Stories, Tasks, and Defects, can do so even though the overall end-to-end customer value stream is inherently executing Kanban.

Currently available for Jira Cloud and Jira Data Center.

Introduction

Since its inception in 2001, the Agile Manifesto and its supporting twelve principles have encouraged many organizations to move on from legacy Waterfall processes and adopt Agile Scrum. At agiledoyens, we feel that Kanban is the next evolution of Agile and many of our solutions center around Kanban principles. Even the most diehard Scrum advocates must accept that upstream workflows that Product Management typically owns (Initiatives, Epics, Features, etc.) are not executed using Scrum. Product Owners don’t conduct Sprints, hold Scrum ceremonies, or point portfolio level work items. They do typically view status and progress via Kanban boards that support the overall customer value stream from idea to delivery as a single continuous flow Kanban system.

Yes, it is a cookie cutter

You will often hear agilists say that implementing Agile cannot take a “cookie-cutter” approach or that “no one size fits all”. Is that statement intended for Agile Teams within an organization, across different organizations, or both? If you don’t apply some level of standardization to an overall Agile approach within an organization, then it becomes all but impossible for management to understand what is happening across the organization. Agile frameworks such as Scrum and SAFe are designed to be cookie cutters across organizations. You start with a baseline approach and then tweak and modify that approach to fit each organization’s unique industry and specific needs. Kanban In a Kan (KIK) follows that same basic concept. It is a “kanned” baseline Kanban approach for a customer value stream from idea to delivery. It is a cookie cutter that can be applied to any Agile Team in any industry doing software development. However, every organization, and Agile Team within an organization, can differentiate themselves by choosing to make chocolate chip, sugar, or peanut butter cookies.

Challenges

“We are a Scrum/SAFe shop.”  Great!  “We have invested heavily in Scrum/SAFe training and have no capacity or budget to learn or implement anything else.” Not great!

An organization that adopts a culture based on the belief that processes and tools will stay static for decades are applying the same failures of Waterfall to Agile. An organization that is built to last is always looking at new ideas and ways to evolve. To quote W. Edwards Deming – “It is not necessary to change. Survival is not mandatory.”

Agile evolution

Many organizations have already implemented Agile and are likely in the early stages of an agile transformation. Kanban In a Kan (KIK) is not something new. It’s evolutionary not revolutionary. All the Agile concepts and principles that have been learned still apply and still have value. However, at some point organizations need to evolve or risk becoming stagnant and surpassed by their competitors. A shift from timeboxed Sprints advocated in Scrum to a continuous flow Kanban approach is a modest change that most Agile Teams prefer.

Pricing

$20,000 for KIK and SOS baseline templates (includes Transformation workshop and supporting Confluence content)

LET’S WORK TOGETHER

We challenge ourselves to continuously learn and implement new ideas, techniques, and tools that help our customers deliver high quality solutions as efficiently as possible.

LET’S DO THIS