Minimum Lovable Product backlog overview
Introduction
In this topic, the position of the MLP backlog in the sales cycle, the use of the backlog, and the details about backlog tasks are explained.
Video
Transcript
Pega provides a prescriptive sales-to-implementation process.
Pega helps the customer through the journey of identifying the right customer-centricity journey and where to start, to development of the first successful project and consecutive projects, and continuous improvement of the Business as Usual to get the maximum value of the solution.
Pega uses the Minimum Lovable Project, or MLP, to define a scoped set of deliverables that lead to an implemented use case that delivers value.
In this scoped set, there are tasks related to infrastructure, application, and organization.
You identify the vision for the customer during the microjourney workshop. The objective is to make the concept of a centralized brain more real by understanding which channels and business objectives to focus on first, using financial, political, technical, and organizational arguments.
Using the microjourney matrix for a specific industry, you take the customer through the various options and use cases and identify an initial microjourney to address. For example, you can focus on cross-selling and upselling bank card products through the web channel.
The use case then goes through the various steps in the sales cycle. In the Opportunity Assessment, it is evaluated against the reality of the current situation at the client. During the Solutions Alignment Workshop, you assess the delivery entry criteria and confirm the scope of the project definition (the MLP) associated with the microjourney.
The MLP backlog is a complete list of activities to complete to implement the most typical MLPs.
The backlog covers all the implementation: Discover, Prepare, Build, and Adopt.
The Discover phase is the first phase. During this phase, your team tries to understand the desired outcomes, confirm the scope of the Minimum Loveable Product, and get ready to start the project.
During the Prepare phase, your team sets the groundwork for the implementation by preparing the organization, infrastructure, and application.
In the Build phase, your team starts to configure Pega Customer Decision Hub™, and use the Next-Best-Action Designer to set up logic, models, and reporting.
Finally, the Adopt phase encompasses the organizational transformation tasks required to allow the users and governance team to get the maximum value from Customer Decision Hub during business as usual (BAU).
The backlog is structured in line with Agile methodology. Each phase is split up into epics, user stories, and tasks. Each task is associated with a sprint. Detailed documentation for each of the activities is provided in separate articles at the task level.
The structure of future MLP backlogs is the same as this first MLP, and certain tasks overlap. However, some tasks may vary for different scopes.
An MLP is scoped alongside the channel and business objective and covers industry specifics where applicable.
The first two MLP backlogs cover inbound digital and outbound. Planned backlogs are for retention, agent-assisted, and Paid Media Manager.
Future MLP backlog development is prioritized based on Pega and customer strategic needs
Backlogs may have overlapping tasks between them, but the outcome of the task can vary. For instance, in the Discover phase for all MLPs, a Solutions Alignment Workshop task is planned. However, the results of the workshop are likely different between an inbound and an outbound project.
Backlogs continuously change and improve, which means that tasks are updated and extended, and the task list and order might change. Change and improvement are expected, as the view of best practices changes, and new functionalities and insights become available.
Each task is assigned to a sprint.
Each task always has primary resources assigned, and sometimes a secondary or tertiary.
This backlog spreadsheet is Pega proprietary content, as mentioned in the Disclaimer in the first tab. Clicking this statement brings you to the more detailed description of the Terms of Use on Pega.com.
You can access delivery phases, epics, and user stories through the navigation pane on the left side of the page.
You can access tasks through a table of links in the main section for a user story. Clicking a task name in the user story brings up the task-level article.
Task-level articles also provide detailed descriptions of:
- How to complete the task in the latest version of Customer Decision Hub (including details on how to use Next-Best-Action Designer or other portals as appropriate),
- Best practice for the specific MLP
- Links to other assets that might be required to complete the task, such as presentations
- Links to other articles or community pages that provide supporting information
This Topic is available in the following Module:
Want to help us improve this content?