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 […]
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
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
An agile approach requires a cross-functional team. That means that everyone on the team focuses on the same intent. That intent might be an entire product. It might be a feature set as part of a larger program. But, the team focuses as a team. That cross-functional team is a product team or a feature
In an ideal agile world, the team would work directly with a customer. When you have a small product that serves maybe three types of customer (new, expert, admin for example), and that customer is down the figurative hall, you might not need any product people. You can create short feedback loops with your customer.
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
You’ve got interdependencies across the organization for a given project or program to release a product. You can see demos. That’s not the problem. You need enough insight or prediction to start the marketing campaign or to create training videos or product documentation. You need some kind of milestone criteria so you know you can complete
Most of my clients struggle with their agile transformation. The teams love agile approaches because they can work on their release frequency and technical excellence. The senior managers love the agile promise because they can see how agile approaches help the teams release a more constant flow of value. They can see the benefits of
Especially when we use agile approaches, we want to be close to our customer. If you’ve ever had a chance to sit with a customer, you’ve learned how effectively (and fast!) the team and the customer learn from each other. And, too few teams have any access to any customers. Most of their customer information
I just finished a series for my Pragmatic Manager newsletter about Agile Transformation Secrets: Part 1: Manage for Change Part 2: Emphasize Collaboration Part 3: Principles Over Practices I wrote this series because I find that many people get a little confused about an agile transformation. They think an agile approach will work because they