component teams

newsletter

Three Tips to Focus to Deliver Better Products Faster

Susan, a new-to-the-company program manager, could not understand why Product A was so late. The teams used a well-known agile approach. They weren’t working on anything else except for production support. Yet, even though the teams worked hard, not one team could meet any of their deadlines. The teams were unhappy with their progress. They

management, MPD

Component Teams Create Coupling in Products and Organizations

Many of my clients feel stuck with their component teams. They feel they must implement across the architecture, not through it. That’s because the people are organized in component teams. As the organization grows, so does the number of component teams. The more component teams they have, the more complexity they create in the teams, in

agile, MPD

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

MPD, product ownership

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

agile, MPD

Product Roles, Part 5: Component Teams to Create Slices

As I’ve written these product role posts, a number of you have asked about how to use component teams. You might have a security team. Maybe a performance team. Regardless of my desire, you have component teams. You want a more agile approach to manage the interdependencies among the teams. You want to be able

agile, MPD

How Long Are Your Iterations? Part 2

When I teach agile, I explain I like small and short stories. I want to see value in the product every day. Many developers can’t do that. That’s because they have interdependencies with other teams—not developers on their team, but other teams. They can’t implement in the way the picture next to this shows: small,

Scroll to Top