Question

62
Views
Close popover
Nige Ross (rossn)
PEGA
Senior System Architect
Pegasystems Inc.
AU
rossn Member since 2016 3 posts
PEGA
Posted: February 1, 2018
Last activity: February 1, 2018
Closed

Pega Upgrades and Review/Refactoring of Existing Build

Upgrades to the PRPC platform and Stragetic Apps deliver new features, improvements and new logic to customers. Regularly, such new functionality supersedes project build that has been delivered to meet customer requirements not yet met previously by Pega standard delivery. What are peoples thoughts on the priority/process of reviewing project-specific build after each upgrade, to determine if removal of custom rules/code and using Pega standard can be achieved?

Such development "black box" activities are not usually seen as a priority by the Process Owner when reviewing the backlog. As customers application(s) grow in size, functionality and complexity through Agile delivery, rule by rule review against what the upgrade delivers (and how) surely compounds to become unmanageable within the Pega release cycle?

Low-Code App Development System Administration Upgrades
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.