In App Studio, the Application profile provides an up-to-date view of all the work items, features, and their status in your application. The Developer Assistant pane helps to organize work by using AI-powered developer aids. Using the Developer Assistant, you can quickly and conveniently access all the Tasks to be completed before the application goes into production. The developer aids are on four tabs: The Guidance tab, the Knowledge tab, the Work tab, and the Checklists tab.
In the following image, click on the + icons to learn more about the Application profile and the different tabs in the Developer Assistant pane:
Agile Workbench is a software tool used in a Pega Platform™ project for stakeholders and team members to track feature development and capture real-time project feedback. Agile Workbench supports Directly Capture Objectives (DCO) and agile development. By managing application feedback and development status directly in Agile Workbench, application development is more efficient.
The following image shows the Assistant Request and Service features displayed in the Feature map tab, as well as Work items and Bugs. Click the + icons to learn more about Agile Workbench navigation:
Features and subfeatures
You can associate work items with features or subfeatures. Features are capabilities that you want your application to support. Subfeatures are features within a feature. When you create a new Case Type in your application, Pega Platform automatically creates a feature with the same name. For example, you associate the Drop-down missing options bug with the Assistant Request feature because you encountered the bug in the Assistance Request Case Type.
Note: To learn more about managing and documenting the features that you implement, see Managing application inventory.
Work items become the backlog of development work. In Agile Workbench, you create three kinds of work items:
- Stories, or 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. Developers use feedback to guide development on current or future releases.
Note: To learn more about uploading user stories, see Creating stories in bulk. To learn more about documenting a bug in Agile Workbench, see Creating bugs to report feature defects.
Every work item has a status of Status list on the work item itself., , or . You change the status of a work item by dragging the card to the appropriate column or using the
Agile Workbench use case
In a typical scenario using Agile Workbench, you demonstrate or play back each feature of a Case Type with the business stakeholders and product owners. For example, you walk through a Customer refund Case Type to ensure that you have not missed any Steps in your business' customer refund Process. If anyone identifies changes to make during the playback session, you record those as bugs, feedback, or enhancements in Agile Workbench.
For example, the following figure shows an Onboarding Case Type on the left. You notice that the Office list does not have any options to select. In Agile Workbench, you document a bug to be fixed, as shown on the right.
Agile Workbench integration
Agile Workbench interfaces with Agile Studio, a separate Pega Platform tool that expands the Agile Workbench functionality with more robust features for release management, progress tracking, team capacity, and analytics. Agile Workbench also interfaces with external tools such as Jira or CA Agile Central. The integration abilities of Agile Workbench allow customers to leverage the benefits of DCO while using their existing infrastructure.
Check your knowledge with the following interaction: