Article

The Pega Delivery Stages

The Pega Delivery methodology is segmented into three stages.

Thumbnail

 

Prepare

Projects typically have various logistics that are completed prior to starting the actual development process. These logistics are grouped under the Prepare phase.

This includes defining key activities, such as identifying dependencies, milestones, training and briefing the team for co-production, provisioning your development environment to work in, and gathering any background information about current processes and data, before formally starting the project with a kickoff meeting to clarify the scope and deliverables to everyone, refine two sprints worth of work using Pega’s Direct Capture of Objectives capability and tools, establish your development standards, and start your Multi-Level Governance meetings.

In this phase we also typically review the overall User Experience (UX) to ensure the agreed scope can deliver a system that will delight the user.

Before starting this phase, you should have completed your Case Type Backlogand Sizing Tool Template and established your Minimum Loveable Product (MLP). This is normally done during the project sales process with either Pega or one of its partner companies.

 

Sprint 1..N – Build / Test / Review / Refine

In this phase, you will follow an Agile iterative methodology to plan, build, and test in a mini-development cycle, called a Sprint. Pega technology is highly aligned to Scrum, the most popular Agile framework, although other Agile frameworks can also be used. The ‘Plan’ step chooses a Sprint’s worth of work from your Sprint Backlog, which is then allocated to your project team to build. Your Product Owner is involved to shape the delivery, and testers are embedded within the Sprint team to Continuously Test. The output of the Sprint may be part or all of a Journey that can be demonstrated and independently tested. The Sprint may or may not go live by itself – typically several sprints are combined into one deliverable release, though it depends on the nature of what is being built.

During Build, take advantage of the unique Pega technology to accelerate delivery, such as Pega Express to start development rapidly, Pega Guardrail reporting to spot problems before they hit testing, and PegaUnit to perform rapid regression tests.

DevOps may be extended to the new Sprint software if it is in use.

Also during the Sprint, any changes to the backlog are refined and an additional sprints worth of work is refined using Pega Direct Capture of Objectives.

Quality during the delivery is assured by the use of a Definition of Done that enforces unit testing, UX and UI reviews and show and tells, to ensure we test as early as possible.

 

 

Go Live

Some projects require special testing that is unique to the customer or industry, for example, Federal Government or Pharma. This phase carries out your industry specific testing, then deploys the software to production with any required post live support and transition to business as usual.

This may be just one of many go lives in a project, so it may be conducted several times based on the cadence of release plans.

After a go live, conduct a release retrospective to learn what can be done better next time.

Published May 7, 2018 — Updated March 14, 2019


93% found this useful

Related Content

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.