App Studio adoption

Lead System Architect (LSA) should promote usage of App Studio in application development. App Studio helps in collaborating with Subject Matter Experts, Business Analysts, and Business Users. Collaboration will remove the gap in understanding the business requirements between professional developers and citizen developers. Case Designer in App studio helps in defining the high-level case lifecycle, associate every stage with required Personas, link data objects and relate each stage with release cycle. However, there are some items to consider ensuring 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 applications that are fit for the program. Once the application is reviewed by 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 was not working. Create a community for business users to share their experiences and ask questions.

Lead system architect should develop a maturity model for an organization to adopt App Studio. As a best practice, the four-level maturity model can be implemented. The following image shows different steps at each stage of four-level maturity model: