Let’s assume that your team does have a definition of Ready. And that they (possibly with a product leader) have shaped the work. But the team still says they don’t know how to start—they don’t have the right people to think through the problem and finish it. If you have component teams, the team is […]
Three Planning Ideas to Support Your Future Decisions Many organizations use deliverable-based planning, specifying the various features or products the teams expect to deliver and when. I’m a fan of short-term deliverable-based planning because it focuses everyone on the (few) deliverables. But the pandemic taught us a critical idea: while long-term deliverable-based planning can illuminate
Most managers I see feel a ton of pressure for delivery. The managers need to “deliver” more projects, products, and features. That pressure rolls down to the teams. Too often, the team hears, “Can you just do a little more?” That often leads to the so-called “quiet quitting” problem. The problem isn’t quiet quitting. The
I started this series by sharing my status of too much WIP (Work in Progress). My WIP was making me slightly crazed and I explained how I worked to reduce it. In case you’re wondering, here’s my current status: 3 presentations still on the list (I completed 2, including the one I recorded). The online
I hate the fact that I let my WIP get this high—and I’m glad I’m working it down. (I wrote why I let my WIP get this high on my other blog in the post, What Would It Take for You to Fail to Success?) My status today: Finished one more presentation and need to
I’m halfway through this week of working through my too-high WIP. So far, I exposed my WIP and talked about how I planned to use continuous flow in Part 1. Part 2 was about cycle time and using Cost of Delay to make easier decisions. Today is about why I don’t use a real backlog
As I said in my Day 1 post, my WIP is too high. Here’s where I stand with my WIP: I completed one presentation, so I have 4 remaining I have some feedback on the book that I need to integrate. I want to address the next 3 chapters, because they’re the platform for the
As with many of you, sometimes my WIP (Work in Progress) is too high. When that occurs, I don’t use a backlog or create iterations. Instead, I use continuous flow. That’s because working in flow allows and creates ease in my development. This week, I want to finish these things: 5 presentations, one of which
I recorded a Being Human podcast with Richard Atherton. It’s wide-ranging from thinking about agile approaches as a way to improve organizational flow and what that means for us as humans. I had a blast. I think Richard did, too. He’s a think-before-he-speaks person, and if you watch the video, you can see him thinking.
Do you struggle with your agile approach? Sometimes, iterations don’t work for teams. Sometimes, flow doesn’t work. Sometimes, you need both. To celebrate the release of Create Your Successful Agile Project: Collaborate, Measure, Estimate, Deliver, I am writing a series of articles on Infoq. The first article, Customize Your Agile Approach: Select Your Agile Approach That Fits