Hi - would appreciate some advice on the following:
1. Is it possible to use Pega Project Management Framework (one product) to coordinate requirements / sprints for multiple Pega applications which are built on the same base layer but which are initiated at different times? We are facing the issue of multiple projects from different Business teams, which will result in separate Pega applications but are built on a shared layer. We need some way for the central team to manage requirements and plan sprints across these different projects (e.g. identify any "common requirements which could be built on the base layer). I understand that PMF allowsa single application to be linked to one or more products but does it work the other way around - i.e. multiple applications to a single product?
2. Can user stories / epics be linked to requirements / specifications gathered during DCO sessions? These strike me as the same things...
***Updated by moderator: Maryrita to add Group Tag***
Share this page
Moderation Team has archived post,
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion.
1. According to the PMF user guide, Page 68 states that products can be made reusable, which will allow them to be used by more than one application.
This is done by setting a field on the product to one of three options:
Application: indicates that the product is associated with a full featured application.
Component: indicates that the product is a reusable component that can be used in an application or framework.
Framework: indicates that the product is associated with a framework.
The latter two options are for re-use scenarios
The user guide can be downloaded from the PDN, I found it by a search.
2. PMF User stories are visible in DCO sessions. A user story created in PMF is assigned to a task and pushed to the development system. When the the System Architect creates a rule to implement that user story they link the two together.