Karl Scotland – Using Agility Strategically
Karl Scotland – Using Agility Strategically
Browsing Tag
I put together a small simulation for the SPA Conference this year which seemed to go well, and which I re-ran at the London Limited WIP Society, and hope to run again. You can download the materials, and this is a short write-up of how it works so people can run it and experiment with it themselves. Overview The basic …
Mary Poppendieck gave a talk on Workflow is Orthogonal to Schedule at Agile2009, during which she very neatly transitioned a schedule-focused view of work, into a flow-focussed view. At least I thought it was neat, so I’m going to try and reproduce the basic elements here, using my favourite agile workflow. 4 Week Time-box Schedule Here we have a schedule …
I recently wrote what I considered to be the four primary practices of a Kanban System for Software Development: Map the Value Stream Visualise the Value Stream Limit the Work in Progress Establish a Cadence During subsequent discussions on the aspect of Continuous Improvement in a Kanban System, I decided that there was a missing fifth primary practice: Reduce the …
While the word Kanban comes from the Japanese for “visual card”, the term Kanban as used by the Kanban Software Development community, represents much more than a standard task-board, or team-board. Additionally, the Kanban Software Development community have not tried to replicate the mechanism of the Toyota Production System kanban tool exactly, but have taken the underlying principles in order …
At the SPA conference recently, Joseph Pelrine talked about “Flow: The Psychology of Optimal Experience” by Mihalyi Czikszentmihalyi. The ideas behind this struck a chord with me as a way of describing something I originally said when discussing whether kanban is only suitable for mature teams. That is that rather than focusing on being Agile which may (and should) lead …
I use a simulation when I have time in presentations on Kanban, Flow and Cadence, which I hope makes the ideas a bitter clearer and more concrete. I was asked if I could make the materials available, so here they are with an explanation. Its not perfect, and can be slow and time consuming, so I’d love any feedback on …
Intro There has been some noticeable increase in interest in Kanban recently, with a number of people asking for more basic info, and more people writing new blogs and articles. This is my attempt to describe in more detail my take on it all, which I refer to as Kanban, Flow and Cadence. Kanban – Controlled Work Flow – Effective …
I’ve been involved in a number of discussions about how User Experience work fits into an Agile process. As a result a trying to articulate my position, I’ve come up with the following explanation of the anatomy of an MMF. The following diagrams assume the following key: Lets start by looking at a typical waterfall model: In this case, all …
One of the regular questions I get asked when I talk to people about KFC Development is about how it is different. As a result I came up with a set of KFC Consequences to try and help articulate this. Kanban Consequence – Eliminate backlogs, timeboxed iterations and estimates. Eliminate might be a slightly strong word, but there is certainly …
I’ve been referring to my latest thinking on development process as KFC Development. Its a bit of a gimmicky name, which makes it memorable, but there is some meaning behind it. KFC stands for Kanban, Flow and Cadence – three lean concepts which I think are important and complementary. Kanban – Kanban is the mechanism which controls the workflow and …