The document describes 5 levels of collaboration between product teams and stakeholders: 1) Void - Teams work in silos with little understanding of user needs. 2) Foundation - Teams start to understand user needs but lack exposure to business value. 3) Discovery - Teams can describe value and follow key performance indicators with the business. 4) Formation - Teams work directly with clients to validate solutions and provide input on objectives. 5) Maturity - Product vision and objectives are central to discussions as stakeholders and teams regularly collaborate on portfolio and roadmap.

1. Levels of Collaboration
Collaboration
Benefits
Luc St-Laurent and Stéphane Lécuyer Better answering the business needs
Void
Fondation
Discovery
Formation
Maturity

2. Level 1 - Void
Learn how to use user stories
Discuss the different product
personaes
No longer talk about a project. Talk
about a product.
To Do
Characteristics
Backlog items do not talks about users or
value. They are simply big tasks.
The team does not understand the why.
The “need” concept is missing.
The discussion around the product is missing.
Members talk about the “Why” in the context
of their own responsibilities (silo).
Luc St-Laurent and Stéphane Lécuyer Better answering the business needs

3. Level 2 - Fondation
The team to present the business value
of their work during the review
Use the review to increase client
interaction
Follow delivered value over time using
KPIs
To Do
The team has an understanding of the
users and their needs.
The team is not expose to the business
value generated by its work.
Engagement level is generally low.
Characteristics
Luc St-Laurent and Stéphane Lécuyer Better answering the business needs

4. Level 3 - Discovery
Team members can, at any moment,
describe the value of their work.
KPIs are in place and are actively followed by
the team.
The team is asking to contribute more to the
product with their ideas.
Characteristics
The team to learn to ask “Why” ( X 5 )
Introduce the client (ideally the end-user) to talk
with the team prior and within a sprint
PO to write the acceptance criteria with the team
The team to learn to ask about the impact of a story
on the followed KPIs
To Do
Luc St-Laurent and Stéphane Lécuyer Better answering the business needs

5. To Do
To learn the various types and technics of
collaborative product discovery sessions, and
learn to use them
PO to include team members in value
roadmapping exercices and product objectives
discussion.
To learn to consider R&D and technical debt in the
product strategy.
Level 4 - Formation
The team has learned to work with a client to
find the best solution to his need.
The team validates with the client each
acceptance criteria.
The team is requesting visibility and interation
with the product objectives and roadmap.
Characteristics
Luc St-Laurent and Stéphane Lécuyer Better answering the business needs

6. Level 5 - Maturity
Product vision and objectives are at the center of
discussions.
The team understands the business challenges
associated with the product and the business
stakeholders understand its technological challenges.
Stakeholders and the team collaborate on a regular
basis to review the products portfolio and the
product roadmap.
Luc St-Laurent and Stéphane Lécuyer Better answering the business needs

7. Benefits of a strong collaboration
1 – Products that respond to real needs
2 – Better innovation (Medici Effect)
3 – Improved employee engagement
4 – Increased in Bus Factor
5 – Higher team retention
6 – Increased ROI
Luc St-Laurent and Stéphane Lécuyer Better answering the business needs

8. Common impediments to collaboration
1 – Fear of loosing control
2 – Fear of loosing power
3 – Cost increase perception
Luc St-Laurent and Stéphane Lécuyer Better answering the business needs