Which two assets are assigned to a release and used to estimate the project scope and duration? (Choose Two)

In the Pega Express™ delivery methodology, project scope and duration for a release are primarily estimated based on the key building blocks of the application. A Case Type represents a Microjourney®, which is the fundamental unit of work and business value delivered in a release. The effort to build the application is estimated by sizing each Case Type. This sizing process considers several factors, including the complexity and number of Data Objects required to support the Case Type's data model. Therefore, Case Types and Data Objects are the two core assets used to define the scope and estimate the effort for a release.

B. Processes: Processes are components within a Case Type. While their complexity contributes to the overall estimate, scoping and high-level estimation for a release are performed at the Case Type level, not the individual process level.

D. Work Groups: Work Groups are organizational units used for routing assignments to users. They are part of the operational design, not assets that define the functional scope or development effort of a release.

E. Channels: Channels (e.g., web, mobile) are the interfaces through which users interact with Case Types. While channel requirements are part of the scope, the core functional asset being estimated is the Case Type itself.

1. Pega Academy

Pega Express Delivery

"Sizing your application" module. This module explicitly states

"In Pega Express

you estimate the effort to build your application by sizing each case type." It further details that the sizing of a case type is based on factors including "the number of... data objects." This directly links both Case Types and Data Objects to the estimation process.

2. Pega Documentation

"Pega Express delivery

" Section: "Discover phase." The documentation for the Discover phase states

"The team defines the project scope and captures the high-level case types and data objects in the project backlog." This confirms that Case Types and Data Objects are the primary assets identified to define the scope at the beginning of a project.

3. Pega Documentation

"Estimating project effort

" Section: "Sizing case types." This section details the best practice of sizing. It reads

"You size each case type by assigning a t-shirt size (XS

S

M

L

XL) to the case type based on the number of user views

personas

and data objects." This reinforces that Data Objects are a direct input to the estimation of a Case Type's complexity and effort.