01 - Introduction to Pega Methods Flashcards
(19 cards)
Why are Agile Methods better suited to projects where requirements change?
Development is in shorter intervals
How does delivery time impact value derived from a system?
- What is valuable to the business at the beginning may not be at the end
- Actual value delivered to the business dimishes through time as requirements change
What are the benefits of shorter release cycles?
- Maximize value gained by the project
- Allows users to gauge value of features requested in first iteration
- Provides higher quality requirements for subsequent releases
What are some of the problems with longer release cycles?
- Increase risk that new requirements will be added
- Lost value
Is Pega BPM a concrete prescriptive process?
No
It is an adaptable framework
What are the phases in Pega BPM lifecycle?
- Inception
- Elaboration
- Construction
- Transition
What two activities supplement Pega BPM phases?
- Project Initiation
- Go-Live
What artifacts are produced in Inception (Sizing) Phase
- Business Objectives
- Requirements
- High Level Specifications
- Work Types
- High Level Process Model
- Application Profile
What artifacts are produced in Elaboration (Defining) Phase?
- Specification Details
- Requirement Details
- Business Draft Flow Details
- Draft Screens
- Project Document
What artifacts are produced in Construction (Building) Phase of Pega BPM?
- System Behavior
- Screen Implementation
- External Interfaces
- Application Document
What artifacts are produced in Transition (Delivering) Phase of Pega BPM?
- QA Test Results
- UA Test Results
- Move to Production
What are the key Project Initiation Activites?
- Define which sliver to begin with
- Demo product features
- Conduct knowledge transfer
What are the key Inception Phase activities?
- Define the scope of the program, project and sliver
- Capture business requirements
- Organize requirements into projects
- Break projects into slivers
- Identify process improvements
- Capture High Level requirements, use cases and work types for sliver
- Estimate Effort
What are the key Elaboration Phase activities?
- Build out the foundation of the proposed application
- Refine requirements, use cases, and work types
- Conduct DCO Sessions to create draft flows and draft UI
- Establish rule links
- Develop a testing plan, migration plan, and establish standards
What are the key Construction Phase activities?
- Assign application configuration tasks using an iterative model
- Unit test each component
- Run application test scripts and begin the system test process
What are the key Transition Phase activities?
- Complete system test process to ensure application is acceptable to stakeholders and business users
- Ensure solution is maintainable by IT (including support)
What are the key Go-Live activities?
- Deploy final release candidate
- Maintain application with enhancements, fixes, and change requests by IT and business users
- Monitor system
What are some key characteristics of Pega BPM Iterations?
- Small, typically 3 to 6 months
- Be self-contained
- Plan for maintenance between releases
- Prioritize critical functionality in early release items along with higher risk features
What are some key benefits of Pega BPM Iterations?
- Short release cycles ensures that maximum value is obtained along the way
- Users provide higher quality requirements for subsequent releases after first hand experience
- Short release cycles reduce pressure on users to review all functionality in first release
- Planning for multiple releases establishes a framework for continued flow of value gain in the future
