Karl Scotland – Using Agile to Deliver Value
| Print article | This entry was posted by Karl Scotland on June 22, 2009 at 8:21 pm, and is filed under Agile. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site. |
Linking Flow, Value and Capability
about 3 weeks ago - 6 comments
I wrote recently that I have come to think about Flow, Value and Capability as the primary impacts I hope a Kanban System will have. Flow, Value and Capability are not independent entities, however, with Capability being the link between Flow and Value. We can think of Flow as “doing the thing right”, where good More >
What is Capability?
about 1 month ago - No comments
I recently gave talk at the London Scrum User Group (LSUG) describing Kanban Thinking and had a very interesting conversation about what I mean by the impact on capability. I realised I needed to think it through in a bit more detail, and this is an attempt to articulate it better. Defining Capability In his More >
Impact, Outcome and Output
about 1 month ago - No comments
As I alluded to in the previous post, one of the changes in thinking, and in particular language, for me recently is the idea of impact. Specifically that impact is different from outcome which is itself different from output. I’ve differentiated outcome from output for some time, as have others, but I believe impact is More >
Three Cynefin Ahas
about 2 months ago - 2 comments
Over the last year I’ve been increasingly influenced by ideas from Cynefin, created by Dave Snowden of Cognitive Edge. If you want a good introduction, Liz Keogh recently blogged a good explanation. I’ve realised that there are 3 key changes in my thinking, some completely new, and some reinforced by a better understanding of cognitive More >
Kanban Thinking on SPaMCAST
about 2 months ago - 1 comment
I recently gave an interview with Tom Cagley who puts together the Software Process and Measurement Cast, and talked about what I am calling Kanban Thinking. The result has just been published – have a listen and let me know what you think. SPaMCAST 174 – Karl Scotland, Kanban Thinking Related posts: Lean & Kanban: More >
The Science of Kanban – Conclusions
about 3 months ago - 11 comments
This is the final part of a write-up of a talk I gave at a number of conferences last year. The previous post was about the science of economics Scientific Management Revisited Is scientific management still relevant for product development then? As I have already said, I believe it is, with the following clarifications. I More >
The Science of Kanban – Economics
about 3 months ago - 2 comments
This is the fourth part of a write-up of a talk I gave at a number of conferences last year. The previous post was about the science of process Having a good understanding of how creative people can have an efficient process still isn’t enough however. As Russell Ackoff is often quoted as saying, “It’s More >
The Science of Kanban – Process
about 3 months ago - 1 comment
This is the third part of a write-up of a talk I gave at a number of conferences last year. The previous post was about the science of people. Even though a kanban system describes knowledge work, we can still apply formal sciences such as mathematics. Rather than applying them at a detailed, micro level, More >
The Science of Kanban – People
about 3 months ago - 3 comments
This is the second part of a write-up of a talk I gave at a number of conferences last year. The previous post was the Introduction. Software and systems development is acknowledged to be knowledge work, performed by people with skills and expertise. This is the basis for the Software Craftsmanship movement, who are focussing More >
The Science of Kanban – Introduction
about 3 months ago - 2 comments
This is a write-up of a talk I gave at a number of conferences last year. I have split it into 5 parts. Abstract Science is the building and organising of knowledge into testable explanations and predictions about the world. Kanban is an approach which leverages many scientific discoveries to enable improved flow, value and More >
about 2 years ago
Sweet sidebar. There are plenty of ways of tripping up whilst explaining Kanban, in my experience [reading such things]. I don’t like the “therefore”, and I perhaps the last sentence should become a new paragraph. Blimey, check me out, wittering on. Good luck with your contribution mate.