A guy walked up to me and said “I hear you’ve got a problem with Flash”. I hadn’t met him before but I’d heard about him. Mike Brown the Development Paratrooper.
Continue reading
Tag Archives: flow
Work Item Tracking, to See or Not to See?
Work Item Tracking, to See or Not to See? This is always an interesting debate. The lists are much longer but for simplicity I’ve surfaced a few salient points. So which is best? Physical or virtual? For me physical boards win hands down, but there are occasionally good reasons for a careful blend.
Continue reading
How to Distinguish Between Activity and Queues on a Kanban Board
My Kanban boards follow a certain pattern, what I call the “Step In Progress then Done” pattern. By default each step in my process has an “In Progress” column and a “Done” column. Some people don’t like that. You wouldn’t believe the number of conversations I’ve had about it. These conversations more or less boil down to me explaining that “Done” is a queue, not an activity. And I want my Kanban board to make it clear that each activity has an associated queue.
Continue reading
Did HeartOfAgile emerge from PDCA?
I don’t know if it was Alistair Cockburn’s inspiration but I’ve noticed a striking similarity between Cockburn’s HeartOfAgile and the plan-do-check-act (PDCA) cycle of TQM.
Continue reading
A U in UX
Obvious, right. Well, perhaps not. After all, what is UX anyway? I have many conversations on this topic, with developers and UX designers, and I never seem to get the same answers. I find that both fascinating, and a little frustrating, and I’m very aware that the feeling’s mutual! I have a simplistic view on this, fortunately for me it aligns with the definition that pops up when you Google (other search engines are available) “what is ux”.
Continue reading
Going back to basics with Agile, what would we find? The Heart of Agile
In a world with non-software Agile and Agile at scale, what is Agile? I think Alistair Cockburn has hit the nail right on the head with his recent HeartOfAgile.
Continue reading
What is the optimal number of manual testers in a development team? Zero?
To have manual testers, or not to have manual testers, that is the question. Typically I have one per team: Less than many teams but more than some organisations get away with.
Continue reading
Lead time versus Cycle Time – Untangling the confusion
Despite being a fan of Lean and using Kanban I’ve stopped talking about “Cycle Time”. The problem is that there are two conflicting definitions of Cycle Time. And one of those definitions is identical to Lead Time. Given the competing definitions for Cycle Time, and that the variations have alternative unambiguous names, it is easier not to use the term at all. All I need is “Takt time”, “Order Lead Time” and “Production Lead Time”.
Continue reading
Look for Product Owners in the Business
You cannot lead what you don’t understand so I often recruit product owners from the business.
Continue reading
Make BlackOps development the Corporate Standard – Embrace Microservices
Contrary to how they are perceived in the media as lumbering dinosaurs, most large organisations have loads of clever people and good ideas.The trouble is these organisations can’t deliver against the ideas. The answer is not “Blue Sky” R&D departments or “BlackOps” teams. The answer is to make the BlackOps approach standard; create an innovation platform built from microservices with new services deployed swiftly into production.
Continue reading