Pega Express delivery
Pega Express™ is a light, design-focused delivery approach that uses the low-code experience of Pega Platform™, best practices, and scrum to deliver meaningful outcomes quickly. The design-thinking technique is used to break the customer journeys into smaller, more manageable pieces called Microjourneys™ (one of the three pillars of Pega express: Microjourneys, personas, and data). Users can monitor the health of the application with the Application Quality Dashboard. For more information on monitoring application health, see the Predictive Diagnostic Cloud page on Pega Community.
Pega Express
The following table provides information on the best practices and tools on which Pega Express is built:
| Business Outcomes - value | ||
| Design Thinking | Direct Capture of Objectives (DCO) | Pega Express |
| Design thinking is a human-centered mindset to identify, innovate, and creatively solve problems throughout the project, building on empathy to create great experiences and realize the business outcomes through MicrojourneysTM | DCO is the Pega Express discipline used to design solutions with clients, fostering ongoing collaboration and feedback between IT and business stakeholders and enable coproduction | Pega Express is based on Agile and Scrum delivering prioritized Microjourneys in increments known as Minimum Lovable Product (MLP) that provide our clients speed to value within 90 days or less. Once delivered, the team can focus on the next MLP. |
| Technical Outcomes - value | ||
| Low-code / No-Code Configuration | DevOps Pipelines and Testing | Application Health Monitoring |
| Pega’s low-code / no-code configuration design allows you to define customer microjourneys and create tailored intuitive applications to deliver business outcomes quickly. | Pega’s DevOps pipeline and automated test suite enables teams to test early, often, and more efficiently than through manual testing alone so that issues can be fixed as early as possible. | Pega’s Application Quality and Predictive capabilities automatically monitor health of your solution and notify you of potential risk with a recommended guardrail score of 90 and above |
Pega Express is divided into four phases: Discover, Prepare, Build, and Adopt. The following table demonstrates the benefits of the four phases.
| Discover | Design Thinking for fantastic experiences. This phase is design focused; it leverages design thinking through design sprints. |
| Prepare | Setting up for success. This phase is quick, light and guides business experts. |
| Build | Rapid configuration of business capabilities. This phase emphasizes using the low-code platform to configure the application based on the design. |
| Adopt | Go live and achieve your goals. This phase talks about balancing business benefits, efforts and user experience. |
Pega Express helps review the progress against the Day 1 Live Plan created during the Discover phase.
Points to consider
As a lead system architect (LSA), Pega Express helps with:
- Designing the MLP and effort sizing.
- Document decisions and actions.
- Adapting Application design best practices.
- Adapting Case design and coding best practices.
- Automating the unit and scenario testing best practice.
- Backlog prioritization, grooming, and planning.
- Easy and faster code deployment into a production environment.
For more information about Pega Express, see the following Pega Academy and Pega Community content:
Direct Capture of Objectives
Gathering, classifying, categorizing, and maintaining requirements is an exhaustive process. Direct Capture of Objectives (DCO), an integral part of Pega Express, helps capture requirements and specifications, organize the artifacts, and manage them throughout the application development. DCO is a methodology that lets business people and IT work together using Word, Excel, and Visio to generate the necessary documentation. DCO also helps in capturing change requirements and versions of the documents. For applications that are not DCO enabled, the DCO Enablement wizard quickly enables applications to leverage DCO capabilities within those applications.
DCO is extremely important as part of the application development process because it facilitates collaboration between business and IT through the following features:
- Information gathering
- Coupled iterative methodology
- Early visualization
- Effort estimation
- Centralized data
- Centralized repository of linked artifacts
- Real-time documentation
- Transparent software development process
DCO helps an LSA with:
- Understanding the scope of the application.
- Creating a minimum lovable product through an iterative approach.
- Knowing the external systems and integration points.
- Better planning and tracking the deliverables,
- Minimal delivery gaps.
For more information about DCO, see the following Pega Academy and Pega Community content.
Sizing sheet
A sizing sheet helps development teams to quickly determine the size of the project. Users can use an empty sheet or generate a sheet in App Studio. If generated, App Studio populates the gathered requirements. Otherwise, users enter the details manually by navigating through the available tabs. This information helps establish the project schedules, resource planning, and allocation across the sprints. The collected data and calculated efforts can be manually adjusted.
Depending on the project methodology, Iterative Waterfall or scrum-based sizing sheets are available in the App Studio application overview. The sizing sheet uses information from the gathered requirements to accurately estimate the required effort.
For an LSA, the sizing sheet helps:
- Manage sprints better.
- Allocate tasks and resources for each sprint.
- Track milestones and delivery.
- Manage the backlog.
This Topic is available in the following Module:
Want to help us improve this content?