Posted: 1 Feb 2018 16:35 EST Last activity: 1 Feb 2018 16:48 EST
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?