Skip to main content

Business outcomes and next MLP

Definition of business value outcomes

After you launch your application, you monitor the business value outcomes and plan the next Minimum Lovable Product (MLP). Business outcomes refer to the benefit (value) the client gets from implementing the application you defined during the Discover phase and implemented using the Day 1 Live Plan.

Gather user feedback and monitor system metrics to ensure your current release is achieving the business outcomes expected. As users develop competency using the application, their insights help you plan your next iteration.

The Day 1 Live Plan and other tools to support the Adopt phase are available on the Pega Express Delivery Resources page. (Please note, you may need to find, click the link, then download, rename or save the tool in order to use it for your project.) For example, the Adopt Phase Plan is a tool that describes the sequence of activities required to gather feedback and prepare for the next MLP.

In the following image, click the + icons to learn more about the activities during the final part of the Adopt phase.

Release Retrospective

A Release Retrospective is a critical event within the Pega Express delivery approach as it captures all the lessons learned and improvements made during the project. The retrospective begins with a team meeting to discuss what worked well and what did not work. Use a template to capture feedback and a communication document to share your findings.

A Release Retrospective is a must-have, as the process uncovers valuable information for the team to discuss. Document findings to make an action plan - improvements needed for future releases. Your Release Retrospective process and action plan mitigate risk and drive continuous improvement.

1. Release Retrospective event

Release Retrospective participants: The entire project team takes part in the retrospective, not just the scrum team. The scrum master facilitates the discussion, captures, and shares feedback with stakeholders.

Location: Virtual/On-site

Duration: This meeting can last 1.5-3 hours depending on the size and complexity of your project.

2. Release Retrospective template

Content: Review the release goals, timeline, budget, major events, and success metrics. A retrospective is an opportunity for the delivery team to identify what they must continue to do because the results are positive, what they must stop doing, and what the team can start doing to improve the process in the next MLP.

You can find the Release Retrospective  template and other tools to support the Adopt phase on the Pega Express Delivery Resources page. (Please note, you may need to find, click the link, then download, rename or save the template in order to use it for your project.)

Note: The Release Retrospective goal is to gather feedback on the delivery experience and identify improvements for the next MLP. It is important to note that throughout the project, the team performs sprint retrospectives and accumulates several useful continuous improvement ideas from those sprints.

In the following image, click the + icons to learn more about the Release Retrospective meeting agenda topics.

Measurement of value outcome

A release going live is not the end of a project; it is often one of many releases. With each deployment, you want to ensure the project achieved the goals and business outcomes as outlined in the Day 1 Live Plan. Measuring business value gives you the opportunity to gather analytics (if available) to track system utilization, and drive continuous improvement for the next MLP.

You can measure value outcomes by:

  • Monitoring system performance
  • Gathering user feedback
  • Measuring business value proactively

Share a Value Impact report with sponsors and decision-makers before you embark on the next MLP. The report helps to celebrate your accomplishments and set the stage for the next release.

A Value Impact report includes:

  • Service-level agreements (SLAs)
  • End-user utilization data
  • Production performance
  • Number of issues identified and solved
  • Feedback from the users
  • Opportunities for continuous improvement

See the Value Impact report template on the Pega Express Delivery Resources page. (Please note, you may need to find, click the link, then download, rename or save the tool in order to use it for your project.)

In the following image, click the + icons to learn more about the Value Impact report.

The next MLP

Before you define your next MLP, review analytics and usage patterns to see if the usage is as expected, or determine change. Usage data helps refine your project roadmap and priorities. The Product Owner determines which Microjourneys™ are appropriate for your next release (MLP2).
A quick transition to the next MLP is important to maintain momentum and make the best use of the available resources. If the delivery team remains the same, plan the next MLP during the Build phase. There might be an opportunity to start the Prepare phase of MLP2 alongside your test activities for MLP1. As your project matures, you can streamline the process by elaborating on user stories in advance.
Check your knowledge with the following interaction.

This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice