Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Pega Express Methodology FAQ

Updated on February 5, 2020

Here is a list of frequently asked questions for the Pega ExpressTM Methodology:

Methodology Materials/Support

What is Pega Express?
Pega Express Methodology is a method that focuses on delivering Journeys that cut across departmental and channel boundaries. Build a process once, then deploy the same process across multiple channels (Contact Center, web, mobile, etc.) with Pega managing the technical complexities. Journeys are deployed to live either singly or in small groups.

Who can I contact if I have questions regarding Pega Express methodology services & materials?
If you have any questions regarding Pega Express materials & services, please contact us at [email protected]

Where can I find an overview of information on the Pega Express Methodology?
You can find the high-level overview of the Pega Express Methodology in our 'Deliver your Pega Project' main landing page here
Also, you can find the detailed descriptions of each Pega Express Methodology stage in our 'The Pega Delivery Stages' article here

Where can I find a copy of the Readiness Checklist template?
You can find a copy of the Readiness Checklist template in Excel here & in Word here.  

Where can I find a copy of the latest Case Type Backlog?
You can find a copy of the latest Case Type Backlog here

Where can I find the latest updates to the Pega Express Methodology?
You can find the latest updates here

When do I create a Case Type Backlog, Day 1 Live Plan and Scrum Sizing etc?
You can find a quick view of when to create specific artifacts here. We acknowledge that every project is different and the exact order and timing of when you use specific tools or run a design sprint can vary. Our guide is based on what we have found works best and is the most logical sequence of events.


Case Type Backlog

When should the Case Type Backlog be created?
The Case Type Backlog’s first intent is to assist during the initial Discover process by providing the potential client with early indications of the size and scope of the initial Minimal Loveable Product (MLP) release. Therefore, it is developed as early during the Discover phase when the information it requires can be obtained.

Who is responsible for creating the Case Type Backlog?
If there is a new license sale, the Solution Consultant is responsible for creating the Case Type Backlog. This is then handed over to the PL as part of the Sales to Services Transition.
If there is not a new license sale, i.e. radiation at an existing client, the PL is responsible for creating the Case Type Backlog (most likely delegated to an EL, LBA, etc).
In both the above cases, sales and services may collaborate for the success of the sale/client success.
In all cases, the PL is always responsible for the project factors tab and reviewing the CTB. That is, the PL owns the overall sizing.

How long does it take to produce a Case Type Backlog?
Most of the time involved in producing a Case Type Backlog is in identifying journeys, micro-journeys, business scenarios, and case types. These can come from conversations that are brief or long … few or many. So it’s difficult to give a simple answer. 
Experience is showing, though, that on average the entire process takes somewhere around 5 – 6 hours. But do note that your mileage may vary.

When do we use the Case Type Backlog, and when do we use the Sizing Tool?
The Case Type Backlog is created early in the Discover stage for full implementations.
The Sizing Tool is used later in the Discover stage – when the client needs an exact price - for full implementations.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us