Skip to main content

Agile development best practices

Agile development supports a customer's need to update their production environment as business needs change. Incorporating agile methodology in application development enables frequent changes and ensures that those changes work as expected.

Pega Platform™ includes best practices for agile development, including:

  • Real-time updates: frequent development iterations that are small in scope
  • Testing: continuous application validation to identify and address issues early
  • Branches: concurrent team development environment to maximize productivity

An agile development approach provides continuous, iterative application development based on small-scope business requirements. When business requirements change, you can make smaller, more frequent updates. For example, you add a chatbot based on feedback or fix a bug in the user interface.

Note: To learn more about adding agile items such as feedback, user stories, or bugs, see Agile Workbench


DevOps tightens the integration between development teams, test teams, and post-go-live support teams to take the agile process further. DevOps teams work across the application life cycle to provide a more automated build, streamlining how you configure, validate, deploy, and deliver an application.  

Note: To learn more, see DevOps.

In the following image, click the + icons to learn more about agile development best practices:

Pega Express best practices

Pega Express™ delivery is an agile methodology tailored to application development using Pega Platform. It consists of four phases designed to support agile best practices in low-code application development.

Agile best practice examples by Pega Express phase include:

  • Discover: Define your business outcomes and create a Day 1 Go-Live plan
  • Prepare: Host a design sprint with end users to build a working prototype
  • Build: Build your application based on user stories in the backlog
  • Adopt: Once your application goes live, conduct a release retrospective
Tip:  To learn more about how Pega supports agile and scrum, see Scrum with Pega Express: Using Scrum to maximum effect with Pega Express. To facilitate using the Pega Express delivery methodology and to access downloadable resources to support your agile project, refer to the Pega Express toolkit. Team members pursuing a badge may wish to complete the Pega Express delivery mission in Pega Academy.

CI/CD best practices

A CI/CD pipeline models the two key stages of software delivery: continuous integration and continuous delivery.

Continuous integration

In the continuous integration stage, developers continuously validate and merge Branches into a target application.

During continuous integration, maintain these best practices:

  • Test early and often: for example, identify issues early by running Pega unit tests and critical integration tests before packaging the application. If tests fail, stop the release pipeline until the issue is fixed.
  • Automate: for example, trigger merges and builds by using the Deployment Manager. 
  • Update Rules: for example, keep the product Rule, Rule-Admin-Product, referenced in an application pipeline, up-to-date.
  • Maintain version history: Publish the exported application archives into a repository to maintain a version history of deployable applications.

Continuous delivery

In the continuous delivery stage, the target application is packaged and moved through progressive stages in the pipeline. After application changes have moved through testing cycles (Pega unit, regression, performance, and load testing), you deploy application packages to a production system. In Pega Platform, you can deploy changes manually or automatically.

Follow these continuous delivery best practices to ensure application quality:

  • Create test environments: Use Docker or a similar tool to create test environments for user acceptance tests (UAT) and exploratory tests.
  • Conduct regression tests: Create a wide variety of regression tests through the user interface and the service layer.
  • Use version control: Define target Ruleset versions for production deployment.
  • Employ a rollback strategy: If a test fails, roll back the latest import.
  • Document: If all the tests pass, annotate the application package to indicate that it is ready to be deployed. Deployment can be performed manually or automatically.
Note:  To learn more about using the systems that support the CI/CD pipeline, see Working with deployment pipelines.

Check your knowledge with the following interaction:

This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

100% found this content useful

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice