Relab

Short Tip: It consists in returning to the Conception stage for a new ideation of the process.

What is it?

It consists in returning to the Conception stage for new activities of solution ideation.

This return is necessary whenever it is discovered that the chosen solution fails to meet user and customer needs as initially expected. Therefore, this procedure is usually subsequent to the User and Customer Feedback obtained in the Release Management stage, but it may just as well occur any other time.

Why use it?

It is the essence of the Fail-Fast concept. Even though resources have already been spent, once it is confirmed that the solution fails to meet the user’s needs, it must be discarded. Eventually, this procedure will generate more value than trying to improve a poor solution.

How to use it?

The Relab should be launched by the Product Owner (PIM-Go^© Agile) or the Initiative Leader (PIM-Go^© Hybrid) and should involve the Program Leader.

The degree of formality for the Relab can vary according to each organization; however, it is usually consistent with the Go/No-go system used at the end of the Conception stage.

It is advisable to record the reason for the Relab decision, as well as the insights learned from the process.