The Second Breakthrough in
Agile for Hardware Development:
“Make decisions at the right time,
with the right people, and the best available knowledge.”

When I started applying the lessons from my “Scrum for Knowledge Work” in product development teams with deadlines, it became clear right away that some things were working better than others. The structure made it possible to implement Dr. Ward’s…

Three Breakthroughs in Agile Methodology, For Hardware Developers:
Deliver your physical products faster,
with an agile system that’s designed for it.

Most of what passes for “Agile for Hardware” is really Scrum for Hardware: organize work into sprints, manage tasks with backlogs, and perform the “ceremonies” of Agile: daily scrums, etc. Or they impose another Agile method, asking the hardware teams…

The Agile Roots of the
Rapid Learning Cycles Framework:
Why your teams need to use different language for different work.

When people with Agile experience see the Rapid Learning Cycles framework, it looks familiar. That’s not an accident. Our first attempts with Rapid Learning Cycles used Scrum. We knew that some people in the Scrum world, including some well-known consultants,…