Three Ways to Manage “Extra” Work in an Iteration

Many of my clients use an iteration-based agile approach. And, they have these problems: They “push” too much into an iteration. They use velocity, not cycle time to estimate.  They rarely finish everything before the iteration ends. They have to manage extra work—work they had not estimated—in the form of an emergency or production support. …

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 …

Product Roles, Part 1: Product Managers, Product Owners, Business Analysts

We have many words for people who shepherd the business value of a product. The many words aren’t a problem, as long as we can all agree on what these various people are and they take responsibility for. When we don’t agree, we run the risk of not managing our strategy, not thinking in terms …