Challenge
Tracking application development
Tracking application development
1 Task
20 mins
Scenario
Stakeholders at GoGoRoad want to develop a new roadside assistance application to streamline operations for customer roadside assistance requests. Using the scope for the Minimum Loveable Product (MLP) and incremental releases, stakeholders want to track the current development progress of the Assistance Request Case Type and determine the next highest priority functionality to develop in the future. To facilitate progress tracking, stakeholders and the Pega team have identified and prioritized a product backlog.
To prepare for development, the business architect (BA) must populate the backlog and update the user stories to include the feature, subfeature, owner, and due date. GoGoRoad uses Agile Workbench to manage and prioritize the work. The team created the user stories in an XSLX file specially formatted for Agile Workbench import. Use the XSLX file to import user stories and populate the backlog.
As a new System Architect, your Lead System Architect provides you with a collection of technical documentation links to help you get started.
The following table provides the credentials you need to complete the challenge:
| Role | User name | Password |
|---|---|---|
| Application Developer | author@gogoroad | pega123! |
After completing this challenge, you should be able to:
- Use Agile Workbench to support application development with Pega Platform.
- Import user stories into Agile Workbench.
- Create user stories with acceptance criteria and technical specifications.
- Configure subfeatures within the Application Profile.
Detailed Tasks
1 Estimate and track application development
Read the technical documentation provided to complete the assigned tasks. The technical documentation might have more information than you need.
Acceptance criteria
- The GoGoRoadUserStoriesforDPP Excel workbook was used to populate the Agile workbench backlog.
- The user stories populated from the GoGoRoadUserStoriesforDPP Excel workbook have the necessary information including feature, subfeature, owner, and due date.
- In the Application Profile, in the Assistance Request Feature, there are three new subfeatures to track work related to providing support for Assistance Request customers. The subfeatures are named Notification, Setup, and Support.
- In Agile Workbench, the Setup subfeature in the Assistance Request feature is associated with the Specify Issue User Story. An owner (author@gogoroad) and a Due date is included.
- In Agile Workbench, a new User Story exists that matches the following information:
Field Details Name Add total cost to service information and customer invoice Description As a customer, I want to receive an invoice for the service provided so that I can confirm that I was charged appropriately. Associated feature Assistance Request > Support Owner author@gogoroad Due Any date in the future Complexity Medium Priority Must have Acceptance criteria Service manager can view the service cost when reviewing the completed service. Acceptance criteria Customer receives an email containing the total cost of the service.
Directions
- Download the GoGoRoadUserStoriesforDPP.xlsx Excel workbook and store it locally on your machine:
- In the Pega instance for the challenge, enter the following credentials:
- In the User name field, enter author@gogoroad.
- In the Password field, enter pega123!.
- In App Studio, from Agile Workbench, import the user stories contained in the GoGoRoadUserStoriesforDPP.xlsx Excel workbook.
- From the Application Profile, add new subfeatures to the Assistance Request feature as detailed in the Acceptance criteria.
- In Agile Workbench, update the Specify issue User Story as detailed in the Acceptance criteria.
- In Agile Workbench, create a new User Story as detailed in the Acceptance criteria.
Available in the following mission:
Want to help us improve this content?