Using Agile Studio and Agile Workbench

Scrum project management tools include the features commonly used to support the creation and management of Scrum projects. These features include the ability to create and manage products, releases, epics, user stories, tasks, reporting requirements, and individual and team Worklists.

As a Pega BA, the Scrum management tools you could encounter include, but are not limited to, Jira, Trello, Asana, or Pega's very own Agile Studio.

Agile Studio is built on Pega Platform, and is Pega's environment for the Product Owner, Scrum Master, and Business Architects to collaborate on the project plan, manage project scope, and create the user stories that direct application development, all in the context of Scrum.

Built on Constellation, Agile Studio's Portal is very much like that of a Pega application's Web Portal.

In the following image, click the + icons to learn more about a user's Agile Studio Home page:

1. Global navigation: The Global navigation area on the left of the Agile Studio window navigation elements that allow users to quickly access their Home page, Followed items, Planning board, direct messages sent through Pulse, and Notifications, just to name a few.
2. Worklist: The Worklist sections displays a user's work items including status and Urgency.
3. Announcements: Efficiently disseminate important information to project stakeholders using the Announcements section.
4. Pulse: The Pulse Section displays a user's recently received messages from project stakeholders.

App Studio includes several features that improve the process of managing the application development process with scrum.

The Application Profile, accessed from the Overview tab of the App Studio navigation pane, provides an up-to-date view of all the project's work items, features, and their status during application development, as displayed in the following image:

The Application Profile is a collection of information related to the application development process including Processes, Case Types, reports, specifications, participants, collaborators, and actors associated with the project implementation. The Application Profile supports an Analysis and Design approach, a continuous process of end-to-end collaboration between project stakeholders from the Business and IT teams.

Match the numbers to the following image to learn more about the Application Profile:

1. Inventory: The Inventory tab details Persona, Data, and application feature information detailed by Case Type. For each of these elements, Pega BAs and IT team members can review the development status of the element, the expected release, and development complexity. 
2. Feature map: The Feature map tab highlights the application's features. The Feature map tab is broken down by Case Type. Items listed in the Feature map are taken from User Stories created by the BA in Agile Studio and then transferred into App Studio with the Agile Workbench integration.

The Developer Assistant pane helps to organize work by using AI-powered developer aids. Using the Developer Assistant, members of the IT team as well as Pega BAs can quickly and conveniently access all the tasks to be completed from the start of application development until 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.

Match the numbers to the following image to learn about the different tabs in the Developer Assistant pane:

1. Guidance tab: Click the Guidance tab to review the guidelines and best practices for the successful design and implementation of your application. The Guidance tab contains suggestions to improve the app, organized by importance. 
2. Knowledge tab: Click the Knowledge tab to review the content that is relevant to the most recent action, such as an article about an automated Process in the Case Lifecycle.
3. Work tab: Click the Work tab to access Agile Workbench, with feedback and development status of the application's features.
4. Checklists tab: Click the Checklists tab to access to checklists, also called application guides, such as the application Security checklist.

Agile Workbench is a software tool that is accessible in both App Studio and Dev Studio and used by members of the IT team, Pega BAs, and other project stakeholders to track feature development and capture real-time project feedback. By managing application development items directly in Agile Workbench, the feedback loop between the project's IT team, Pega BAs, and the Business team is reduced, making the entire application development process 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. Match the numbers to the following image to learn about Agile Workbench navigation:

1. Developer Assistant icon: Click the Toggle Developer Assistant icon to access the Developer Assistant pane. Agile workbench is in the Work tab of the Developer Assistant pane.
2. Agile Workbench icon: Click the Toggle Agile Workbench icon to directly access Agile Workbench.
3. Create a story, bug, or feedback item: Click the Add icon to create a new story, bug, or feedback item. Additionally, you have the option to create user stories by downloading the Excel template and importing the Excel file with the user story information.
4. View the menu: Click the More icon to view the Application Profile and refresh Agile Workbench.
5. List existing items by feature: Use the List by feature list to select a feature, such as a story, bug, or feedback item, defined in your application. Selection of a feature refreshes the list of work items to show only items associated with the selected feature.
6. View stories, bugs, and feedback: Click Stories, Bugs, or Feedback to view the user stories, bugs, and feedback items in your application. From this view, you can see the name of the bug, its identification number (for example, BUG-1001), the creation date of the bug, and its priority. 
7. Change work item status: Click the icon to the left of the work item to either reject the item, change its status to Doing, or change its status to Done.
8. Use record and screen capture to create a work item: Use the Record video and Capture screen options to capture a video or image of the application, which is attached to a new work item.
9. Work items: Work items become the backlog of development work.

It is to possible associate user stories with features or subfeatures. Features are capabilities that you want your application to support. Subfeatures are features within a feature. When a new Case Type is created in an 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.

As a Pega BA, you can associate the user stories created in Agile Studio with the specific features and subfeatures created in App Studio and visible in the Application Profile and Agile Workbench. As these tasks are worked on and updated in Agile Workbench by the IT team, the information flows back into Agile Studio. This enables both the IT team, Pega BAs, the Scrum Master, the Project Delivery Lead (PDL) and other relevant stakeholders to track development process in accordance to the various scrum rituals like sprints.

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.

When you import an application from a Blueprint file, Pega Platform automatically populates stories in Agile Workbench for each Case Type and Live Data Object. The following image shows the Stories created for the Data Objects associated with the Retail Loan Origination application created using Blueprint:

Status

Every work item has a status of To do, Doing, or Done. You change the status of a work item by dragging the card to the appropriate column or using the Status list on the work item itself.

The integration abilities of Agile Workbench allow customers to leverage the benefits of the Analysis and Design approach while using their existing infrastructure. Agile Workbench integrates 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 Studio is a project management application built on Pega Platform.  Pega Agile Studio presents Pega's methodology for application development in the context of an Agile or Scrum project. Similar to Agile Workbench, teams and other stakeholders use Agile Studio to collaborate on features, plan releases, and execute development tasks.

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: