Amir and I have been so busy in the past few months that we’ve not been able to do much work on the blogs or the book. But, a window opened up and we’ve got some new ideas to share. We’re calling them, collectively, TDD Mark 3, and we’ve written the first blog about it. Take a look!
A few years ago I called Kanban (by which I mean the term generally and not limited to the Kanban Method which I now call LKU Kanban) the 2nd generation of Lean-Agile. I now realize we are already ready for the 3rd generation of Lean-Agile methods. Let me explain.
Both Scrum and Kanban are based on Lean principles and practices to different degrees. They pull from some common principles/axioms and add some things unique to themselves. Scrum and Kanban both include:
My last blog hinted at describing a new way to create frameworks/methods/processes (henceforth in this blog called frameworks). I’ve decided to do a couple of other blogs first to deepen my understanding of my intended approach. But I’ll tell you where I am going.
Disclaimer: I could have named this framework/method/process myopia, but that seems a bit redundant. So don’t infer I mean to pick on any Agile approach that is a framework over one that is called a method or a process. I am just using the word framework generically. For the purposes of shortness, whenever I use “framework” in this blog, pretend I’ve said “framework/method/process/…”.