01 - Introduction to Pega Methods Flashcards

1
Q

Why are Agile Methods better suited to projects where requirements change?

A

Development is in shorter intervals

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

How does delivery time impact value derived from a system?

A
  • 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the benefits of shorter release cycles?

A
  • Maximize value gained by the project
  • Allows users to gauge value of features requested in first iteration
  • Provides higher quality requirements for subsequent releases
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are some of the problems with longer release cycles?

A
  • Increase risk that new requirements will be added
  • Lost value
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Is Pega BPM a concrete prescriptive process?

A

No

It is an adaptable framework

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are the phases in Pega BPM lifecycle?

A
  • Inception
  • Elaboration
  • Construction
  • Transition
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What two activities supplement Pega BPM phases?

A
  • Project Initiation
  • Go-Live
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What artifacts are produced in Inception (Sizing) Phase

A
  • Business Objectives
  • Requirements
  • High Level Specifications
  • Work Types
  • High Level Process Model
  • Application Profile
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What artifacts are produced in Elaboration (Defining) Phase?

A
  • Specification Details
  • Requirement Details
  • Business Draft Flow Details
  • Draft Screens
  • Project Document
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What artifacts are produced in Construction (Building) Phase of Pega BPM?

A
  • System Behavior
  • Screen Implementation
  • External Interfaces
  • Application Document
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What artifacts are produced in Transition (Delivering) Phase of Pega BPM?

A
  • QA Test Results
  • UA Test Results
  • Move to Production
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the key Project Initiation Activites?

A
  • Define which sliver to begin with
  • Demo product features
  • Conduct knowledge transfer
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the key Inception Phase activities?

A
  • 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are the key Elaboration Phase activities?

A
  • 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are the key Construction Phase activities?

A
  • Assign application configuration tasks using an iterative model
  • Unit test each component
  • Run application test scripts and begin the system test process
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the key Transition Phase activities?

A
  • Complete system test process to ensure application is acceptable to stakeholders and business users
  • Ensure solution is maintainable by IT (including support)
17
Q

What are the key Go-Live activities?

A
  • Deploy final release candidate
  • Maintain application with enhancements, fixes, and change requests by IT and business users
  • Monitor system
18
Q

What are some key characteristics of Pega BPM Iterations?

A
  • 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
19
Q

What are some key benefits of Pega BPM Iterations?

A
  • 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