Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Rachana Jayasimha (RachanaJ16772981)
Gmail

Gmail
AU
RachanaJ16772981 Member since 2023 5 posts
Gmail
Posted: Oct 23, 2017
Last activity: Nov 20, 2018
Posted: 23 Oct 2017 1:55 EDT
Last activity: 20 Nov 2018 23:27 EST
Closed
Solved

DCO Requirements Vs User Stories of Agile Work Bench

Hi,

Can anyone let me know if there is any link between the DCO Requirements &Specificiations and the User Stories & Bugs of Agile Workbench.

Regards,

Rachana J

***Updated by moderator: Lochan to update Categories***

To see attachments, please log in.
Project Delivery

Accepted Solution

Posted: 7 years ago
Posted: 23 Oct 2017 7:45 EDT
Vijaya Kumar Bandaru (VijayBandaru) Sr. Product Manager- Agile Studio
Pegasystems Inc.
IN

There is no relationship between those two. They are two different ways of managing the work. the Agile Workbench is more of an Agile way of handling requirements in terms of Feedback, User Story and Bugs associating to features of the application. 

To see attachments, please log in.
Posted: 6 years ago
Posted: 2 Jul 2018 21:33 EDT
Abhijeet Srivastava (augustabhijeet)
Cognitonic Systems
Lead Solutions Consultant
Cognitonic Systems
AU

Hi Vijay

So how do we manage the user stories captured in DCO through the Agile workbench? If stories have been captured in DCO should they be re-entered into the agile workbench to manage them during the sprints?

As there is a user story category within the DCO tool as well, shouldn't they be directly visible in the agile workbench as well?

To see attachments, please log in.
Posted: 6 years ago
Posted: 20 Nov 2018 23:27 EST
Shantan Vemuganti (Titan2k15)
Areteans
Associate Director- Solutions consulting
Areteans
GB

There is no way to link the requirements or specifications added in the DCO to AWB.

I guess Pega is trying to move away from the traditional DCO process to a more Agile way. To support this, they have allowed for creation of Features instead of requirements and specifications. These features can be directly link to the user stories in AWB. This is more in line with how you create Requirement Artifiacts in Agile: EPICS(Can be interchanged with Features)-->User Stories-->Acceptance Criteria

To see attachments, please log in.

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

Pega Collaboration Center 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