Product Roles, Part 8: Summary: Collaborate at All Levels for the Product

Too many teams have overloaded Product Owners. The teams and PO have trouble connecting the organization’s strategy to what the teams deliver. The teams, PO, management, all think they need big planning. Too often, the POs don’t do small-enough replanning. They’re not living the principles of the agile manifesto. That insufficient collaboration means the PO …

Product Roles, Part 6: Shorten Feedback Loops

I started this series discussing the issue of the various product-based roles in an agile organization. I suggested a product value team because one person becomes a bottleneck. One person is unlikely to shepherd the strategy and the tactics for a product. And, batching the product planning in one-quarter chunks doesn’t encourage us to reduce …

Product Roles, Part 4: Product Orientation and the Role of Projects

Many people in the agile community promote a product orientation over a project orientation. That’s possible because an organization has product or feature teams. That works until you have more products than teams. That’s when you might still need projects to accomplish everything. If you keep teams together, you can still use projects in a …

Balance Innovation, Commitment, & Feedback Loops: Part 1: High Innovation Products

Many of my clients are trying to use short feedback loops in agile approaches. That desire bumps up against their management’s desires for longer commitments. This continuum might help them think through their needs for commitment and innovation. High Need for Product Innovation and Change The more need for product innovation and change, the shorter the feedback loops need …

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? …

Balance Innovation, Commitment, & Feedback Loops: Part 3: Low Innovation Products

What if you don’t need to experiment to reduce risks? You may have technical risks in terms of getting it “all” done. Especially for a given release date. In that case, you have a low need for product innovation. Your planning feedback loops can be longer. I’ve seen this occur in some of these circumstances: A …