{"id":1409,"date":"2021-07-01T13:36:36","date_gmt":"2021-07-01T13:36:36","guid":{"rendered":"https:\/\/www.anamata.nl\/?p=1409"},"modified":"2024-06-05T12:09:24","modified_gmt":"2024-06-05T12:09:24","slug":"the-skills-of-a-pega-architect-introducing-the-m-model","status":"publish","type":"post","link":"https:\/\/www.anamata.eu\/nl\/1409\/","title":{"rendered":"De vaardigheden van een Pega Architect: introductie van het M-Model"},"content":{"rendered":"\n

As Pega continues to deliver innovative software that crushes business complexity, challenges are on its path. A big promise of low-code platforms like Pega is to facilitate fast delivery of great new features to enhance an organization\u2019s business. However, fulfilling this promise can be quite a challenge, because the time spent on actual \u201cbuilding\u201d is drastically reduced. This relatively increases the impact of aspects like business analysis, design, release management and operations. In addition, these aspects have become more and more intertwined in agile, low-code endeavors. 
These challenges require a rethinking of both the software delivery process and the optimal skills of a Pega Architect: Pega Express\u2122 and Anamata\u2019s M-shaped profile.<\/p>\n\n\n\n

Pega Express\u2122<\/strong><\/h3>\n\n\n\n

Having a low-code platform, capable of creating customer-centric journeys, it is key to identify the stakeholders of that journey and include these stakeholders in the delivery process. 
To optimize the collaboration between a Pega delivery team and the business stakeholders, it is important to have a way of working in place. This way of working should optimize the amount of time spent on identifying processes, determining requirements, validating the MLP[1]<\/sup><\/a> and giving feedback during the process. Additionally, all delivery team members should be aware of the importance of the way of working and have the ability to execute.<\/p>\n\n\n\n

Pega developed a methodology to describe this way of working, Pega Express\u2122. It is, in their own words, \u201cA light, design-focused delivery approach that uses Pega\u2019s low-code experience, best practices and scrum to deliver meaningful outcomes quickly.\u201c<\/p>\n\n\n\n

<\/div>
\n
\n

To deliver the right things fast, the focus should be on the definition of these right things, based on the business outcome. With the desired business outcome in mind, the most valuable journey(s) can be determined. The focus should be on one MicroJourney\u2122 at a time, creating MLPs that include these journey(s). 
<\/p>\n<\/div><\/div>\n\n\n\n

\n
\"\"
Pega Express\u2122 overview by Pega. More information can be found through this link.<\/a> <\/figcaption><\/figure>\n<\/div><\/div>\n<\/div><\/div><\/div>\n\n\n\n

Focus<\/strong> on business outcomes<\/h3>\n\n\n\n

Anamata believes that the key to a successful delivery process is a relentless focus on the business outcomes. This focus on what an organization wants to achieve with a technological solution, should be present in each and every phase of the delivery. As a result, all people involved in a project will know the considerations and decisions that are being made from a business perspective. This will encourage all to focus on the outcome and be aware of any deviations.
Having the Business Outcomes as common goal not only helps to maximize the effectiveness of everyone\u2019s contributions. It is also highly motivational to<\/p>\n\n\n\n