product management

agile, MPD

Balance Innovation, Commitment, & Feedback Loops: Summary

Is it possible to balance the product innovation and feedback we need, with the commitment our management wants? Maybe. I tried to show my thinking for these questions in this series: When does it make sense to ask for or offer estimation and commitments? When does it make sense to ask for more feedback instead? […]

MPD, product ownership

Planning: Risk Management to Manage Uncertainty

Many organizations plan to create certainty, guarantees of some variety. What if we thought about agile planning as a way to manage uncertainty? When I look at long roadmaps with all the “must-do” feature sets and the pressure managers put on teams to commit to delivery, I wonder about this question: How well do we

Syllabus

Practical Product Owner Workshop: Deliver What Your Customers Value and Need

I no longer offer this workshop. Please see Practical Product Leadership: Deliver Better and Faster with Continual Replanning Workshop for the updated syllabus. Does this describe your product ownership predicament: You are supposed to be the product manager, product owner, and business analyst. You might even juggle different responsibilities for multiple teams. You struggle to read

conference, MPD

My Agile 2015 Roundup

Agile 2015 was the week of Aug 3-7 this year. It was a great week. Here are the links to my interviews and talks. Interview with Dave Prior. We spoke about agile programs, continuous planning, and how you might use certifications. I made a little joke about measurement. Interview with Paul DuPuy of SolutionsIQ. We

MPD, product ownership

How to Use Continuous Planning

If you’ve read Reasons for Continuous Planning, you might be wondering, “How can we do this?” Here are some ideas. You have a couple of preconditions: The teams get to done on features often. I like small stories that the team can finish in a day or so. The teams continuously integrate their features. Frequent features

MPD, program management

Reasons for Continuous Planning

I’m working on the program management book, specifically on the release planning chapter. One of the problems I see in programs is that the organization/senior management/product manager wants a “commitment” for an entire quarter. Since they think in quarter-long roadmaps, that’s not unreasonable—from their perspective. There is a problem with commitments and the need for

MPD, product ownership

Who Should be Your Product Owner?

In agile, we separate the Product Owner function from functional (development) management. The reason is that we want the people who can understand and evaluate the business value to articulate the business value to tell the people who understand the work’s value when to implement what. The technical folks determine how to implement the what.

Scroll to Top