Managing Application Development using agile workbench in PEGA -PART #1

In order to track the progress and feedback of application development, stakeholders and team members use Agile workbench. It supports DCO or Direct Capturing of Objectives which means, instead of creating mountains of requirements documents, business people and IT use a shared visual model that can automatically generate the documentation you need. In Agile Workbench, we can create three kinds of work items:

• User stories to describe business requirements. The majority of development work consists of user stories. To save time, upload user stories from Excel.
• Bugs to document feature defects. Developers typically address major bugs before minor ones.
• Feedback items to record enhancement requests identified during playback sessions.

Application profile

The Application profile provides an up-to-date view of the work items, features, and their status in your application. It is possible to associate work items with features or sub features (feature within a feature).Every work item has a status of To do, Doing, or Done. This is known as Status.

In order to expand the capability, agile work bench interfaces/integrated with agile studio .It provides more robust features for release management, progress tracking, team capacity, and analytics.

Release Management with PEGA

We all have heard about DevOps right? What is it all about? It means developing quality applications in agile method. DevOps methodology drives innovation and operates on three components: people, process, technology.

Continous Integration and Delivery(CI/CD)

With continuous integration, application developers frequently check in changes to the source environment and use an automated build process to verify these changes automatically. You should add ‘ready to share’ and ‘integrate changes’ steps as part of your pipeline to ensure that all the necessary critical tests are run before integrating and publishing changes to a development repository.

Continous Integration

With continuous integration, application developers frequently check in changes to the source environment and use an automated build process to verify these changes automatically. You should add ‘ready to share’ and ‘integrate changes’ steps as part of your pipeline to ensure that all the necessary critical tests are run before integrating and publishing changes to a development repository.

Continuous Delivery

testing. The changes are deployed to a staging environment for further testing to ensure that the application is ready to deploy on the production system.

The Pega CI/CD Pipeline

The following image depicts the high-level overview of the Pega CI/CD pipeline. Different questions are asked during every stage of the pipeline. These questions fall into two categories:

• Developer-centric questions
• Customer-centric questions

We can start our DevOps journey by using the Deployment Manager and integrate third-party tools at a later time. Pega Platform includes support for open DevOps integration using popular third-party tools such as Jenkins and Microsoft Azure DevOps by providing an open platform with all the necessary hooks and services. With open DevOps integration, we can build a deployment pipeline by using third-party tools to automate branching.