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". Pega Scrum adheres to the tenets of Scrum by:

• Accomplishing the tasks that provide the greatest benefit first
• The sprint team is completely autonomous, while management’s focus is to remove obstacles to the team’s progress
• The team decides what it can commit to and is left alone to deliver on the current sprint
• Communication (and collaboration) is incorporated with daily meetings of the team
• The team goal is producing a working software increment within the set time period for a committed set of work (the sprint)

Vision Definition

Suggested Activities

• Develop both long and short term strategies for delivering significant business value in short increments 
• Define functionality that will be delivered, delivery target timelines, and the expected business value

Project Initiation

Suggested Activities

• Scrum team(s) and stakeholders review the benefits, assumptions, risks and costs associated with implementing a Scrum project 
• Scrum team(s) and stakeholders define the standards that will be used to guide this project through completion; standards include, but are not limited to UI, Naming Convention, Code Release, Interfacing, as well as Code Complete/Done Definition standards

Key Deliverables

• Inventory and analyze what artifacts already exist, identifying reuse and leveraging existing artifacts 
• Initiate "Direct Capture of Objectives (DCO)" sessions (prep & review, white board & review, or real-time capture) 
• Enter the DCO session artifacts directly into the Application Profiler 
• Application Profile is started with user stories entered as use cases 
• Application Profile is imported into PMF and product backlog is built-out 
• The test plans are built-out using the Test Management Framework (TMF) 
• Tasks and Resources are then added to the project using PMF 

Additional Information

Introduction to the Business Analyst Portal 
Defining and using Key Performance Indicators in the Business Analyst portal 
About the Direct Capture of Objectives

back to top

Enterprise Planning

Suggested Activities

• Plan, design and construct enterprise architectural components that create the foundation of an application 
• Take into consideration capabilities that will be added in future releases
  Review the Application Profile documentation auto-generated from the Application Profiler

Key Deliverables

• Run the Application Accelerator to establish the application foundation 
• Review the enterprise class structure, organizational structure and reporting structure 
• Update the project plan leveraging PMF 
• Update the test plans leveraging TMF

Additional Information

Designer Studio Overview 
DCO 6.2 - Creating Application Profiles and Discovery Maps 
DCO 6.2 - Using the Application Accelerator 
DCO 6.2 - Using the Application Document Wizard

back to top

Release Implementation

Suggested Activities

• Build out the application on top of the foundation created during Enterprise Planning 
• Complete a preliminary Sprint estimate using the product backlog, defining a small sprint of work from the estimated and prioritized user stories 
• In Sprint planning meeting, team selects the highest priority items from the backlog they can complete in a Sprint based on their velocity 
• Team decides how to break down large user stories into manageable ones 
• Task level details created from resulting user stories 
• Plan for reporting on target metrics and measurements for success

Key Deliverables

• Sprint takes as input the backlog and produces a working increment 
• Team agrees on what must occur for a sprint to be complete 
• Daily Scrum meetings are held to ensure progress is on track, and obstacles are identified and removed 
• Resources complete tasks they committed to for each sprint 
• Complete the Application Profile with the atomic use cases detailed 
• Produce the automated document generation from the Application Profile and update the sizing effort 
• Run the Application Accelerator to establish the application foundation 
• Create the draft flows and draft UI 
• Establish the links between the requirements, cases and rules 
• Update PMF as work progresses 
• Develop TMF testing plan, migration plan and establish standards for executing the plans if they do not yet exist 
• Update the Deployment Plan and Automated/ Systems Integration Test Plan if needed 
• Automated testing, test plans, UAT and integration systems testing are all stories or tasks within the sprint  
• Create, review and continuously update the product backlog in PMF 
• Estimate, define, and run sprints iteratively using the product backlog in PMF 
• Engage TMF to test, report on and ensure rule quality 
• Design review and user experience review with stakeholders 
• End-user training, production deployment and Support guides, as needed 
• Update any requirements and regenerate documentation using the Application Profile 
• Performance, Pre-Flight, PAL, and log file analysis 
• Work iteratively and review work to-date 
• Conduct a "Sprint Review", a formal retrospective at the completion of each sprint

Additional Information

Introduction to Process Definition
Introduction to work parties and work party rules
Standards for rule names, tables, and other objects 
About RuleSet Versions 
How class inheritance works 
How to customize the login screen 
How to customize the favicon for the User and Manager composite portals
Running flow models 
About Automated Testing 
About Standard Management Reports

back to top

Release Retrospective

Suggested Activities

• A sprint review is performed, at the end of each sprint, for the Scrum team itself 
• Using the sprint review feedback, conduct a formal "Release Retrospective" including the team and the stakeholders, (after 1 or more sprints) at the completion of a release 
• Use retrospectives to collect action items, ensuring continuous improvement by adapting processes 
• Revisit target metrics and measurements for success 
• Return to Vision Definition phase for new initiatives or continue Release Implemention with the next sprint

Key Deliverables

• Review reports, what application metrics will be gathered and how follow-up will occur 
• Document and implement sprint retrospective action items 
• Document and implement release retrospective action items 
• Retrospective action items may become prioritized user stories in the product backlog

Additional Information

Using the Report Viewer to define and evolve simple reports
Using the Report Browser to Organize and Manage Reports
About Standard Management Reports
Understanding Monitor Processes reports in the Monitor Activity workspace
Understanding Monitor Assignments reports in the Monitor Activity workspace
Understanding Analyze Performance reports in the Monitor Activity workspace
Understanding Analyze Quality reports in the Monitor Activity workspace
Preparing to create and use interactive charts

back to top