Release management 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.
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.
In the following image, click the + icons to learn more about agile development best practices:
As a Pega Business Architect you may work with business stakeholders to test an application, and then deliver that information back to the development team for further refinement as part of the agile development process.
Check your knowledge with the following interaction: