Considerations

Feedback is a way of validating the work we are doing and the way in which we do it. Validation is defined as testing that a product or service meets the needs of the stakeholders irrespective of what the stated requirements are. This is in contrast to verification which is testing the product or service against its stated requirements.

If the requirements are an accurate reflection of need, then validation and verification are equivalent. We use frequent and regular feedback to ensure that our understanding of need as described in our backlog is an accurate reflection of the actual need. Validation confirms whether or not we are building the right thing - that is, meeting the need. Verification confirms we built the thing right - satisfying documented requirements.

Levels

Green

Frequent, Regular Feedback, Effectively Used

Product Teams have mature mechanisms that help them to gather feedback from stakeholders. These mechanisms are used on a frequent and regular basis.

The mechanisms are supported by stakeholders who actively provide feedback.

The teams gather feedback and use it to help make decisions about product priorities and about ways of working.

Teams close the loop by informing stakeholders of the actions they have taken in response. feedback received.

Amber

Inconsistent But Well Used Feedback

Product Teams have developed mechanisms that would help them to gather feedback from stakeholders. Mechanisms am used only Infrequently or irregularly.

The mechanisms are poorly supported by stakeholders.

Lack of consistency and stakeholder support means little feedback is received. The teams take care that any feedback received is used to help make decisions.

Teams may not close the loop, failing to keep stakeholders informed of their actions.

Red

Inconsistent, Unused Feedback

Product teams have no developed mechanisms for gathering feedback. Or if there are stated mechanisms they are used only rarely or inconsistently.

Any mechanisms that do exist are not recognised or used by stakeholders.

Little or no feedback is received. Feedback received informally is only exceptionally used to help decision making.

Stakeholders are unaware of any action taken by teams in respect of feedback.