Bulk actions in Agile Workbench
Agile Workbench supports actions for creating and exporting stories in bulk. By importing raw data instead of manually creating stories, you can involve stakeholders sooner and size your project more quickly.
For example, you can use a story template to define and review with stakeholders the initial scope of work for your project. After you import the story template to Agile Workbench, you can work with your development team to refine the project scope by capturing feature gaps in new stories and providing more information, such as a due date or an attachment.
As a best practice, import one story template before you size your project, and then periodically export story data to update your stakeholders throughout the development life cycle.
| Name | Description | Complexity | Priority | Acceptance criteria |
|---|---|---|---|---|
| Authorize purchase orders | Users must provide a valid account number and corresponding pin number when submitting a purchase order. | Medium | Must have | Error message indicates which input value is incorrect, Account is locked after 3 failed attempts |
| Secure data | All sensitive personal information is encrypted, stored, and accessed in compliance with regional laws and regulations. | High | Must have | Security team approves test plan
|
| Self-service account management | Users have the option to unlock their account instead of calling customer service. | Low | Nice to have |
Example data in a story template
Story details in Agile Workbench
Previous topic DCO 3.1 - Using the Enterprise Application Accelerator Next topic Interactive tasks in an application guide