Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Creating stories

Updated on April 5, 2022

Speed up your application development by providing your team with specific information about the features that they design. By implementing stories, you can also track and manage the workload of your team more effectively.

When you create stories, you define the functional requirements for features, estimate the completion time, and assign the priority level.
Before you begin: To provide context for the team and to speed up feature development through videos or screenshots, log in to your application in Google Chrome by using the HTTPS protocol.
  1. In the header of App Studio, click the Agile Workbench icon.
  2. Optional: To record videos or take screenshots, in the Agile Workbench tool, add the Pega Screen and Video Capture extension to your browser, by clicking Install the plugin at the bottom of the tool, and then following the instructions in Google Chrome.
  3. In the header of the Agile Workbench tool, click Create work itemCreate Story.
  4. In the Name field, enter text that summarizes what users can do with the new functionality.
  5. In the Description field, enter text that describes the new functionality to implement, the key stakeholders to involve, and the relevant business value.
  6. In the Associated feature list, select a feature that relates to the story.
  7. In the Due field, select a deadline for story resolution.
  8. Optional: To speed up story resolution, in the Owner field, assign the story to a user by entering a user ID.
  9. In the Complexity list, select the level of effort to complete the story.
  10. In the Priority field, select the relative importance of the story.
    During triaging, the development team uses this field to determine when to implement the story relative to other items in the product backlog.
  11. Optional: To add an attachment, click Add attachment, and then select the attachment type:
    Record a video
    1. On the Attachments menu, click Record video.
    2. In the Share your screen window, select a screen that you want to record, and then begin the recording by clicking Share.
    3. In the timer window, stop the recording by clicking Stop.
    Take a screenshot
    1. On the Attachments menu, click Capture screen.
    2. Drag the target pointer onto the screen area that relates to the story.
    3. In the text field below the target pointer, enter additional information about the story, and then click Capture screen.
    4. In the Share your entire screen window, select a screen that you want to capture, and then click Share.
    Attach a file
    1. On the Attachments menu, click Attach files.
    2. In the Attach file(s) window, select the files that you want to upload, and then click Attach.
    Attach a URL
    1. On the Attachments menu, click Attach URL.
    2. In the Attach a link window, in the Name field, enter a descriptive name for the URL.
    3. In the URL field, enter the URL.
    4. In the Attachment category list, select URL.
    5. Click Submit.
  12. In the Acceptance criteria section, click Add new criteria, and then enter metrics or constraints that the team must meet before they can resolve the story.
  13. Click Save.
What to do next: Discuss the story with a development team. For more information, see Collaborating with development teams.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us