The Application Delivery Governance Model enables customers with a lightweight, effective way to govern their Appian delivery teams. By implementing this model, Appian program owners can ensure that applications are 1) built according to best practices and 2) adhere to program-specific requirements and standards. Designed by Appian’s Customer Success Professionals, this model provides delivery teams with the standards, measurements and process alignment needed to develop quality low-code applications, quickly and efficiently.
Roles InvolvedWhile this model can be implemented with slight variations based on organizational requirements and risk appetite, Appian strongly encourages the involvement of at minimum the following three roles in order to implement effective governance. Program Owner The Program Owner wears a few different hats, but is ultimately the individual responsible for making sure the governance model is followed. They are the ultimate approval authority for governance standards, ensuring that project managers enforce standards, and making the “go forward” decisions at readiness checks. They also provide delivery teams with contextual information and awareness of the program’s direction.
Program Architect The Program Architect’s primary concern is executing the governance program through a series of lightweight reviews and readiness checks. They will ensure the high quality of your application.
TIP: To get the most value out of your Program Architect, Appian encourages this role to be a part of the planning efforts early in the project lifecycle. The visibility will not only help prepare them for readiness checks throughout, but their domain expertise will also help navigate unforeseen obstacles in planning sessions.
Team Lead(s) Team Leads are the day-to-day coordinator for application development ceremonies and serve as the main point of contact for delivery teams. They ensure their teams follow governance guidelines and standards set by the Program Owner and facilitate discussions between teams where needed. They also attend all readiness checks and reviews for their teams.
Readiness Checks and Application Reviews Application delivery requires different types of governance attention across the application development lifecycle. Appian has condensed this lifecycle into four phases and mapped a series of mandatory, lightweight readiness checks and application reviews to each phase: Prepare, Initiate, Build, and Release (see Figure 1). These readiness checks and application reviews ensure best practices and program standards are implemented consistently and that the application does not create any unnecessary or unforeseen organizational risk.
Application ReviewsDuring each phase of the application development lifecycle, delivery teams engage in select reviews where their progress will be checked by an expert against outlined best practices and program-standards. These reviews are designed to be lightweight and favor discussion over documentation; although some reviews do require artifacts for facilitation.
Application reviews will result in a prioritized list of recommended next steps categorized by risk profile (High, Medium, Low). If there are findings in the “High” category, the team should address the recommendation and perform the review again. Teams should still address “Medium” and “Low” findings, but these should be done in parallel as development continues.
Readiness ChecksAfter a team is ready to advance the next phase of development, delivery teams engage in readiness checks. Here, program management will review the current status of all findings and determine whether the team is ready to advance to the next lifecycle phase. If a team is not deemed ready to proceed, Program Owners will provide teams with the steps needed to advance to the next phase. Delivery teams will continue this process until the application has been released.
Be sure to download the application review and readiness checklists document below.
Solution Architecture ReviewGoal: Mitigate architectural risk early in the process by modeling and reviewing foundational design decisions.What to Bring: Completed Appian Architecture DocumentWhen to Review: End of Initiate PhaseAttendees: Team Lead, Project Manager, Program Architect
Development ReviewGoal: Ensure the developed features are designed according to standards. What to Bring: Demonstration of completed featuresWhen to Review: As needed, but at least a few times every iterationAttendees: Team Lead, Key Developers, Program Architect
UX ReviewGoal: Ensure interfaces are intuitive, adhere to best practices, and are consistent across the platform. What to Bring: Mockups or demonstration of developed UX When to Review: During Initiate Phase or during sprint 1 and again before the end of the Build Phase.Attendees: Team Lead, Key Developers, Program Architect
Health Check ReviewGoal: Ensure developed features adhere to development standards via the Health Check tool. What to Bring: Health Check results from the development environmentWhen to Review: Every iterationAttendees: Team Lead, Program Architect
Technical Readiness CheckGoal: Ensure the application is technically ready to release. Though the delivery team will have created a release-able application throughout the Build phase, this is an opportunity for a final check.What to Bring: Deployment Plan, Defect LogWhen to Review: During the Release PhaseAttendees: Team Lead, Key Developers
© 2020 Appian. All rights reserved.