June 11, 2018
Score 8 out of 10
Overall Satisfaction with Pega Platform
We are using the Pega platform to build custom workflow applications across the organization. I am leading the effort for our back office work to seamlessly orchestrate and automate complex service requests for our customers. We have engaged E&Y to help build a foundation framework where each workflow use case can leverage the common structures.
- The Pega platform has enabled us to quickly develop end to end tracking of back-office processes along with a myriad of integration points to legacy systems to automate a number of manual steps.
- Out of the box reporting and dashboards have saved time for our business partners in adapting to the new processes and managing to metrics in real time.
- Prototypes of the workflow are invaluable in gaining a quick validation of the workflow with end users. With Pega, we are able to build those models very quickly.
- The features themselves are not difficult to use, but I think Pega oversells the simplicity to non-technology organizations. While workflow can be built with minor training, having the proper data models and class structures established are critical to long-term success.
- Out of the box, error handling can be confusing to a novice developer in Pega. Pega can handle exceptions automatically but the default “broken queue” concept can get messy and ultimately result in work that sits unnoticed by end users and creates extra work for the support team.
- Experienced Pega engineers are in short supply and therefore more expensive than most other developers.
- With our framework, we have been able to build new applications in 10% of the time/cost. Example, we built an application that took 8 months and 1.2 million k in a traditional .net environment and was able to build a similar application in 60 days for about 100k
- Collaboration with the designer shaves weeks off the requirements gathering
- Standard reporting is a launchpad that allows the users to accept the system without waiting for MIS reports to follow application build which often would usually delay use for 60 to 90, but not with Pega
Pega is well suited for developing applications that manage fairly straightforward stages and steps based workflows. Complex workflows can be built but are more difficult to maintain and modernize, particularly when required to deviate from basic out of the box features and writing custom code. This risk is mitigated by experienced Pega architects setting and enforcing design practices.