App Studio adoption
Lead System Architects (LSAs) should promote the use of App Studio in application development. App Studio helps Subject Matter Experts, Business Analysts, and Business Users to collaborate. Collaboration can remove gaps in understanding of the business requirements between professional developers and citizen developers. For example, Case Designer in App Studio helps with defining the high-level case lifecycle, associating every stage with required Personas, linking data objects, and relating each stage with the release cycle. However, there are some things that you should consider to ensure that the enterprise successfully adopts App Studio and that you provide citizen developers with the support they need for application development.
Successful adoption of App Studio
First, establish governance and evaluate the applications that are fit for the program. Once the application has been reviewed by the Lead System Architect, pair the business team with a coach. Teams with little or no App Studio experience rely heavily on the coach, while other, more experienced teams are self-sufficient. Ensure that there are regular meetings between the project team and the coach.
Publish a release train schedule and hold retrospectives to adjust what is not working. Create a community for business users to share their experiences and ask questions.
LSAs should develop a maturity model for the organization to help them adopt App Studio. As a best practice, the four-level maturity model can be implemented. The four levels are:
- Enablement/Collaboration
- Standalone Departmental Initiatives
- Supported Departmental Initiatives
- COE Orchestrated Deployment/Innovation
The following figure explains the different steps at each stage of the four-level maturity model:
Check your knowledge with the following interaction:
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?