Where does the Serendebyte Pega ALM Integration Toolkit (PAT) Fit?
ALM, or Application Lifecycle Management solutions are a vital part of development projects. Properly used, the ALM solution provides clarity into a complex process for testers, developers, analysts and project managers, and can give project sponsors the high level dashboard type view they require to maintain visibility into a project’s health. There are many ALM solutions available, many with features specifically designed to work with specific methodologies. When considering an ALM solution for a Pega project there is one major drawback to third party ALM solutions, they are not made to leverage the native ALM functionalities built into Pega.
Pega PRPC, offers some truly revolutionary features, the ability to capture requirements, user stories/use cases and flows in the system during DCO sessions and then providing these gathered specifications to system architects in real time in the system they are working in is an extraordinarily powerful tool. With the addition of Pega’s Project Management Framework, Pega can provide a full scale ALM, the only drawback to this is that in most cases a customer already uses an ALM solution and has several projects outside of the scope of Pega.This is where the Serendebyte Pega ALM Integration Toolkit (PAT) comes in. Serendebyte began development of this tool based on needs expressed by both System and Business Architects. The ability to tie requirements and user stories stored in third party ALM tools directly to Pega gives the project team the visibility they require while still using the powerful tools provided by Pega PRPC.
PAT allows us to close the gap between project managers using existing ALM tools, business architects who often need to work in both existing ALM tools and Pega, and System Architects who are responsible for building a system and reporting status across ALM and Pega tools. With PAT it is possible to utilize multiple tools all in the way they are meant to be used, without forcing resources to duplicate work and effort.
By giving System Architects and Business Architects a one stop shop for requirements and specifications within Pega, we give a project team a truly unique 360-degree view of tasks assigned and of the complete project. This is particularly powerful in distributed team models where Business Architects are not co-located with development teams and communication is not always immediate. When traditional ALM artifacts are separate from the Pega development environment it is very easy to miss key requirements and descriptions and end up reworking tasks that could have and should have been completed correctly the first time.
Serendebyte has seen a tremendous amount of interest in just the first release of the PAT, and we are very excited about some of the functionality we plan to add in future releases.
To learn more about PAT feel free to contact us.