Product-Led agility TM
A collection of patterns that help agile teams move beyond feature delivery to focus their efforts on outcomes over outputs.
One single team with all required skills
The team developing the product (a.k.a. Product Team) has all the required skills to build the product or product area they are responsible for. The Product Team doesn't depend on third parties to successfully do its job.
Balancing Strategy, Discovery & Delivery
The Product Team is capable of doing continuous discovery and delivery, balancing both disciplines, and periodically reviewing and adapting the product strategy.
Working with outcomes-based roadmaps
The Product Team receives a roadmap of problems to solve (opportunities). The Product Team comes up with experiments with feature ideas (tentative features) for each problem or opportunity.
Interacting with end-users
The Product Team interacts directly with end-users. The developers observe them, interview them and meet with them periodically.
Being the primary source of ideas
It is the Product Team the source of ideas. All other ideas (coming from users and stakeholders) are turned into opportunities instead of required features. To successfully do it, the product team needs to understand the problem behind each of these ideas deeply.
Continuously discussing expected outcomes
The Product Team discusses acceptance criteria for each feature to be delivered and the expected outcome in terms of user behavior, product health, and business goals.
Focused on Influencing real users behaviors
Product Team don't take the Definition of Done and acceptance criteria as the end of the road. Instead, they understand that it's just the beginning of a multi-iterations journey to inspect and adapt each feature until it delivers value.
Periodically reviewing their outcomes
The Product Team periodically reviews the delivered features and the product health and expected outcomes.