Skip to main content

Estimating and tracking application development

1 Task

25 mins

Pega Platform '24.2
Visible to: All users
Beginner
Pega Platform '24.2
Low-Code App Development
English

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.

Before beginning work on the Roadside Assistance application, stakeholders requested an estimate of the project size and scope based on the Case Types included in the GoGoRoad application to date and the user stories included in the backlog. The estimate considers staffing models and provides an approximate timeframe for application delivery.

Your Lead System Architect has assigned you the task of assigning releases to the Channels and Data Objects that are associated with the Assistance Request and Service Case Types. Once the release versions are assigned, you are to use the Estimator tool to calculate the sizing estimate for the MLP 1 release.

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!

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

Detailed Tasks

1 Estimate and track application development

Estimating and tracking application development Journey Map.

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, each of the new Assistance Request subfeatures, Notification, Setup, and Support, are associated with the Specify Issue User Story. An owner (author@gogoroad) and a Due date is included with each of the new subfeatures.
  • 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.
  • In the Assistance Request Case Type, MLP releases are assigned to the Channels. The Web Portal Channel is assigned the release of MLP1. All other Channels are assigned the release MLP2.
  • In the Assistance Request Case Type,  MLP releases, complexity, and other information is assigned to the data objects based on the following information:
    Case Type Stage Data object Data source Read Write Existing API Release Complexity Mark as done
    Assistance Request Create Service address Pega       MLP 1 Low  
    Assistance Request Create Vehicle information Pega       MLP 1 Low  
    Assistance Request Create Payment information Pega     x MLP 1 High  
    Assistance Request Service Service provider Pega x   x MLP 1 Low  
    Assistance Request Resolution Services offered Pega       MLP 1 Medium  
  • The Estimator tool was used to provide estimates for the work associated with MLP1 release of the Assistance Request Case Type. Work should be estimated using various combinations of selections for the Delivery list, Number of teams field, the Scrum Maturity list, the Staffing model list, the Environment list, Organization complexity list, and the Data import effort list.

Directions

  1. Download the GoGoRoadUserStoriesforDPP.xlsx Excel workbook and store it locally on your machine:

    GoGoRoadUserStoriesforDPP.xlsx

  2. In the Pega instance for the challenge, enter the following credentials:
    1. In the User name field, enter author@gogoroad.
    2. In the Password field, enter pega123!.
  3. In App Studio, from Agile Workbench, import the user stories contained in the GoGoRoadUserStoriesforDPP.xlsx Excel workbook.
  4. From the Application Profile, add a new subfeatures to the Assistance Request feature as detailed in the Acceptance criteria.
  5. In Agile Workbench, update the Specify issue User Story as detailed in the Acceptance criteria.
  6. In Agile Workbench, create a new User Story as detailed in the Acceptance criteria.
  7. For the Assistance Request Case Type, assign MLP releases for the Channels as detailed in the Acceptance criteria.
  8. For the Assistance Request Case Type, assign MLP releases and other information for the data objects as detailed in the Acceptance criteria.
  9. Use App Studio's Estimator to provide an estimate for the work associated with MLP1 release of the Assistance Request Case Type.

Confirm your work

Run the Estimator tool to calculate the sizing estimate for the MLP1 release.

Your finished product should look similar to the following image: 

Estimating and tracking application development

To see a suggested solution, initialize an instance in the Using Insights challenge.



Available in the following mission:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice