1

Technical Governance Overview

COE Peer to Peer Forum

20 November 2015

2

Topics

Why Technical Governance ?

What is it and who does it ?

How to start ?

WHY TECHNICAL GOVERNANCE ?

4

Pega Application Development is Easy

We want to

Deliver on time

With repetitive quality

Maximise reuse

But…

Timelines are challenging

Team experience varies

Requirements change

Getting it right takes discipline and experience

5

Delivery Pressure Brings Risky Decisions

Emergency cargo dump

Best Practices

Quality Specifications

Guardrails

Reusable Design

Unit Testing

…

6

Technical Governance Helps Lower Risk

Ensures and monitors use of best practices

Prioritises and maximises reuse

Ensures common build and release approach

Prevents building development silos

Standardises good designs and practices

WHAT IS TECHNICAL GOVERNANCE ?

8

What is Pega Technical Governance ? Set of practices and governance processes to ensure solutions quality, reference architecture

and manage compliance with policies and standards

Reduce technical risks through proactive monitoring and remediation

Increase compliance with enterprise policies and standards

Control and align design with the Pega reference architecture and enterprise architecture

Increase and coordinate reuse capabilities

Manage common technical Issues

Agility Cost of Ownership

9

Pega Technical Governance Model

Lean model stripped of heavy processes

Modular to prioritise what is needed

Starts project level and moves to COE

Uses Pega tools to minimise overhead

Engages with PDLC in a structured way

10

Technical Governance Components Covers three major areas where

quality of solution is concerned– Reference Documents

– Support Practices

– Solution Quality

Technical Governanceis owned by COE Roles

Central point for escalationof technical issues

Typically driven by regular technical governance meeting

Technical Governance

Reference Architecture

Best Practices and EPS

Release Management

Build Management

Expert Services

Technical Oversight

Reuse Management

Design Support

11

intake

Sprint 0

Sprint 1Sprint N

Sprint Z

Go-Live

E

C

E

C

E

C

Expert Services - SCRUM• Technical Governance Team engaged efficiently

• Technical delivery risks reduced

• Development team uses right tools

Harvest Reusable Assets

Phase Readiness Assurance

User Experience Review

Performance Healthcheck

Configuration Walk-through

Pega Fit & Business

Value Assessment

Project Onboarding

Hardware Sizing

Application Profile Review

Application Express Support

Reuse Assessment

Design Review

Rule Security Analyser

• Once before transition

Log & Alert Review

• Every week

PAL,DB Trace, Profiler

• Run Regularly

Guardrail Tool

• Once per 2 weeks

Unit Test and Tracer

• Unit test before check in

Portfolio

Planning

12

intake

Inception

ElaborationConstruction

Transition

Go-Live

E

C

E

C

E

C

Expert Services – Pega BPM• Technical Governance Team engaged efficiently

• Technical delivery risks reduced

• Development team uses right tools

Harvest Reusable Assets

Phase Readiness Assurance

User Experience Review

Performance Healthcheck

Configuration Walk-through

Pega Fit & Business

Value Assessment

Project Onboarding

Hardware Sizing

Application Profile Review

Application Express Support

Reuse Assessment

Design Review

Rule Security Analyser

• Once before transition

Log & Alert Review

• Every week

PAL,DB Trace, Profiler

• Run Regularly

Guardrail Tool

• Once per 2 weeks

Unit Test and Tracer

• Unit test before check in

Project

Initiation

13

Expert Services: Project Onboarding

Project Onboarding is an entry gate for the projects – where Project Team is familiarised with the Pega build approach, standards and best practices and Asset Repository.

This service focuses on Assessment of the Route-To-Live for the project

Adoption of the Release Management Process

Adoption of the Technical Governance Model

Adoption of Pega Best Practices and build approach

Access to Pega Asset Repository

Input

• Project Onboarding Questionnaire

• Interview with the PM

Output

• Pega Route-To-Live assessment

• Enterprise policies and standards package

• Access to Asset Repository

• Access to Pega CoE Documents

Reference: Project Onboarding Service Description .ppt

14

Expert Services: Application Profile ReviewReview of DCO artifacts generated by the AP

Technical Feasibility Review

Identify dependencies with external systems

Walk through of use cases and determine technical feasibility

Identify reporting and correspondence needs in PRPC

Review work types

Project Health Check

Clear business objectives and project scope

Use cases defined at sufficient detail level

Project sizing has been performed and is reasonable

Adequate number of skilled resources available for the project

Funding is approved, project plan exists and delivery dates are

achievable

Initial Reuse assessment – build with “reuse in

mind”

Identify existing components in the Shared Asset Repository

Initially Identify candidates for future reuse

Reference: AP Review Service Description .pdf

Input

• Pega Application Profile Document

• Pega Sizing document

• Interview with the team

Output

• Pega AP Recommendations

15

Expert Services: Design Review Design Review establishes that the business users’ needs have been well understood and clearly documented and that

all stakeholders are aligned on project scope and requirements. An unbiased, informed assessment also ensures that your team is fully leveraging Pega’s technology for maximum performance, responsiveness, quality, extensibility, scalability, maintainability, and security

High level review of proposed Architecture as described in the project charter

Assessment of feasibility of “future state” as proposed

Review focuses on overall picture, i.e. how the Pega solution will fit into the larger Customer ecosystem

Address typical technical design challenges that PRPC development teams may be facing. Delivered in 3 parts:

Document Review: Architecture docs, AP doc (generated), Design doc (generated), Class Structure

Interviews with key team members: Lead BA, Tech Lead, Project Manager

Document Findings & Recommendations

Input

• Pega Application High Level Design

• Key Design Challenges List / Dashboard

• On-site interview with the project Lead System Architect

Output

• Pega CoE Design Review Document with recommendations

• Initial qualification of the Key Design Challenges to Design Clinic process

Reference: Pega High Level Design Template, Pega Design Review Template, Key Design Challenges Template

16

Technical Governance Roles

CoE Manager / Technical Lead

•Owns and directs Technical Governance Strategy

•Owns Pega Reference Architecture

•Defines level of engagement of the Technical Governance team

•Reports Technical Health status to Delivery Management

•Manages all Technical Governance escalations

CoE Lead System Architect

•Maintains Reference Architecture

•Ensures that Design Principles are followed

•Drives Design Clinic Activities

•Oversees Technical Quality

•Assists Lead Solution Design with Reuse Management

CoE Enterprise Architect

•Ensures Reference Architecture feasibility

•Influences Enterprise-level reference architecture

CoE Lead Business Architect

•Owns Business Solution Architecture

•Facilitates Design Clinics to maintain proper Business Focus

•Engages Business as needed for the proper Business Solution design and feasibility

•Manages and Owns Catalogue of Reusable Assets

Technical Governance Team

Execution RolesManagement Roles

HOW TO START ?

18

Tips For Technical Governance Newcomers

“Death Grip” kills innovation and pragmatism

Use Expert Services rather than heavy process

Use Pega development tools to manage quality

Keep Improving Policies and Standards as you go

Get help from Pega BPM Adoption Team

19

Technical Governance 5-steps Quick Start

Start using Project level Technical Oversight tools

Define near term goals and prioritise Expert Services with supporting processes

Establish and enable roles for the Technical Governance Team

Implement Technical Governance Meeting and selected Expert Services

Adopt and refine basic Best Practices and EPS

CASE STUDY

21

Technical Governance Real-Life Case Study

Global Pega Program to roll out to 150 countries

2 new programs to join existing portfolio in the next 2 quarters

Innovative architecture implemented by multiple SI-s

Governance challenges started appearing from day zero

Much better after technical governance was adopted

QUESTIONS & ANSWERS

23

Technical Governance

Performance

24

Achieve and maintain optimal production performance by including production & operations considerations throughout application lifecycle

Inception

Elaboration

Construction

Transition

Production

25

intake

Sprint 0

Sprint 1Sprint N

Sprint Z

Production

Performance Governance -

SCRUM

Monitoring

Infrastructure Optimization

Performance Expectations

Reporting & Data Retention

Portfolio

Planning

Predictive Performance Analysis Monitoring & Metrics

Performance & Quality Governance

Performance Validation

26

intake

Inception

ElaborationConstruction

Transition

Production

Performance Governance –

Pega BPM

Monitoring

Infrastructure Optimization

Performance Expectations

Reporting & Data Retention

Project

Initiation

Predictive Performance Analysis Monitoring & Metrics

Performance & Quality Governance

Performance Validation

27

Sprint 0 / Inception

28

Sprint 0 / Inception Assign metrics for functional and non-functional performance goals

Document target inventory for cases, workbaskets, worklists, attachments and service level agreements

Evaluate data lifecycle requirements for retention, archive, purge, search or reactivation

Gather requirements for operations, audit and business intelligence reporting.

Establish Pega7 features appropriate for functional goals.

Set expectations for production monitoring and governance. Assign responsibility for monitoring technical and functional indicators of application health and success

Identify non-functional integrations for monitoring and operations management if appropriate.

Deploy AES or PDC at outset - monitor stability of development systems and performance and quality of higher environments.

29

Sprint(s) / Construction

30

Sprint(s) / Construction Minimize IO for greatest scalability and performance

Maximize parallelism to improve user experience

Document expectations for service and connector responsiveness and establish ownership & responsibilities

Optimize schema based on reporting requirements

Balance features with performance requirements. Identify conflicts early

Include appropriate instrumentation to prove system success Is the application delivering expected business value?

Are interfaces performing as expected?

Are task, case and queue inventories consistent with expectations?

Build all applications to leverage high availability multi-node operations

Explicitly tune automated agent processing to match functional needs of your application

Document deployment design to allow for appropriate monitoring

Include services, connectors and scripts to support custom monitoring if required

31

Predictive Performance Analysis

32

Predictive Performance Analysis Performance or scaling inefficiencies should be fixed during unit testing rather than deferred until after functional signoff

Use Pega7 Performance Analysis Tools, including

PAL : screen by screen resource utilization summary

DB Trace : each and every database query

Profiler : rule by rule timing and CPU

Use profiler to identify ‘slow’ and ‘expensive’ rules, particularly streams and expressions

Collect and analyze database access

Identify unnecessary database queries – leverage data pages to avoid duplicate data lookups

Identify and review use of database functions (UPPER) or LIKE in where clause

Identify use of stream functions and assess scalability

Engage database administration team during development process – not after go-live

Assess indexes needed to satisfy where, join and order by clauses

Identify costly queries that would best be improved by better rules

Help DBA staff to best help you

Zero tolerance for Alerts

Zero tolerance for Exceptions

33

Predictive Performance Analysis

It’s math, not magic

34

Predictive Performance Analysis

Be honest with bad news

35

Infrastructure Optimization (tune the plumbing)

36

Infrastructure Optimization Tune application server resources based on resource requirements ‘as built’ and consumption as measured during testing

Java memory / garbage collection

Thread pools for agents, child requestors and asynchronous data pages

Distribute processing to ensure consistent response for users

Agents

Services

Search

Listeners

Tune database to minimize contention and maximize throughput

Buffers and memory

Optimize log space to reduce log switching overhead

Pre-allocate space to minimize ‘extending’ storage at runtime

Optimize access to volatile objects identified during predictive analysis

Leverage DBMS-native performance tools and engage DBA’s

Tune Pega7 engine based on alerts, expected load and reviewing SMA advanced features

Set requestor pools appropriate for expected service and data page volumes

Adjust caches as needed to avoid draining and pruning

37

Performance Validation (Load Testing)

38

Performance Validation (Load Testing)

39

Performance Validation (Load Testing) Design tests consistent with how the application will be used

Realistic distribution of load cases

True human think time

Provide a suitably large number of test operators and test customers/accounts to avoid ‘hot clusters’ such as

Oversize worklist and worklist contention from multiple use of single test operator

Oversize transaction history from multiple use of single test account

Each test must include reports or queries to prove that test cases were processed successfully

Start with one user and build

Review logs, alerts and data after each test

Stop and fix – if a test fails with ten users there is no point running one hundred

40

Performance Validation (Load Testing)

41

Monitoring

42

Monitoring Use best of breed tools for basic platform monitoring services (server availability, CPU, disk space & servlet availability)

Leverage Pega tools (AES/PDC or API’s) for real-time notification of critical internal events

Agent operations and agent failures

Requestor counts

Database exceptions

Excessive number of performance alerts

Long running requestors

Leverage AES/PDC or build processes to gather and report system responsiveness, performance opportunities and quality issues. These data sources include

Log-Usage data – summarized PAL data automatically persisted to the database

Alerts – excessive resource usage or performance outside of configurable thresholds

Exceptions

Regularly report processing metrics and case / task inventories to technical and functional managers

Is case creation / resolution rate consistent with expectations?

Are task (assignment) and queue levels appropriate ?

Have automated tasks failed to process appropriately?

Business monitoring is as important as technical monitoring

43

Monitoring – RealTime Events

44

Monitoring – RealTime Events

45

Monitoring – Automated Tasks

46

Monitoring – Automated Tasks

47

Three Principals of Governance

1- Clearly defined roles, responsibilities and authority

48

Three Principals of Governance

2- Metrics and measurements

49

Three Principals of Governance

3- Well defined prioritization

50

Governance Regular assessments of whether application / system is delivering on functional and technical performance requirements

Data driven continuous improvement process to improve responsiveness and system quality

Review key metrics and data points including

Server response time

High priority alerts, based on severity and frequency

High priority exceptions based on frequency

Regularly track response time – especially before and after any significant functional or technical deployment

Identify and prioritize opportunities to improve performance and quality

51

Governance – Average Response

52

Governance – High Priority Alerts

53

Governance – High Priority Exceptions

QUESTIONS & ANSWERS

55

Next Steps

Send any additional questions to PegaCOE@pega.com

Look out for our follow up email with today’s replay and presentation

Let us know what topics you would like to hear about in an upcoming webinar

Next COE Peer to Peer webinar will be pre-PegaWORLD 2016

56

twitter.com/pega

linkedin.com/company/pegasystems