Table of Contents

Agree on the Outcome

The first part of the Discover phase identifies the problem that we are trying to solve in graphical terms with measurable results. This is achieved through identifying the relevant microjourneys™ that deliver the most business value. These microjourneys are represented as a service blueprint, which starts to identify the key constructs that are required to build a Pega application; they include the case types, features, personas and channels, data entities and interfaces. These are captured directly in App Studio. For those not on the latest Pega version and who want to generate a sizing estimate, you can use the Case Type Backlog.

The tasks and relevant templates, tools and help articles are:

Key Tasks

Resource Links:

 Understand desired business outcomes and benefits

 

✓ Further identify the opportunity

Catalyst course

 Identify and create a shortlist of MLP candidate micro-journeys  

 Identify expected user base and volumes

 

 Create Service Blueprint based on micro-journey shortlist

 

 Identify if an existing Pega app is a good fit

Product Case Type Backlogs

✓ Capture the key Information

Case Type Backlog Template

How to create a case type backlog

Suggest Edit

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.