pa-logo

 
Product Agility is a gathering of people focused on producing more of what is really needed and less of what is not needed, not useful, or never used. Our inspiration spans a wide range of processes and principles. From Intuition Engineering to Lean Product Management, we’ve incorporated practices associated with evidence of success.
While collaboratively framing Product Agility 0.1.0, we imagined small teams and large programs learning faster and making better choices by frequently validating ideas in a blended cadence of discovery and delivery. Please join the community and help us spark meaningful discussions in digital forums and at local groups around the world.

Product Centered Principles

Bond Teams Around Products and Services – ensuring teams are able to gather evidence in eco-systems where failure is reframed as learning in the form of small experiments.
Embrace Uncertainty and Avoid Product Arrogance – being ready to be wrong and focusing on validated learning from evidence derived from a blended cadence of product discovery and product delivery.
Build Lean and Anti-Fragile Environments – automating and collaborating across perspectives, allowing more access to more people. Build visualizations that promote discussions of environment health and complexity.
Validate Against Concise and Measurable Goals – using evidence to bravely decide to pivot or persevere. Balance a willingness to be wrong with the discipline of not giving up without a fight. Strive toward your next best investment instead of merely getting more done faster.

Product Centered Learning

 

flow-diagram

As a rough guide for how we work, we created a simple graphic and associated it with a collection of practices. Please avoid seeing these as “the way to do work”. Instead, view them as a starter set that supports the principles listed above. 
The graphic is meant to show a simple, but not singular progression, starting with the creation of product oriented teams before moving on to early product discovery. From there, we have tried to re-frame planning to be more about learning and less about scheduling. Lastly, we are hoping to foster ways of working the blend learning from discovery with learning in production.
Clicking on any of the category titles will take to you a more detailed explanation of the practices it contains. Please send any suggestions or ideas to info@productagility.org – Enjoy!
Map Teams to Products
Create Safe Work Spaces
Select Just Enough Process
Foster Ubiquitous Leadership
Why are we doing this?
Who do we want to learn about?
What are their needs?
Where should we start learning?
Right-Sizing Work
Add Early Validation
Build Impact-Oriented Horizons
Learn Outside Production
Blend Discovery and Delivery
Bond Communities Around Impact
Practice Responsive Engineering
Visualize and Address Complexity

Join the Product Agility Community

Please join our growing community, by clicking the “Join the Community” button. We’ll add you to the Product Agility community and send you notifications when we update the content on the site based on the feedback we hear and the information we gather.


Product Communities

Product communities are one or more blended teams working together to learn about customers and their needs. A blended team has product, design, and engineering skills. The following practice are some, but not all, of the practices that we have found to build better bonds around customer and product learning.

Map Teams to Products
Create Safe Work Spaces
Select Just Enough Process
Foster Ubiquitous Leadership

Early Discovery

The amount of discovery that happens outside of the continuous learning varies. For new ideas, it might be called “initial discovery”. For many product communities, some amount of early discovery happens before a blended cadence of learning from discovery and learning from delivery sets in. The following ideas of why, who, what, and where are possible with various techniques and at varying levels of depth. More important that the tools in use is the importance of getting to the real needs of the people who will be impacted by the product or services produced and narrowing down the universe of all ideas and choosing where is the most importance area to start learning.

Why are we doing this?
Who do we want to learn about?
What are their needs?
Where should we start learning?

Planning to Learn

Avoiding the mythical certainty too often associated with “getting better at estimation”, planning to learn is a collection of ideas and techniques that help product communities breakdown and schedule bits of work that promote learning about customer needs, learning about the technology in play, and learning how to work within and across teams that are part of the product community.

Right-Sizing Work
Add Early Validation
Build Impact-Oriented Horizons
Learn Outside Production

Continuous Learning

We hope that this is where most communities spend the bulk of their time. For smaller communities, or what might be commonly called a single team, it is more possible to overlap or interleave discovery and delivery within a learning cycle. For larger communities, where many teams are needed to validate the needs of the customer, it might make sense to have a discovery cadence that informs a delivery cadence which then informs a discovery cadence. The following ideas / practices, are a starter set of ideas, but are in no way all the practices that a product community may use to learn from discover or learn from delivery.

Blend Discovery and Delivery
Bond Communities Around Impact
Practice Responsive Engineering

Visualize and Address Complexity