Skip to main content


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

Creating stories in bulk

Updated on January 14, 2022

Save time during your application development by creating stories in bulk. By incorporating stories, you provide traceability for the process of delivering an application and link functional requirements with traceable work items.

For example, you can create a template with of stories that are common to your development process, and then import the stories from the template, instead of creating similar stories multiple times. You can also communicate with your stakeholders offline to prepare a story template, and then conveniently upload the stories into Agile Workbench.
Before you begin: Ensure that your application is not integrated with Pega Agile Studio or other project management applications.
  1. Populating story templates

    Automate the creation of stories by populating the columns in a story template with functional requirements. By implementing stories, you can track, manage, and communicate development of your projects. For example, you can define which stories contain features that are essential to your application, so that your development team can prioritize their work.

  2. Importing story templates

    Track and manage development of your application by importing stories into Agile Workbench. By importing stories into your project you can ensure that your development team correctly prioritizes work, for example, by focusing on stories with a high priority.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us