29. #AGILE Workbench in #PEGA || #userstories #features #estimations || #APPStudio

Summary

In this video, the presenter explores the features and functionalities of Azure Workbench in Pega App Studio. They explain how to create and manage user stories, defects, and feedback, while demonstrating the process of importing user stories from templates. The video also covers the concept of features and sub-features, and how they relate to user stories. Additionally, the presenter explains the process of assigning features to releases, managing complexities, and estimating efforts for project delivery. With practical tips and a detailed walkthrough, this video is a helpful guide for using Agile Workbench effectively in Pega App Studio.

Takeaways

• 😀 Azure Workbench is a tool available in Pega App Studio used to manage agile development tasks, such as user stories, defects, and feedback.
• 😀 The key features in Azure Workbench include the ability to create, import, and manage user stories and defects, with additional options for feedback.
• 😀 User stories represent the work that needs to be done against a feature, while defects address issues in incomplete or incorrect user stories.
• 😀 Feedback captures new business requirements or changes that arise after the initial user story has been created, unlike defects.
• 😀 Pega App Studio allows importing user stories via Excel templates to speed up the process when dealing with large numbers of tasks.
• 😀 Each user story can be linked to a specific feature, with features representing the capabilities an application should support (e.g., case types).
• 😀 Minimum Level Product (MLP) planning helps categorize features for specific releases, and each feature is mapped to its respective MLP phase.
• 😀 Azure Workbench allows developers to assign priority, complexity, due dates, and owner for each user story, making task management more efficient.
• 😀 Estimation tools in Azure Workbench help calculate how many resources and hours are needed to complete a feature, based on the team size and environment.
• 😀 The platform also provides features to upload supporting documents, videos, and attachments for developers and testers to better understand the user stories and features.

Q & A

What is Azure Workbench in Pega App Studio?

Azure Workbench is a tool within Pega App Studio that allows users to manage user stories, defects, and feedback, helping teams plan, track, and estimate their project work efficiently.

What types of work items can be created in Agile Workbench?

In Agile Workbench, you can create three types of work items: Stories (tasks to be done for a feature), Defects (issues or bugs in incomplete user stories), and Feedback (additional business requirements not captured initially).

How can multiple user stories be added at once in Agile Workbench?

Multiple user stories can be added at once by importing an Excel template provided by Agile Workbench. The template includes required fields such as name, description, associated feature, complexity, priority, and acceptance criteria.

What is the difference between a feature and a sub-feature in Pega?

A feature represents a primary capability or case type within the application, while a sub-feature is a component or smaller part of that main feature. Stories can be associated with either to define work granularity.

How are user stories associated with features and sub-features?

User stories are mapped to features or sub-features by selecting the relevant feature or sub-feature in Agile Workbench and saving the association. This ensures the work item is linked to the correct component of the application.

What is MLP and why is it important in project planning?

MLP stands for Minimum Lovable Product (or Minimum Level Product). It is used to categorize which features should be included in specific releases, allowing teams to plan incrementally rather than building all features at once.

How does Agile Workbench help in estimating project effort?

Agile Workbench provides an estimator tab where users can input team size, delivery type, team maturity, staffing model, and environment. Based on MLPs and feature complexity, it calculates the estimated hours and resources required for development.

What types of attachments and supporting information can be added to work items?

Users can attach documents, screenshots, or record videos to provide additional context or prototypes for features. Comments can also be added for team collaboration and clarification.

How can the priority and complexity of a user story be set?

Priority can be set to indicate the urgency of the work (e.g., must-have, future release), and complexity is chosen based on the story's details. Both are selected in Agile Workbench when creating or editing a story.

How does Agile Workbench support collaboration among team members?

Agile Workbench allows assigning stories to specific developers, adding comments, posting attachments, and recording supporting videos. This ensures clear communication and alignment across developers, BAs, and QA teams.

What are the benefits of using Agile Workbench before starting a project build?

Using Agile Workbench before project build helps plan the case lifecycle, define features and sub-features, associate stories to releases (MLPs), estimate resources and effort, and provide all supporting information for smooth execution.