Level 3 Credential
The Level 3 Credential is a two-part exam consisting of a multiple-choice test and an interview with one of our Appian Architects. The Level 3 Credential evaluates an individual's knowledge of the platform and experience leading a project on Appian.
- Be a member of an Customer or Partner Organization (required)
- Passing the Level 1 Credential Exam and Level 2 Credential Exam prior to taking attempting the Level 3 Exam (recommended)
- Successfully completing Appian Developer and Advanced Developer courses(recommended)
- At least 24 months of project leadership experience is required. Leadership on a project consists of the following duties:
- Leading Sprint 0s
- Interfacing with stakeholders about user stories
- Leading grooming sessions and sprint demos
- Setting the overall design direction
- Enforcing reviews and best practices
- Meeting with the Appian Architects
- Exam Details
Participants must complete and pass Part 1 of the exam prior to continuing to Part 2.
The Level 3 Credential consists of 2 parts:
- Part 1: 35 multiple choice questions testing a thorough understanding of Appian concepts. Once started, participants must complete the exam within 30 minutes.
- Part 2: A live interview with an Appian Architect to review your Appian project experience.
The interview is structured like a design review. You must submit sample project artifacts at least a week before the scheduled interview date, including:
- Business Case: describe the customer situation/problem, project goals, and solution that was delivered. This can include:
- How the project or operations benefit the businesses strategy
- Project and/or release time scales
- The project risks
- The project’s limitations
- Business Impact: describe how many people were impacted by the application (should be more than one, preferably LOB users) and in what way.
- Expected return on investment (ROI) over time from the businesses perspective.
- Future extensions or add-ons to the solution.
- Project Responsibilities: provide an overview of your role and responsibilities as it relates to the project. This should include how many people were on your team. How you managed the client’s expectations from a technical and release perspective.
- Make up and structure of the delivery team.
- Daily responsibilities.
- Development Approach used.
- Risk mitigation strategies employed with specific examples.
- User Experience: Provide an overview of the user experience and how the user experience has been tailored for this client and application. It should cover how users interact with the system, and what considerations you took in relation to accessibility. How did you clarify the design with the client as part of the development approach. Please submit any diagrams, wireframes and/or screenshots that will illustrate how the user interacts with the system.
- Design Artifacts (that can be provided with customer consent) that provide a sufficient overview of the solution. This may include, but is not limited to:
- Diagrams/screenshots of the solution.
- Architecture and design document of the solution.
- Process model documentation (if available) or screenshots.
- Areas of special interest, e.g. where specific workarounds had to be used, or where a departure from best practices was necessary.
- Reusable components utilized as part of the solution.
- ERD and any accompanying materials, explanations
- Integration to other systems with details of system/integration design.
- What systems were integrated into the solution
- Diagrams of the integration architecture
- Directionality of the integrations
- Authentication methods
- Any complications encountered
- Testing Practices: Provide an overview of what testing practices were put in place in order to decrease risks and increase quality of the application. This can include functional and non functional testing.
- Devops: Provide details on how you used code management, deployments and change control practices to reduce development to production risks while ensuring and managing quality.
- Health Check Results: Explain how the health check results have been used in the continuous improvement of the application. If Health Check has not been used please explain why and provide other metrics showing how continuous improvement has incorporated and measured in your project.
- Application Concepts
- Appian Object Design
- Appian and Agile terminology
- Designer Interfaces
- Application and Object-Level Security
- Application Deployment Best Practices
- Administrative Functions
- Document Management
- Application Usability Best Practices
- Advanced Interface and Process Management
- Advanced Data Structures
- Integration Objects
- The Appian Playbook
- $600.00 (US)
- Credential fees are non-refundable. The fee covers grading and materials. Paying the credential fee does not guarantee awarding of the credential.
- Cost of the credential is for each attempt. Exam re-takes and project re-submissions are not included.