See the Implementation Approach section in Application Profile documents for details about each methodology.Pegasystems offers two methodologies -- Pega BPM and Pega Scrum -- that you can use to manage application development projects. Both provide an adaptable process framework which is flexible and can be blended without conflict with your organization's methods and project management approach.
The methodologies are designed to work together with Process Commander's Direct Capture of Objectives capabilities and integrate with Pegasystems' Project Management (PMF) and Test Management frameworks.
Methodologies are referenced in Application and Specification rules, Application Express, the Sizing wizard and spreadsheet, and the Application Document Wizard.
See the Implementation Approach section in Application Profile documents for details about each methodology.
Similar in approach to the Rational Unified Process (RUP), the Pega BPM methodology takes an iterative development approach that is structured around four phases: inception, elaboration, construction, and transition. It is not a concrete prescriptive process. It is designed to be flexible so your implementation team can adapt it to any size project.
Specifications in Pega BPM are commonly called use cases.
Pega Scrum is the Scrum Methodology using DCO tools, management frameworks and Pega processes. Scrum is an agile methodology with iterative development accomplished in very short cycles known as "sprints".
Information is gathered and organized using the Project Management Framework (PMF) into a product backlog. PMF reflects the initial functionality that will be delivered, the sprint timelines and the expected business value. PMF integration works best with Scrum so that acceptance criteria mapping can be maintained.
Specifications in Pega Scrum are commonly called user stories.
Definitions