Get Started with Process Models

Appian Max Team — Tue, 23 Apr 2024 13:08:56 GMT

Current Revision posted to Article by Appian Max Team on 4/23/2024 1:08:56 PM

There’s a lot to do and consider when working with process models in Appian. How do we set ourselves (and our process models) up for success from the beginning? Process model design should not only be focused on optimizing the load on the system hardware, but should also ensure the future application support team will be able to quickly and easily address end user concerns. Performance considerations for minimizing process runtimes and node counts help ease the burden on the system, but there are a few key aspects that we should address when creating any process model to ensure maintainability:

Security
Dynamic Display Names
Data management
Alerts

Tackling these aspects early on in the development of every process model will ensure that you, and any future developer that might pick up your project, are set up for success in developing, testing, and troubleshooting your process model.

Security

Process model security is addressed when any process model is initially created and is the most complex security of any Appian object. In addition to the typical object security roles of Administrator, Editor, Viewer, and Deny, process models also have Manager and Initiator. To initiate any process, a user must have at least the “Initiator” permission level. Users who have no access to initiate a process model will be unable to see any record actions associated with that process model.

Ensure the correct user groups have the appropriate level of security access to your process model from the beginning. If security for a process model needs to be updated it can be accessed from the Appian Designer Object View or from the Process Modeler itself. For more information, see the Process Model Security table.

Dynamic Display Names

By default, new processes in Appian have the same process display name as the process model object. This makes it difficult to differentiate between process instances when troubleshooting.

As you can see, the above instances of the AA Add Vehicle process model version 3.0 are not easily distinguished. A better approach is to update the Process Display Name on the General tab in the Process Model Properties to include some dynamic information such as the year, make, and model of the vehicle being added.

Dynamic display names make it easier to distinguish between process model instances and can provide valuable context when troubleshooting a process model that is misbehaving.

Data Management

Every time a process model instance is executed, Appian caches information from that instance. Over time, this information can take up a lot of space. It is important to consider this when configuring the data management for your process model. Except in rare circumstances, it is best to avoid the “Do not automatically clean-up processes” option. For process models that require history or may need extra recoverability during development or initial deployment, use the “Archive” option. For process models where the history is not important, use the “Delete” option.

See Consideration for Archiving Processes for more best practices.

Alerts

Alerts for a process model are triggered when there is an issue with a process instance. The system default for alerts is to send an email to all system administrators. Typically, however, alerts are sent to the administrators of the application while it’s in development. After deployment these alerts will be configured to be sent to the administrator of the production environment. Therefore, during initial set up, you should configure the alerts to be sent to the application administrators and not the system administrators.

Creating manageable, efficient, robust, and maintainable process models begins with a strong foundation. Addressing the areas of security, dynamic display names, data management, and alerts from the beginning will set you and your process models up for success in the future.

Tags: records, process models, Data Management

Get Started with Process Models

joel.larin — Wed, 14 Feb 2024 18:54:15 GMT

Revision 20 posted to Article by joel.larin on 2/14/2024 6:54:15 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

By default, new processes in Appian have the same process display name as the process model object. This makes it difficult to differentiate between process instances when troubleshooting.

Dynamic display names make it easier to distinguish between process model instances and can provide valuable context when troubleshooting a process model that is misbehaving.

Data Management

See Consideration for Archiving Processes for more best practices.

Alerts

Tags: records, process models, Data Management

Get Started with Process Models

joel.larin — Wed, 10 Jan 2024 16:21:19 GMT

Revision 19 posted to Article by joel.larin on 1/10/2024 4:21:19 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

By default, new processes in Appian have the same process display name as the process model object. This makes it difficult to differentiate between process instances when troubleshooting.

Dynamic display names make it easier to distinguish between process model instances and can provide valuable context when troubleshooting a process model that is misbehaving.

Data Management

See Consideration for Archiving Processes for more best practices.

Alerts

Tags: records, process models, Data Management

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 19:42:32 GMT

Revision 18 posted to Article by joel.larin on 1/9/2024 7:42:32 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

By default, new processes in Appian have the same process display name as the process model object. This makes it difficult to differentiate between process instances when troubleshooting.

Dynamic display names make it easier to distinguish between process model instances and can provide valuable context when troubleshooting a process model that is misbehaving.

Data Management

See Consideration for Archiving Processes for more best practices.

Alerts

Tags: records, process models, Data Management

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 19:40:07 GMT

Revision 17 posted to Article by joel.larin on 1/9/2024 7:40:07 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

By default, new processes in Appian have the same process display name as the process model object. This makes it difficult to differentiate between process instances when troubleshooting.

Dynamic display names make it easier to distinguish between process model instances and can provide valuable context when troubleshooting a process model that is misbehaving.

Data Management

Alerts

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 19:36:24 GMT

Revision 16 posted to Article by joel.larin on 1/9/2024 7:36:24 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

By default, new processes in Appian have the same process display name as the process model object. This makes it difficult to differentiate between process instances when troubleshooting.

Dynamic display names make it easier to distinguish between process model instances and can provide valuable context when troubleshooting a process model that is misbehaving.

Data Management

Alerts

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 19:32:36 GMT

Revision 15 posted to Article by joel.larin on 1/9/2024 7:32:36 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

By default, new processes in Appian have the same process display name as the process model object. This makes it difficult to differentiate between process instances when troubleshooting.

Dynamic display names make it easier to distinguish between process model instances and can provide valuable context when troubleshooting a process model that is misbehaving.

Data Management

Alerts

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 19:31:25 GMT

Revision 14 posted to Article by joel.larin on 1/9/2024 7:31:25 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

By default, new processes in Appian have the same process display name as the process model object. This makes it difficult to differentiate between process instances when troubleshooting.

Dynamic display names make it easier to distinguish between process model instances and can provide valuable context when troubleshooting a process model that is misbehaving.

Data Management

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 18:42:59 GMT

Revision 13 posted to Article by joel.larin on 1/9/2024 6:42:59 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

By default, new processes in Appian have the same process display name as the process model object. This makes it difficult to differentiate between process instances when troubleshooting.

Dynamic display names make it easier to distinguish between process model instances and can provide valuable context when troubleshooting a process model that is misbehaving.

Scope

Within the scope section, organizations should provide prospective delivery partners with detailed descriptions of the scope of services and the desired solution’s functional and non-functional capabilities and requirements. These descriptions should be written to the level of detail that facilitates accurate estimation for the selected contracting approach. Organizations should also clearly outline the bounds of project scope to avoid confusion around project deliverables and scope creep. The following subsections outline the scope suggestions.

Services

Below is a list of services you would expect to see from a partner when proposing to manage your project. The full list may not apply in all project scenarios:

Agile Project Management
Stakeholder Management
Requirements Management
Configuration and Development
Data Management
Architecture, Infrastructure Support, and System Administration

Functional requirements

The following factors will help accurately estimate the scale and scope of an Appian solution. It enables organizations and partners to quickly begin “Sprint 0” where project goals and scope is confirmed, and initial sprints are planned.

High-level description statements of system functionality, in support of the objectives specified in the prior sections. Note that Appian does not recommend using detailed requirements documents (eg. BRUF), but instead high-level objectives which support an agile requirements process.
Supported business processes, including providing business process flow diagrams.
System Personas, including high-level descriptions of how the personas will use the application and the number of anticipated users by persona.
User Interfaces, Appian Sites, Reports, and Generated Documents, including high-level descriptions, estimated or expected quantities and complexities.
Integrations, including descriptions, methods (e.g. file, e-mail, messaging, database connection, etc.), data volumes, interface flows, data specifications, and formats.
Document Management, including the types and formats of stored documents and the anticipated document sizes and volumes.

For the full list of functional requirements, see the downloadable ebook.

Non-functional requirements

Similar to the Functional Requirements, the Non-Functional Requirements will help formulate an accurate proposal and cost estimate for the in-scope solution.

Identify technical environments for pre-production and production. State the partner’s responsibility for infrastructure/network engineering, configuration documentation, hardware, network, and software installation support and/or administration.
Continuous Integration/Continuous Deployment (CI/ CD) pipeline requirements, including automated testing, automated deployment, software version control, etc.
Technical standards, enterprise architecture standards, and governance processes and review requirements.
Performance requirements, including peak concurrent users, total user counts, application response times, anticipated data volumes etc.
User experience standards and user interface requirements.
System Service Level Agreement (SLAs) requirements.

For the full list of non-functional requirements, see the downloadable ebook.

Team Requirements

Project delivery team staffing and structure should align to the scope, scale, and complexity of the planned Appian solution, as well as with organization-specific processes and requirements. While the specific program and/or project designs may vary, organizations should ask for personnel with the right qualifications, training, and experience to fill defined roles that efficiently deliver high quality outcomes.

Role	Qualifications
Team/Delivery Manager	Appian Certified Analyst (or higher) Recommended 18+ months of active Appian project experience Agile project management certification (eg. SAFe Certification, PgMP and/or PMP)
Architect	Appian Certified Lead Developer Recommended 3-4 years of active Appian project experience Certified Scrum Master or equivalent certification
Lead Developer	Appian Certified Lead Developer Recommended 2-3 years of active Appian project experience Certified Scrum Master or equivalent certification
Low Code Developers	Appian Certified Senior Developer Junior team members- Appian Certified Associate Developer
Analysts and/or Testers	Appian Certified Analyst Note: These roles can be performed by Appian developers rather than specialists
UI/UX Engineers (optional)	Appian Certified Associate Developer Appian Pro UX Badge (Coming Soon) Implementing SAFe Certification Note: These roles can be performed by Appian developers rather than specialists

Project level resourcing

At the project level, Appian recommends small, multidisciplinary teams, called Pods, that deliver outcomes through short iterations, called sprints. Typically, these teams consist of 4 to 7 team members, and contain a Scrum Master, a Product Owner*, and the development team consisting of architecture, development, business analysis, and testing capabilities.

In some cases, specialized skill sets, such as DevOps/System Administrator or Integrator team members, are required based on the scope of work the team is delivering. For complex implementations, create dedicated Technical and Infrastructure Pod(s) to focus on the delivery of infrastructure components, DevOps pipelines, and common components and other specialized technical stories.

Appian Project Delivery Best Practices

Appian suggests that the following best practices be specified as part of a contract:

The delivery partner will implement the solution using only out-of-the-box Appian platform features and functionality unless otherwise confirmed by an Appian Architect.
Appian Health Check should be scheduled to automatically run every increment in all non-production environments. All the new high-risk findings must be addressed before the increment ends. Other findings should be added to the product backlog and prioritized along with other backlog items. The list of findings includes but is not limited to: failures to adhere to design best practices, performance issues, process sizing, system resource utilization, etc.
Appian Health Check should also be scheduled to automatically run every month in the production environment. All high-risk findings must be prioritized for remediation in the following increment and addressed before the next production deployment. Add other findings to the product backlog and prioritize along with other backlog items.
Architectural reviews and configuration peer reviews will be conducted as part of the implementation. The Senior Appian Designer or Appian Architect will validate that the implemented configurations adhere to the agreed-upon architectural direction and meet technical requirements. During Peer Reviews, the Designers, the Senior Appian Designer and/or Appian Architect review individual configurations ensuring that best practices are followed and that the solution will perform as required. For more information, please review Appian’s best practice readiness checks and application reviews.
All User Interfaces must follow Appian’s published UX Design Guide. The Appian Architect should ensure compliance against a project tailored User Interface Style Guide for all applications in the Appian platform.
The partner will create a high-level system design that describes process, data, integrations, and security for the system’s future state. The system architecture will describe the functional design of the system at a high level. This description will include key news events, tasks, records, reports, and actions
The partner will proactively collaborate with the stakeholder community to ensure that the project direction, requirements, and designs are aligned to the stakeholder’s vision and business needs. As required, the partner will use techniques to collaborate on and confirm direction including developing prototypes as necessary.
The partner will allow project stakeholders to provide feedback, and will gain on-going approval for completed product features.
The partner will collect system performance requirements and develop and execute automated performance testing scripts. Performance testing activities will be planned to occur throughout the delivery of the project life cycle, ensuring that issues are identified and corrected early.

Select delivery partners who understand the best practices for delivering Appian based solutions. Assess the vendor’s approach to integrating and applying best practices within their solution. For more best practice guidance, visit the Appian Max Success Center.

Download full article e-book

community.appian.com/.../Right_5F00_Appian_5F00_Delivery_5F00_Partner_5F00_WP_5F00_Final.pdf

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 18:40:37 GMT

Revision 12 posted to Article by joel.larin on 1/9/2024 6:40:37 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

By default, new processes in Appian have the same process display name as the process model object. This makes it difficult to differentiate between process instances when troubleshooting.

Dynamic display names make it easier to distinguish between process model instances and can provide valuable context when troubleshooting a process model that is misbehaving.

Scope

Services

Below is a list of services you would expect to see from a partner when proposing to manage your project. The full list may not apply in all project scenarios:

Agile Project Management
Stakeholder Management
Requirements Management
Configuration and Development
Data Management
Architecture, Infrastructure Support, and System Administration

Functional requirements

High-level description statements of system functionality, in support of the objectives specified in the prior sections. Note that Appian does not recommend using detailed requirements documents (eg. BRUF), but instead high-level objectives which support an agile requirements process.
Supported business processes, including providing business process flow diagrams.
System Personas, including high-level descriptions of how the personas will use the application and the number of anticipated users by persona.
User Interfaces, Appian Sites, Reports, and Generated Documents, including high-level descriptions, estimated or expected quantities and complexities.
Integrations, including descriptions, methods (e.g. file, e-mail, messaging, database connection, etc.), data volumes, interface flows, data specifications, and formats.
Document Management, including the types and formats of stored documents and the anticipated document sizes and volumes.

For the full list of functional requirements, see the downloadable ebook.

Non-functional requirements

Similar to the Functional Requirements, the Non-Functional Requirements will help formulate an accurate proposal and cost estimate for the in-scope solution.

Identify technical environments for pre-production and production. State the partner’s responsibility for infrastructure/network engineering, configuration documentation, hardware, network, and software installation support and/or administration.
Continuous Integration/Continuous Deployment (CI/ CD) pipeline requirements, including automated testing, automated deployment, software version control, etc.
Technical standards, enterprise architecture standards, and governance processes and review requirements.
Performance requirements, including peak concurrent users, total user counts, application response times, anticipated data volumes etc.
User experience standards and user interface requirements.
System Service Level Agreement (SLAs) requirements.

For the full list of non-functional requirements, see the downloadable ebook.

Team Requirements

Role	Qualifications
Team/Delivery Manager	Appian Certified Analyst (or higher) Recommended 18+ months of active Appian project experience Agile project management certification (eg. SAFe Certification, PgMP and/or PMP)
Architect	Appian Certified Lead Developer Recommended 3-4 years of active Appian project experience Certified Scrum Master or equivalent certification
Lead Developer	Appian Certified Lead Developer Recommended 2-3 years of active Appian project experience Certified Scrum Master or equivalent certification
Low Code Developers	Appian Certified Senior Developer Junior team members- Appian Certified Associate Developer
Analysts and/or Testers	Appian Certified Analyst Note: These roles can be performed by Appian developers rather than specialists
UI/UX Engineers (optional)	Appian Certified Associate Developer Appian Pro UX Badge (Coming Soon) Implementing SAFe Certification Note: These roles can be performed by Appian developers rather than specialists

Project level resourcing

Appian Project Delivery Best Practices

Appian suggests that the following best practices be specified as part of a contract:

The delivery partner will implement the solution using only out-of-the-box Appian platform features and functionality unless otherwise confirmed by an Appian Architect.
Appian Health Check should be scheduled to automatically run every increment in all non-production environments. All the new high-risk findings must be addressed before the increment ends. Other findings should be added to the product backlog and prioritized along with other backlog items. The list of findings includes but is not limited to: failures to adhere to design best practices, performance issues, process sizing, system resource utilization, etc.
Appian Health Check should also be scheduled to automatically run every month in the production environment. All high-risk findings must be prioritized for remediation in the following increment and addressed before the next production deployment. Add other findings to the product backlog and prioritize along with other backlog items.
Architectural reviews and configuration peer reviews will be conducted as part of the implementation. The Senior Appian Designer or Appian Architect will validate that the implemented configurations adhere to the agreed-upon architectural direction and meet technical requirements. During Peer Reviews, the Designers, the Senior Appian Designer and/or Appian Architect review individual configurations ensuring that best practices are followed and that the solution will perform as required. For more information, please review Appian’s best practice readiness checks and application reviews.
All User Interfaces must follow Appian’s published UX Design Guide. The Appian Architect should ensure compliance against a project tailored User Interface Style Guide for all applications in the Appian platform.
The partner will create a high-level system design that describes process, data, integrations, and security for the system’s future state. The system architecture will describe the functional design of the system at a high level. This description will include key news events, tasks, records, reports, and actions
The partner will proactively collaborate with the stakeholder community to ensure that the project direction, requirements, and designs are aligned to the stakeholder’s vision and business needs. As required, the partner will use techniques to collaborate on and confirm direction including developing prototypes as necessary.
The partner will allow project stakeholders to provide feedback, and will gain on-going approval for completed product features.
The partner will collect system performance requirements and develop and execute automated performance testing scripts. Performance testing activities will be planned to occur throughout the delivery of the project life cycle, ensuring that issues are identified and corrected early.

Download full article e-book

community.appian.com/.../Right_5F00_Appian_5F00_Delivery_5F00_Partner_5F00_WP_5F00_Final.pdf

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 18:36:49 GMT

Revision 11 posted to Article by joel.larin on 1/9/2024 6:36:49 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

By default, new processes in Appian have the same process display name as the process model object. This makes it difficult to differentiate between process instances when troubleshooting.

Dynamic display names make it easier to distinguish between process model instances and can provide valuable context when troubleshooting a process model that is misbehaving.

Scope

Services

Below is a list of services you would expect to see from a partner when proposing to manage your project. The full list may not apply in all project scenarios:

Agile Project Management
Stakeholder Management
Requirements Management
Configuration and Development
Data Management
Architecture, Infrastructure Support, and System Administration

Functional requirements

High-level description statements of system functionality, in support of the objectives specified in the prior sections. Note that Appian does not recommend using detailed requirements documents (eg. BRUF), but instead high-level objectives which support an agile requirements process.
Supported business processes, including providing business process flow diagrams.
System Personas, including high-level descriptions of how the personas will use the application and the number of anticipated users by persona.
User Interfaces, Appian Sites, Reports, and Generated Documents, including high-level descriptions, estimated or expected quantities and complexities.
Integrations, including descriptions, methods (e.g. file, e-mail, messaging, database connection, etc.), data volumes, interface flows, data specifications, and formats.
Document Management, including the types and formats of stored documents and the anticipated document sizes and volumes.

For the full list of functional requirements, see the downloadable ebook.

Non-functional requirements

Similar to the Functional Requirements, the Non-Functional Requirements will help formulate an accurate proposal and cost estimate for the in-scope solution.

Identify technical environments for pre-production and production. State the partner’s responsibility for infrastructure/network engineering, configuration documentation, hardware, network, and software installation support and/or administration.
Continuous Integration/Continuous Deployment (CI/ CD) pipeline requirements, including automated testing, automated deployment, software version control, etc.
Technical standards, enterprise architecture standards, and governance processes and review requirements.
Performance requirements, including peak concurrent users, total user counts, application response times, anticipated data volumes etc.
User experience standards and user interface requirements.
System Service Level Agreement (SLAs) requirements.

For the full list of non-functional requirements, see the downloadable ebook.

Team Requirements

Role	Qualifications
Team/Delivery Manager	Appian Certified Analyst (or higher) Recommended 18+ months of active Appian project experience Agile project management certification (eg. SAFe Certification, PgMP and/or PMP)
Architect	Appian Certified Lead Developer Recommended 3-4 years of active Appian project experience Certified Scrum Master or equivalent certification
Lead Developer	Appian Certified Lead Developer Recommended 2-3 years of active Appian project experience Certified Scrum Master or equivalent certification
Low Code Developers	Appian Certified Senior Developer Junior team members- Appian Certified Associate Developer
Analysts and/or Testers	Appian Certified Analyst Note: These roles can be performed by Appian developers rather than specialists
UI/UX Engineers (optional)	Appian Certified Associate Developer Appian Pro UX Badge (Coming Soon) Implementing SAFe Certification Note: These roles can be performed by Appian developers rather than specialists

Project level resourcing

Appian Project Delivery Best Practices

Appian suggests that the following best practices be specified as part of a contract:

The delivery partner will implement the solution using only out-of-the-box Appian platform features and functionality unless otherwise confirmed by an Appian Architect.
Appian Health Check should be scheduled to automatically run every increment in all non-production environments. All the new high-risk findings must be addressed before the increment ends. Other findings should be added to the product backlog and prioritized along with other backlog items. The list of findings includes but is not limited to: failures to adhere to design best practices, performance issues, process sizing, system resource utilization, etc.
Appian Health Check should also be scheduled to automatically run every month in the production environment. All high-risk findings must be prioritized for remediation in the following increment and addressed before the next production deployment. Add other findings to the product backlog and prioritize along with other backlog items.
Architectural reviews and configuration peer reviews will be conducted as part of the implementation. The Senior Appian Designer or Appian Architect will validate that the implemented configurations adhere to the agreed-upon architectural direction and meet technical requirements. During Peer Reviews, the Designers, the Senior Appian Designer and/or Appian Architect review individual configurations ensuring that best practices are followed and that the solution will perform as required. For more information, please review Appian’s best practice readiness checks and application reviews.
All User Interfaces must follow Appian’s published UX Design Guide. The Appian Architect should ensure compliance against a project tailored User Interface Style Guide for all applications in the Appian platform.
The partner will create a high-level system design that describes process, data, integrations, and security for the system’s future state. The system architecture will describe the functional design of the system at a high level. This description will include key news events, tasks, records, reports, and actions
The partner will proactively collaborate with the stakeholder community to ensure that the project direction, requirements, and designs are aligned to the stakeholder’s vision and business needs. As required, the partner will use techniques to collaborate on and confirm direction including developing prototypes as necessary.
The partner will allow project stakeholders to provide feedback, and will gain on-going approval for completed product features.
The partner will collect system performance requirements and develop and execute automated performance testing scripts. Performance testing activities will be planned to occur throughout the delivery of the project life cycle, ensuring that issues are identified and corrected early.

Download full article e-book

community.appian.com/.../Right_5F00_Appian_5F00_Delivery_5F00_Partner_5F00_WP_5F00_Final.pdf

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 18:33:11 GMT

Revision 10 posted to Article by joel.larin on 1/9/2024 6:33:11 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

This section provides organizations with guidance on submitting effective RFPs to delivery partners for Appian projects or programs. It is intended to assist in providing the delivery partner with clear scoping statements, standardized task(s), personnel, and deliverable requirements for agile-based development on the Appian platform. Organizations should tailor and adapt this guidance to the specific vision for each Appian implementation contract and adjust on a project-by-project basis.

Scope

Services

Below is a list of services you would expect to see from a partner when proposing to manage your project. The full list may not apply in all project scenarios:

Agile Project Management
Stakeholder Management
Requirements Management
Configuration and Development
Data Management
Architecture, Infrastructure Support, and System Administration

Functional requirements

High-level description statements of system functionality, in support of the objectives specified in the prior sections. Note that Appian does not recommend using detailed requirements documents (eg. BRUF), but instead high-level objectives which support an agile requirements process.
Supported business processes, including providing business process flow diagrams.
System Personas, including high-level descriptions of how the personas will use the application and the number of anticipated users by persona.
User Interfaces, Appian Sites, Reports, and Generated Documents, including high-level descriptions, estimated or expected quantities and complexities.
Integrations, including descriptions, methods (e.g. file, e-mail, messaging, database connection, etc.), data volumes, interface flows, data specifications, and formats.
Document Management, including the types and formats of stored documents and the anticipated document sizes and volumes.

For the full list of functional requirements, see the downloadable ebook.

Non-functional requirements

Similar to the Functional Requirements, the Non-Functional Requirements will help formulate an accurate proposal and cost estimate for the in-scope solution.

Identify technical environments for pre-production and production. State the partner’s responsibility for infrastructure/network engineering, configuration documentation, hardware, network, and software installation support and/or administration.
Continuous Integration/Continuous Deployment (CI/ CD) pipeline requirements, including automated testing, automated deployment, software version control, etc.
Technical standards, enterprise architecture standards, and governance processes and review requirements.
Performance requirements, including peak concurrent users, total user counts, application response times, anticipated data volumes etc.
User experience standards and user interface requirements.
System Service Level Agreement (SLAs) requirements.

For the full list of non-functional requirements, see the downloadable ebook.

Team Requirements

Role	Qualifications
Team/Delivery Manager	Appian Certified Analyst (or higher) Recommended 18+ months of active Appian project experience Agile project management certification (eg. SAFe Certification, PgMP and/or PMP)
Architect	Appian Certified Lead Developer Recommended 3-4 years of active Appian project experience Certified Scrum Master or equivalent certification
Lead Developer	Appian Certified Lead Developer Recommended 2-3 years of active Appian project experience Certified Scrum Master or equivalent certification
Low Code Developers	Appian Certified Senior Developer Junior team members- Appian Certified Associate Developer
Analysts and/or Testers	Appian Certified Analyst Note: These roles can be performed by Appian developers rather than specialists
UI/UX Engineers (optional)	Appian Certified Associate Developer Appian Pro UX Badge (Coming Soon) Implementing SAFe Certification Note: These roles can be performed by Appian developers rather than specialists

Project level resourcing

Appian Project Delivery Best Practices

Appian suggests that the following best practices be specified as part of a contract:

The delivery partner will implement the solution using only out-of-the-box Appian platform features and functionality unless otherwise confirmed by an Appian Architect.
Appian Health Check should be scheduled to automatically run every increment in all non-production environments. All the new high-risk findings must be addressed before the increment ends. Other findings should be added to the product backlog and prioritized along with other backlog items. The list of findings includes but is not limited to: failures to adhere to design best practices, performance issues, process sizing, system resource utilization, etc.
Appian Health Check should also be scheduled to automatically run every month in the production environment. All high-risk findings must be prioritized for remediation in the following increment and addressed before the next production deployment. Add other findings to the product backlog and prioritize along with other backlog items.
Architectural reviews and configuration peer reviews will be conducted as part of the implementation. The Senior Appian Designer or Appian Architect will validate that the implemented configurations adhere to the agreed-upon architectural direction and meet technical requirements. During Peer Reviews, the Designers, the Senior Appian Designer and/or Appian Architect review individual configurations ensuring that best practices are followed and that the solution will perform as required. For more information, please review Appian’s best practice readiness checks and application reviews.
All User Interfaces must follow Appian’s published UX Design Guide. The Appian Architect should ensure compliance against a project tailored User Interface Style Guide for all applications in the Appian platform.
The partner will create a high-level system design that describes process, data, integrations, and security for the system’s future state. The system architecture will describe the functional design of the system at a high level. This description will include key news events, tasks, records, reports, and actions
The partner will proactively collaborate with the stakeholder community to ensure that the project direction, requirements, and designs are aligned to the stakeholder’s vision and business needs. As required, the partner will use techniques to collaborate on and confirm direction including developing prototypes as necessary.
The partner will allow project stakeholders to provide feedback, and will gain on-going approval for completed product features.
The partner will collect system performance requirements and develop and execute automated performance testing scripts. Performance testing activities will be planned to occur throughout the delivery of the project life cycle, ensuring that issues are identified and corrected early.

Download full article e-book

community.appian.com/.../Right_5F00_Appian_5F00_Delivery_5F00_Partner_5F00_WP_5F00_Final.pdf

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 18:31:55 GMT

Revision 9 posted to Article by joel.larin on 1/9/2024 6:31:55 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

Scope

Services

Below is a list of services you would expect to see from a partner when proposing to manage your project. The full list may not apply in all project scenarios:

Agile Project Management
Stakeholder Management
Requirements Management
Configuration and Development
Data Management
Architecture, Infrastructure Support, and System Administration

Functional requirements

High-level description statements of system functionality, in support of the objectives specified in the prior sections. Note that Appian does not recommend using detailed requirements documents (eg. BRUF), but instead high-level objectives which support an agile requirements process.
Supported business processes, including providing business process flow diagrams.
System Personas, including high-level descriptions of how the personas will use the application and the number of anticipated users by persona.
User Interfaces, Appian Sites, Reports, and Generated Documents, including high-level descriptions, estimated or expected quantities and complexities.
Integrations, including descriptions, methods (e.g. file, e-mail, messaging, database connection, etc.), data volumes, interface flows, data specifications, and formats.
Document Management, including the types and formats of stored documents and the anticipated document sizes and volumes.

For the full list of functional requirements, see the downloadable ebook.

Non-functional requirements

Similar to the Functional Requirements, the Non-Functional Requirements will help formulate an accurate proposal and cost estimate for the in-scope solution.

Identify technical environments for pre-production and production. State the partner’s responsibility for infrastructure/network engineering, configuration documentation, hardware, network, and software installation support and/or administration.
Continuous Integration/Continuous Deployment (CI/ CD) pipeline requirements, including automated testing, automated deployment, software version control, etc.
Technical standards, enterprise architecture standards, and governance processes and review requirements.
Performance requirements, including peak concurrent users, total user counts, application response times, anticipated data volumes etc.
User experience standards and user interface requirements.
System Service Level Agreement (SLAs) requirements.

For the full list of non-functional requirements, see the downloadable ebook.

Team Requirements

Role	Qualifications
Team/Delivery Manager	Appian Certified Analyst (or higher) Recommended 18+ months of active Appian project experience Agile project management certification (eg. SAFe Certification, PgMP and/or PMP)
Architect	Appian Certified Lead Developer Recommended 3-4 years of active Appian project experience Certified Scrum Master or equivalent certification
Lead Developer	Appian Certified Lead Developer Recommended 2-3 years of active Appian project experience Certified Scrum Master or equivalent certification
Low Code Developers	Appian Certified Senior Developer Junior team members- Appian Certified Associate Developer
Analysts and/or Testers	Appian Certified Analyst Note: These roles can be performed by Appian developers rather than specialists
UI/UX Engineers (optional)	Appian Certified Associate Developer Appian Pro UX Badge (Coming Soon) Implementing SAFe Certification Note: These roles can be performed by Appian developers rather than specialists

Project level resourcing

Appian Project Delivery Best Practices

Appian suggests that the following best practices be specified as part of a contract:

The delivery partner will implement the solution using only out-of-the-box Appian platform features and functionality unless otherwise confirmed by an Appian Architect.
Appian Health Check should be scheduled to automatically run every increment in all non-production environments. All the new high-risk findings must be addressed before the increment ends. Other findings should be added to the product backlog and prioritized along with other backlog items. The list of findings includes but is not limited to: failures to adhere to design best practices, performance issues, process sizing, system resource utilization, etc.
Appian Health Check should also be scheduled to automatically run every month in the production environment. All high-risk findings must be prioritized for remediation in the following increment and addressed before the next production deployment. Add other findings to the product backlog and prioritize along with other backlog items.
Architectural reviews and configuration peer reviews will be conducted as part of the implementation. The Senior Appian Designer or Appian Architect will validate that the implemented configurations adhere to the agreed-upon architectural direction and meet technical requirements. During Peer Reviews, the Designers, the Senior Appian Designer and/or Appian Architect review individual configurations ensuring that best practices are followed and that the solution will perform as required. For more information, please review Appian’s best practice readiness checks and application reviews.
All User Interfaces must follow Appian’s published UX Design Guide. The Appian Architect should ensure compliance against a project tailored User Interface Style Guide for all applications in the Appian platform.
The partner will create a high-level system design that describes process, data, integrations, and security for the system’s future state. The system architecture will describe the functional design of the system at a high level. This description will include key news events, tasks, records, reports, and actions
The partner will proactively collaborate with the stakeholder community to ensure that the project direction, requirements, and designs are aligned to the stakeholder’s vision and business needs. As required, the partner will use techniques to collaborate on and confirm direction including developing prototypes as necessary.
The partner will allow project stakeholders to provide feedback, and will gain on-going approval for completed product features.
The partner will collect system performance requirements and develop and execute automated performance testing scripts. Performance testing activities will be planned to occur throughout the delivery of the project life cycle, ensuring that issues are identified and corrected early.

Download full article e-book

community.appian.com/.../Right_5F00_Appian_5F00_Delivery_5F00_Partner_5F00_WP_5F00_Final.pdf

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 18:30:53 GMT

Revision 8 posted to Article by joel.larin on 1/9/2024 6:30:53 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

Scope

Services

Below is a list of services you would expect to see from a partner when proposing to manage your project. The full list may not apply in all project scenarios:

Agile Project Management
Stakeholder Management
Requirements Management
Configuration and Development
Data Management
Architecture, Infrastructure Support, and System Administration

Functional requirements

High-level description statements of system functionality, in support of the objectives specified in the prior sections. Note that Appian does not recommend using detailed requirements documents (eg. BRUF), but instead high-level objectives which support an agile requirements process.
Supported business processes, including providing business process flow diagrams.
System Personas, including high-level descriptions of how the personas will use the application and the number of anticipated users by persona.
User Interfaces, Appian Sites, Reports, and Generated Documents, including high-level descriptions, estimated or expected quantities and complexities.
Integrations, including descriptions, methods (e.g. file, e-mail, messaging, database connection, etc.), data volumes, interface flows, data specifications, and formats.
Document Management, including the types and formats of stored documents and the anticipated document sizes and volumes.

For the full list of functional requirements, see the downloadable ebook.

Non-functional requirements

Similar to the Functional Requirements, the Non-Functional Requirements will help formulate an accurate proposal and cost estimate for the in-scope solution.

Identify technical environments for pre-production and production. State the partner’s responsibility for infrastructure/network engineering, configuration documentation, hardware, network, and software installation support and/or administration.
Continuous Integration/Continuous Deployment (CI/ CD) pipeline requirements, including automated testing, automated deployment, software version control, etc.
Technical standards, enterprise architecture standards, and governance processes and review requirements.
Performance requirements, including peak concurrent users, total user counts, application response times, anticipated data volumes etc.
User experience standards and user interface requirements.
System Service Level Agreement (SLAs) requirements.

For the full list of non-functional requirements, see the downloadable ebook.

Team Requirements

Role	Qualifications
Team/Delivery Manager	Appian Certified Analyst (or higher) Recommended 18+ months of active Appian project experience Agile project management certification (eg. SAFe Certification, PgMP and/or PMP)
Architect	Appian Certified Lead Developer Recommended 3-4 years of active Appian project experience Certified Scrum Master or equivalent certification
Lead Developer	Appian Certified Lead Developer Recommended 2-3 years of active Appian project experience Certified Scrum Master or equivalent certification
Low Code Developers	Appian Certified Senior Developer Junior team members- Appian Certified Associate Developer
Analysts and/or Testers	Appian Certified Analyst Note: These roles can be performed by Appian developers rather than specialists
UI/UX Engineers (optional)	Appian Certified Associate Developer Appian Pro UX Badge (Coming Soon) Implementing SAFe Certification Note: These roles can be performed by Appian developers rather than specialists

Project level resourcing

Appian Project Delivery Best Practices

Appian suggests that the following best practices be specified as part of a contract:

The delivery partner will implement the solution using only out-of-the-box Appian platform features and functionality unless otherwise confirmed by an Appian Architect.
Appian Health Check should be scheduled to automatically run every increment in all non-production environments. All the new high-risk findings must be addressed before the increment ends. Other findings should be added to the product backlog and prioritized along with other backlog items. The list of findings includes but is not limited to: failures to adhere to design best practices, performance issues, process sizing, system resource utilization, etc.
Appian Health Check should also be scheduled to automatically run every month in the production environment. All high-risk findings must be prioritized for remediation in the following increment and addressed before the next production deployment. Add other findings to the product backlog and prioritize along with other backlog items.
Architectural reviews and configuration peer reviews will be conducted as part of the implementation. The Senior Appian Designer or Appian Architect will validate that the implemented configurations adhere to the agreed-upon architectural direction and meet technical requirements. During Peer Reviews, the Designers, the Senior Appian Designer and/or Appian Architect review individual configurations ensuring that best practices are followed and that the solution will perform as required. For more information, please review Appian’s best practice readiness checks and application reviews.
All User Interfaces must follow Appian’s published UX Design Guide. The Appian Architect should ensure compliance against a project tailored User Interface Style Guide for all applications in the Appian platform.
The partner will create a high-level system design that describes process, data, integrations, and security for the system’s future state. The system architecture will describe the functional design of the system at a high level. This description will include key news events, tasks, records, reports, and actions
The partner will proactively collaborate with the stakeholder community to ensure that the project direction, requirements, and designs are aligned to the stakeholder’s vision and business needs. As required, the partner will use techniques to collaborate on and confirm direction including developing prototypes as necessary.
The partner will allow project stakeholders to provide feedback, and will gain on-going approval for completed product features.
The partner will collect system performance requirements and develop and execute automated performance testing scripts. Performance testing activities will be planned to occur throughout the delivery of the project life cycle, ensuring that issues are identified and corrected early.

Download full article e-book

community.appian.com/.../Right_5F00_Appian_5F00_Delivery_5F00_Partner_5F00_WP_5F00_Final.pdf

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 18:29:58 GMT

Revision 7 posted to Article by joel.larin on 1/9/2024 6:29:58 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

Scope

Services

Below is a list of services you would expect to see from a partner when proposing to manage your project. The full list may not apply in all project scenarios:

Agile Project Management
Stakeholder Management
Requirements Management
Configuration and Development
Data Management
Architecture, Infrastructure Support, and System Administration

Functional requirements

High-level description statements of system functionality, in support of the objectives specified in the prior sections. Note that Appian does not recommend using detailed requirements documents (eg. BRUF), but instead high-level objectives which support an agile requirements process.
Supported business processes, including providing business process flow diagrams.
System Personas, including high-level descriptions of how the personas will use the application and the number of anticipated users by persona.
User Interfaces, Appian Sites, Reports, and Generated Documents, including high-level descriptions, estimated or expected quantities and complexities.
Integrations, including descriptions, methods (e.g. file, e-mail, messaging, database connection, etc.), data volumes, interface flows, data specifications, and formats.
Document Management, including the types and formats of stored documents and the anticipated document sizes and volumes.

For the full list of functional requirements, see the downloadable ebook.

Non-functional requirements

Similar to the Functional Requirements, the Non-Functional Requirements will help formulate an accurate proposal and cost estimate for the in-scope solution.

Identify technical environments for pre-production and production. State the partner’s responsibility for infrastructure/network engineering, configuration documentation, hardware, network, and software installation support and/or administration.
Continuous Integration/Continuous Deployment (CI/ CD) pipeline requirements, including automated testing, automated deployment, software version control, etc.
Technical standards, enterprise architecture standards, and governance processes and review requirements.
Performance requirements, including peak concurrent users, total user counts, application response times, anticipated data volumes etc.
User experience standards and user interface requirements.
System Service Level Agreement (SLAs) requirements.

For the full list of non-functional requirements, see the downloadable ebook.

Team Requirements

Role	Qualifications
Team/Delivery Manager	Appian Certified Analyst (or higher) Recommended 18+ months of active Appian project experience Agile project management certification (eg. SAFe Certification, PgMP and/or PMP)
Architect	Appian Certified Lead Developer Recommended 3-4 years of active Appian project experience Certified Scrum Master or equivalent certification
Lead Developer	Appian Certified Lead Developer Recommended 2-3 years of active Appian project experience Certified Scrum Master or equivalent certification
Low Code Developers	Appian Certified Senior Developer Junior team members- Appian Certified Associate Developer
Analysts and/or Testers	Appian Certified Analyst Note: These roles can be performed by Appian developers rather than specialists
UI/UX Engineers (optional)	Appian Certified Associate Developer Appian Pro UX Badge (Coming Soon) Implementing SAFe Certification Note: These roles can be performed by Appian developers rather than specialists

Project level resourcing

Appian Project Delivery Best Practices

Appian suggests that the following best practices be specified as part of a contract:

The delivery partner will implement the solution using only out-of-the-box Appian platform features and functionality unless otherwise confirmed by an Appian Architect.
Appian Health Check should be scheduled to automatically run every increment in all non-production environments. All the new high-risk findings must be addressed before the increment ends. Other findings should be added to the product backlog and prioritized along with other backlog items. The list of findings includes but is not limited to: failures to adhere to design best practices, performance issues, process sizing, system resource utilization, etc.
Appian Health Check should also be scheduled to automatically run every month in the production environment. All high-risk findings must be prioritized for remediation in the following increment and addressed before the next production deployment. Add other findings to the product backlog and prioritize along with other backlog items.
Architectural reviews and configuration peer reviews will be conducted as part of the implementation. The Senior Appian Designer or Appian Architect will validate that the implemented configurations adhere to the agreed-upon architectural direction and meet technical requirements. During Peer Reviews, the Designers, the Senior Appian Designer and/or Appian Architect review individual configurations ensuring that best practices are followed and that the solution will perform as required. For more information, please review Appian’s best practice readiness checks and application reviews.
All User Interfaces must follow Appian’s published UX Design Guide. The Appian Architect should ensure compliance against a project tailored User Interface Style Guide for all applications in the Appian platform.
The partner will create a high-level system design that describes process, data, integrations, and security for the system’s future state. The system architecture will describe the functional design of the system at a high level. This description will include key news events, tasks, records, reports, and actions
The partner will proactively collaborate with the stakeholder community to ensure that the project direction, requirements, and designs are aligned to the stakeholder’s vision and business needs. As required, the partner will use techniques to collaborate on and confirm direction including developing prototypes as necessary.
The partner will allow project stakeholders to provide feedback, and will gain on-going approval for completed product features.
The partner will collect system performance requirements and develop and execute automated performance testing scripts. Performance testing activities will be planned to occur throughout the delivery of the project life cycle, ensuring that issues are identified and corrected early.

Download full article e-book

community.appian.com/.../Right_5F00_Appian_5F00_Delivery_5F00_Partner_5F00_WP_5F00_Final.pdf

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 18:28:47 GMT

Revision 6 posted to Article by joel.larin on 1/9/2024 6:28:47 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

Scope

Services

Below is a list of services you would expect to see from a partner when proposing to manage your project. The full list may not apply in all project scenarios:

Agile Project Management
Stakeholder Management
Requirements Management
Configuration and Development
Data Management
Architecture, Infrastructure Support, and System Administration

Functional requirements

High-level description statements of system functionality, in support of the objectives specified in the prior sections. Note that Appian does not recommend using detailed requirements documents (eg. BRUF), but instead high-level objectives which support an agile requirements process.
Supported business processes, including providing business process flow diagrams.
System Personas, including high-level descriptions of how the personas will use the application and the number of anticipated users by persona.
User Interfaces, Appian Sites, Reports, and Generated Documents, including high-level descriptions, estimated or expected quantities and complexities.
Integrations, including descriptions, methods (e.g. file, e-mail, messaging, database connection, etc.), data volumes, interface flows, data specifications, and formats.
Document Management, including the types and formats of stored documents and the anticipated document sizes and volumes.

For the full list of functional requirements, see the downloadable ebook.

Non-functional requirements

Similar to the Functional Requirements, the Non-Functional Requirements will help formulate an accurate proposal and cost estimate for the in-scope solution.

Identify technical environments for pre-production and production. State the partner’s responsibility for infrastructure/network engineering, configuration documentation, hardware, network, and software installation support and/or administration.
Continuous Integration/Continuous Deployment (CI/ CD) pipeline requirements, including automated testing, automated deployment, software version control, etc.
Technical standards, enterprise architecture standards, and governance processes and review requirements.
Performance requirements, including peak concurrent users, total user counts, application response times, anticipated data volumes etc.
User experience standards and user interface requirements.
System Service Level Agreement (SLAs) requirements.

For the full list of non-functional requirements, see the downloadable ebook.

Team Requirements

Role	Qualifications
Team/Delivery Manager	Appian Certified Analyst (or higher) Recommended 18+ months of active Appian project experience Agile project management certification (eg. SAFe Certification, PgMP and/or PMP)
Architect	Appian Certified Lead Developer Recommended 3-4 years of active Appian project experience Certified Scrum Master or equivalent certification
Lead Developer	Appian Certified Lead Developer Recommended 2-3 years of active Appian project experience Certified Scrum Master or equivalent certification
Low Code Developers	Appian Certified Senior Developer Junior team members- Appian Certified Associate Developer
Analysts and/or Testers	Appian Certified Analyst Note: These roles can be performed by Appian developers rather than specialists
UI/UX Engineers (optional)	Appian Certified Associate Developer Appian Pro UX Badge (Coming Soon) Implementing SAFe Certification Note: These roles can be performed by Appian developers rather than specialists

Project level resourcing

Appian Project Delivery Best Practices

Appian suggests that the following best practices be specified as part of a contract:

The delivery partner will implement the solution using only out-of-the-box Appian platform features and functionality unless otherwise confirmed by an Appian Architect.
Appian Health Check should be scheduled to automatically run every increment in all non-production environments. All the new high-risk findings must be addressed before the increment ends. Other findings should be added to the product backlog and prioritized along with other backlog items. The list of findings includes but is not limited to: failures to adhere to design best practices, performance issues, process sizing, system resource utilization, etc.
Appian Health Check should also be scheduled to automatically run every month in the production environment. All high-risk findings must be prioritized for remediation in the following increment and addressed before the next production deployment. Add other findings to the product backlog and prioritize along with other backlog items.
Architectural reviews and configuration peer reviews will be conducted as part of the implementation. The Senior Appian Designer or Appian Architect will validate that the implemented configurations adhere to the agreed-upon architectural direction and meet technical requirements. During Peer Reviews, the Designers, the Senior Appian Designer and/or Appian Architect review individual configurations ensuring that best practices are followed and that the solution will perform as required. For more information, please review Appian’s best practice readiness checks and application reviews.
All User Interfaces must follow Appian’s published UX Design Guide. The Appian Architect should ensure compliance against a project tailored User Interface Style Guide for all applications in the Appian platform.
The partner will create a high-level system design that describes process, data, integrations, and security for the system’s future state. The system architecture will describe the functional design of the system at a high level. This description will include key news events, tasks, records, reports, and actions
The partner will proactively collaborate with the stakeholder community to ensure that the project direction, requirements, and designs are aligned to the stakeholder’s vision and business needs. As required, the partner will use techniques to collaborate on and confirm direction including developing prototypes as necessary.
The partner will allow project stakeholders to provide feedback, and will gain on-going approval for completed product features.
The partner will collect system performance requirements and develop and execute automated performance testing scripts. Performance testing activities will be planned to occur throughout the delivery of the project life cycle, ensuring that issues are identified and corrected early.

Download full article e-book

community.appian.com/.../Right_5F00_Appian_5F00_Delivery_5F00_Partner_5F00_WP_5F00_Final.pdf

Get Started with Process Models

joel.larin — Tue, 09 Jan 2024 18:24:58 GMT

Revision 5 posted to Article by joel.larin on 1/9/2024 6:24:58 PM

Security
Dynamic Display Names
Data management
Alerts

Security

Dynamic Display Names

Scope

Services

Below is a list of services you would expect to see from a partner when proposing to manage your project. The full list may not apply in all project scenarios:

Agile Project Management
Stakeholder Management
Requirements Management
Configuration and Development
Data Management
Architecture, Infrastructure Support, and System Administration

Functional requirements

High-level description statements of system functionality, in support of the objectives specified in the prior sections. Note that Appian does not recommend using detailed requirements documents (eg. BRUF), but instead high-level objectives which support an agile requirements process.
Supported business processes, including providing business process flow diagrams.
System Personas, including high-level descriptions of how the personas will use the application and the number of anticipated users by persona.
User Interfaces, Appian Sites, Reports, and Generated Documents, including high-level descriptions, estimated or expected quantities and complexities.
Integrations, including descriptions, methods (e.g. file, e-mail, messaging, database connection, etc.), data volumes, interface flows, data specifications, and formats.
Document Management, including the types and formats of stored documents and the anticipated document sizes and volumes.

For the full list of functional requirements, see the downloadable ebook.

Non-functional requirements

Similar to the Functional Requirements, the Non-Functional Requirements will help formulate an accurate proposal and cost estimate for the in-scope solution.

Identify technical environments for pre-production and production. State the partner’s responsibility for infrastructure/network engineering, configuration documentation, hardware, network, and software installation support and/or administration.
Continuous Integration/Continuous Deployment (CI/ CD) pipeline requirements, including automated testing, automated deployment, software version control, etc.
Technical standards, enterprise architecture standards, and governance processes and review requirements.
Performance requirements, including peak concurrent users, total user counts, application response times, anticipated data volumes etc.
User experience standards and user interface requirements.
System Service Level Agreement (SLAs) requirements.

For the full list of non-functional requirements, see the downloadable ebook.

Team Requirements

Role	Qualifications
Team/Delivery Manager	Appian Certified Analyst (or higher) Recommended 18+ months of active Appian project experience Agile project management certification (eg. SAFe Certification, PgMP and/or PMP)
Architect	Appian Certified Lead Developer Recommended 3-4 years of active Appian project experience Certified Scrum Master or equivalent certification
Lead Developer	Appian Certified Lead Developer Recommended 2-3 years of active Appian project experience Certified Scrum Master or equivalent certification
Low Code Developers	Appian Certified Senior Developer Junior team members- Appian Certified Associate Developer
Analysts and/or Testers	Appian Certified Analyst Note: These roles can be performed by Appian developers rather than specialists
UI/UX Engineers (optional)	Appian Certified Associate Developer Appian Pro UX Badge (Coming Soon) Implementing SAFe Certification Note: These roles can be performed by Appian developers rather than specialists

Project level resourcing

Appian Project Delivery Best Practices

Appian suggests that the following best practices be specified as part of a contract:

The delivery partner will implement the solution using only out-of-the-box Appian platform features and functionality unless otherwise confirmed by an Appian Architect.
Appian Health Check should be scheduled to automatically run every increment in all non-production environments. All the new high-risk findings must be addressed before the increment ends. Other findings should be added to the product backlog and prioritized along with other backlog items. The list of findings includes but is not limited to: failures to adhere to design best practices, performance issues, process sizing, system resource utilization, etc.
Appian Health Check should also be scheduled to automatically run every month in the production environment. All high-risk findings must be prioritized for remediation in the following increment and addressed before the next production deployment. Add other findings to the product backlog and prioritize along with other backlog items.
Architectural reviews and configuration peer reviews will be conducted as part of the implementation. The Senior Appian Designer or Appian Architect will validate that the implemented configurations adhere to the agreed-upon architectural direction and meet technical requirements. During Peer Reviews, the Designers, the Senior Appian Designer and/or Appian Architect review individual configurations ensuring that best practices are followed and that the solution will perform as required. For more information, please review Appian’s best practice readiness checks and application reviews.
All User Interfaces must follow Appian’s published UX Design Guide. The Appian Architect should ensure compliance against a project tailored User Interface Style Guide for all applications in the Appian platform.
The partner will create a high-level system design that describes process, data, integrations, and security for the system’s future state. The system architecture will describe the functional design of the system at a high level. This description will include key news events, tasks, records, reports, and actions
The partner will proactively collaborate with the stakeholder community to ensure that the project direction, requirements, and designs are aligned to the stakeholder’s vision and business needs. As required, the partner will use techniques to collaborate on and confirm direction including developing prototypes as necessary.
The partner will allow project stakeholders to provide feedback, and will gain on-going approval for completed product features.
The partner will collect system performance requirements and develop and execute automated performance testing scripts. Performance testing activities will be planned to occur throughout the delivery of the project life cycle, ensuring that issues are identified and corrected early.

Download full article e-book

community.appian.com/.../Right_5F00_Appian_5F00_Delivery_5F00_Partner_5F00_WP_5F00_Final.pdf

Get Started with Process Models

joel.larin — Mon, 18 Dec 2023 22:57:55 GMT

Revision 4 posted to Article by joel.larin on 12/18/2023 10:57:55 PM

Whatever the project, aligning the right services, qualifications, and ensuring the partner follows best practices helps set the stage for success. Key factors to consider include:

Does the partner have a clear understanding of my solution requirements and an effective plan for delivery? Successful projects begin with a detailed plan. As part of the contract development process, make sure you have provided sufficient detail on functional and nonfunctional requirements, but in return, make sure the partner has clearly articulated a plan for each phase of project delivery.
Does the partner have the necessary Appian Team requirements (technical and managerial skills) to be successful? When evaluating team resources, organizations should assess the number of years of direct Appian platform and customer domain experience. Always review team resumes and request partner team Appian Certifications to ensure partners can provide qualified personnel.
Does the partner’s delivery plan adhere to Appian delivery best practices? Select delivery partners who understand the best practices for delivering Appian based solutions. Assess the vendor’s approach to integrating and applying best practices within their solution.
Does the partner team have relevant industry/domain expertise and a proven track record of Appian delivery success for similar solutions? Where possible, ask to speak with references within your organization’s industry or domain. Make sure that not just the partner, but the specific individuals on the project team have relevant industry/domain experience. Past performances should also demonstrate not only Appian experience, but also experience with any additional in-scope technologies.

💡Appian Customer Success Support for Projects

Appian Customer Success offers a range of implementation and advisory services that deliver expert guidance and support for all aspects of Appian platform strategy, architecture, design, and delivery. By working closely with both you and your chosen delivery partner, Appian’s Success Services are proven to increase delivery velocity and quality, while reducing implementation risks. Appian’s services can be integrated together and scaled up and down to support stand-alone implementation projects or provide sustained support for large digital transformation programs. For more information, contact your Appian account representative or reach out to the Appian Customer Success team directly.

Contracting Guidance

Scope

Services

Below is a list of services you would expect to see from a partner when proposing to manage your project. The full list may not apply in all project scenarios:

Agile Project Management
Stakeholder Management
Requirements Management
Configuration and Development
Data Management
Architecture, Infrastructure Support, and System Administration

Functional requirements

High-level description statements of system functionality, in support of the objectives specified in the prior sections. Note that Appian does not recommend using detailed requirements documents (eg. BRUF), but instead high-level objectives which support an agile requirements process.
Supported business processes, including providing business process flow diagrams.
System Personas, including high-level descriptions of how the personas will use the application and the number of anticipated users by persona.
User Interfaces, Appian Sites, Reports, and Generated Documents, including high-level descriptions, estimated or expected quantities and complexities.
Integrations, including descriptions, methods (e.g. file, e-mail, messaging, database connection, etc.), data volumes, interface flows, data specifications, and formats.
Document Management, including the types and formats of stored documents and the anticipated document sizes and volumes.

For the full list of functional requirements, see the downloadable ebook.

Non-functional requirements

Similar to the Functional Requirements, the Non-Functional Requirements will help formulate an accurate proposal and cost estimate for the in-scope solution.

Identify technical environments for pre-production and production. State the partner’s responsibility for infrastructure/network engineering, configuration documentation, hardware, network, and software installation support and/or administration.
Continuous Integration/Continuous Deployment (CI/ CD) pipeline requirements, including automated testing, automated deployment, software version control, etc.
Technical standards, enterprise architecture standards, and governance processes and review requirements.
Performance requirements, including peak concurrent users, total user counts, application response times, anticipated data volumes etc.
User experience standards and user interface requirements.
System Service Level Agreement (SLAs) requirements.

For the full list of non-functional requirements, see the downloadable ebook.

Team Requirements

Role	Qualifications
Team/Delivery Manager	Appian Certified Analyst (or higher) Recommended 18+ months of active Appian project experience Agile project management certification (eg. SAFe Certification, PgMP and/or PMP)
Architect	Appian Certified Lead Developer Recommended 3-4 years of active Appian project experience Certified Scrum Master or equivalent certification
Lead Developer	Appian Certified Lead Developer Recommended 2-3 years of active Appian project experience Certified Scrum Master or equivalent certification
Low Code Developers	Appian Certified Senior Developer Junior team members- Appian Certified Associate Developer
Analysts and/or Testers	Appian Certified Analyst Note: These roles can be performed by Appian developers rather than specialists
UI/UX Engineers (optional)	Appian Certified Associate Developer Appian Pro UX Badge (Coming Soon) Implementing SAFe Certification Note: These roles can be performed by Appian developers rather than specialists

Project level resourcing

Appian Project Delivery Best Practices

Appian suggests that the following best practices be specified as part of a contract:

The delivery partner will implement the solution using only out-of-the-box Appian platform features and functionality unless otherwise confirmed by an Appian Architect.
Appian Health Check should be scheduled to automatically run every increment in all non-production environments. All the new high-risk findings must be addressed before the increment ends. Other findings should be added to the product backlog and prioritized along with other backlog items. The list of findings includes but is not limited to: failures to adhere to design best practices, performance issues, process sizing, system resource utilization, etc.
Appian Health Check should also be scheduled to automatically run every month in the production environment. All high-risk findings must be prioritized for remediation in the following increment and addressed before the next production deployment. Add other findings to the product backlog and prioritize along with other backlog items.
Architectural reviews and configuration peer reviews will be conducted as part of the implementation. The Senior Appian Designer or Appian Architect will validate that the implemented configurations adhere to the agreed-upon architectural direction and meet technical requirements. During Peer Reviews, the Designers, the Senior Appian Designer and/or Appian Architect review individual configurations ensuring that best practices are followed and that the solution will perform as required. For more information, please review Appian’s best practice readiness checks and application reviews.
All User Interfaces must follow Appian’s published UX Design Guide. The Appian Architect should ensure compliance against a project tailored User Interface Style Guide for all applications in the Appian platform.
The partner will create a high-level system design that describes process, data, integrations, and security for the system’s future state. The system architecture will describe the functional design of the system at a high level. This description will include key news events, tasks, records, reports, and actions
The partner will proactively collaborate with the stakeholder community to ensure that the project direction, requirements, and designs are aligned to the stakeholder’s vision and business needs. As required, the partner will use techniques to collaborate on and confirm direction including developing prototypes as necessary.
The partner will allow project stakeholders to provide feedback, and will gain on-going approval for completed product features.
The partner will collect system performance requirements and develop and execute automated performance testing scripts. Performance testing activities will be planned to occur throughout the delivery of the project life cycle, ensuring that issues are identified and corrected early.

Download full article e-book

community.appian.com/.../Right_5F00_Appian_5F00_Delivery_5F00_Partner_5F00_WP_5F00_Final.pdf

Get Started with Process Models

joel.larin — Mon, 18 Dec 2023 22:49:12 GMT

Revision 3 posted to Article by joel.larin on 12/18/2023 10:49:12 PM

Whatever the project, aligning the right services, qualifications, and ensuring the partner follows best practices helps set the stage for success. Key factors to consider include:

Does the partner have a clear understanding of my solution requirements and an effective plan for delivery? Successful projects begin with a detailed plan. As part of the contract development process, make sure you have provided sufficient detail on functional and nonfunctional requirements, but in return, make sure the partner has clearly articulated a plan for each phase of project delivery.
Does the partner have the necessary Appian Team requirements (technical and managerial skills) to be successful? When evaluating team resources, organizations should assess the number of years of direct Appian platform and customer domain experience. Always review team resumes and request partner team Appian Certifications to ensure partners can provide qualified personnel.
Does the partner’s delivery plan adhere to Appian delivery best practices? Select delivery partners who understand the best practices for delivering Appian based solutions. Assess the vendor’s approach to integrating and applying best practices within their solution.
Does the partner team have relevant industry/domain expertise and a proven track record of Appian delivery success for similar solutions? Where possible, ask to speak with references within your organization’s industry or domain. Make sure that not just the partner, but the specific individuals on the project team have relevant industry/domain experience. Past performances should also demonstrate not only Appian experience, but also experience with any additional in-scope technologies.

💡Appian Customer Success Support for Projects

Contracting Guidance

Scope

Services

Below is a list of services you would expect to see from a partner when proposing to manage your project. The full list may not apply in all project scenarios:

Agile Project Management
Stakeholder Management
Requirements Management
Configuration and Development
Data Management
Architecture, Infrastructure Support, and System Administration

Functional requirements

High-level description statements of system functionality, in support of the objectives specified in the prior sections. Note that Appian does not recommend using detailed requirements documents (eg. BRUF), but instead high-level objectives which support an agile requirements process.
Supported business processes, including providing business process flow diagrams.
System Personas, including high-level descriptions of how the personas will use the application and the number of anticipated users by persona.
User Interfaces, Appian Sites, Reports, and Generated Documents, including high-level descriptions, estimated or expected quantities and complexities.
Integrations, including descriptions, methods (e.g. file, e-mail, messaging, database connection, etc.), data volumes, interface flows, data specifications, and formats.
Document Management, including the types and formats of stored documents and the anticipated document sizes and volumes.

For the full list of functional requirements, see the downloadable ebook.

Non-functional requirements

Similar to the Functional Requirements, the Non-Functional Requirements will help formulate an accurate proposal and cost estimate for the in-scope solution.

Identify technical environments for pre-production and production. State the partner’s responsibility for infrastructure/network engineering, configuration documentation, hardware, network, and software installation support and/or administration.
Continuous Integration/Continuous Deployment (CI/ CD) pipeline requirements, including automated testing, automated deployment, software version control, etc.
Technical standards, enterprise architecture standards, and governance processes and review requirements.
Performance requirements, including peak concurrent users, total user counts, application response times, anticipated data volumes etc.
User experience standards and user interface requirements.
System Service Level Agreement (SLAs) requirements.

For the full list of non-functional requirements, see the downloadable ebook.

Team Requirements

Role	Qualifications
Team/Delivery Manager	Appian Certified Analyst (or higher) Recommended 18+ months of active Appian project experience Agile project management certification (eg. SAFe Certification, PgMP and/or PMP)
Architect	Appian Certified Lead Developer Recommended 3-4 years of active Appian project experience Certified Scrum Master or equivalent certification
Lead Developer	Appian Certified Lead Developer Recommended 2-3 years of active Appian project experience Certified Scrum Master or equivalent certification
Low Code Developers	Appian Certified Senior Developer Junior team members- Appian Certified Associate Developer
Analysts and/or Testers	Appian Certified Analyst Note: These roles can be performed by Appian developers rather than specialists
UI/UX Engineers (optional)	Appian Certified Associate Developer Appian Pro UX Badge (Coming Soon) Implementing SAFe Certification Note: These roles can be performed by Appian developers rather than specialists

Project level resourcing

Appian Project Delivery Best Practices

Appian suggests that the following best practices be specified as part of a contract:

The delivery partner will implement the solution using only out-of-the-box Appian platform features and functionality unless otherwise confirmed by an Appian Architect.
Appian Health Check should be scheduled to automatically run every increment in all non-production environments. All the new high-risk findings must be addressed before the increment ends. Other findings should be added to the product backlog and prioritized along with other backlog items. The list of findings includes but is not limited to: failures to adhere to design best practices, performance issues, process sizing, system resource utilization, etc.
Appian Health Check should also be scheduled to automatically run every month in the production environment. All high-risk findings must be prioritized for remediation in the following increment and addressed before the next production deployment. Add other findings to the product backlog and prioritize along with other backlog items.
Architectural reviews and configuration peer reviews will be conducted as part of the implementation. The Senior Appian Designer or Appian Architect will validate that the implemented configurations adhere to the agreed-upon architectural direction and meet technical requirements. During Peer Reviews, the Designers, the Senior Appian Designer and/or Appian Architect review individual configurations ensuring that best practices are followed and that the solution will perform as required. For more information, please review Appian’s best practice readiness checks and application reviews.
All User Interfaces must follow Appian’s published UX Design Guide. The Appian Architect should ensure compliance against a project tailored User Interface Style Guide for all applications in the Appian platform.
The partner will create a high-level system design that describes process, data, integrations, and security for the system’s future state. The system architecture will describe the functional design of the system at a high level. This description will include key news events, tasks, records, reports, and actions
The partner will proactively collaborate with the stakeholder community to ensure that the project direction, requirements, and designs are aligned to the stakeholder’s vision and business needs. As required, the partner will use techniques to collaborate on and confirm direction including developing prototypes as necessary.
The partner will allow project stakeholders to provide feedback, and will gain on-going approval for completed product features.
The partner will collect system performance requirements and develop and execute automated performance testing scripts. Performance testing activities will be planned to occur throughout the delivery of the project life cycle, ensuring that issues are identified and corrected early.

Download full article e-book

community.appian.com/.../Right_5F00_Appian_5F00_Delivery_5F00_Partner_5F00_WP_5F00_Final.pdf

Get Started with Process Models

joel.larin — Mon, 18 Dec 2023 22:48:01 GMT

Revision 2 posted to Article by joel.larin on 12/18/2023 10:48:01 PM

Whatever the project, aligning the right services, qualifications, and ensuring the partner follows best practices helps set the stage for success. Key factors to consider include:

Does the partner have a clear understanding of my solution requirements and an effective plan for delivery? Successful projects begin with a detailed plan. As part of the contract development process, make sure you have provided sufficient detail on functional and nonfunctional requirements, but in return, make sure the partner has clearly articulated a plan for each phase of project delivery.
Does the partner have the necessary Appian Team requirements (technical and managerial skills) to be successful? When evaluating team resources, organizations should assess the number of years of direct Appian platform and customer domain experience. Always review team resumes and request partner team Appian Certifications to ensure partners can provide qualified personnel.
Does the partner’s delivery plan adhere to Appian delivery best practices? Select delivery partners who understand the best practices for delivering Appian based solutions. Assess the vendor’s approach to integrating and applying best practices within their solution.
Does the partner team have relevant industry/domain expertise and a proven track record of Appian delivery success for similar solutions? Where possible, ask to speak with references within your organization’s industry or domain. Make sure that not just the partner, but the specific individuals on the project team have relevant industry/domain experience. Past performances should also demonstrate not only Appian experience, but also experience with any additional in-scope technologies.

💡Appian Customer Success Support for Projects

Contracting Guidance

Scope

Services

Below is a list of services you would expect to see from a partner when proposing to manage your project. The full list may not apply in all project scenarios:

Agile Project Management
Stakeholder Management
Requirements Management
Configuration and Development
Data Management
Architecture, Infrastructure Support, and System Administration

Functional requirements

High-level description statements of system functionality, in support of the objectives specified in the prior sections. Note that Appian does not recommend using detailed requirements documents (eg. BRUF), but instead high-level objectives which support an agile requirements process.
Supported business processes, including providing business process flow diagrams.
System Personas, including high-level descriptions of how the personas will use the application and the number of anticipated users by persona.
User Interfaces, Appian Sites, Reports, and Generated Documents, including high-level descriptions, estimated or expected quantities and complexities.
Integrations, including descriptions, methods (e.g. file, e-mail, messaging, database connection, etc.), data volumes, interface flows, data specifications, and formats.
Document Management, including the types and formats of stored documents and the anticipated document sizes and volumes.

For the full list of functional requirements, see the downloadable ebook.

Non-functional requirements

Similar to the Functional Requirements, the Non-Functional Requirements will help formulate an accurate proposal and cost estimate for the in-scope solution.

Identify technical environments for pre-production and production. State the partner’s responsibility for infrastructure/network engineering, configuration documentation, hardware, network, and software installation support and/or administration.
Continuous Integration/Continuous Deployment (CI/ CD) pipeline requirements, including automated testing, automated deployment, software version control, etc.
Technical standards, enterprise architecture standards, and governance processes and review requirements.
Performance requirements, including peak concurrent users, total user counts, application response times, anticipated data volumes etc.
User experience standards and user interface requirements.
System Service Level Agreement (SLAs) requirements.

For the full list of non-functional requirements, see the downloadable ebook.

Team Requirements

Role	Qualifications
Team/Delivery Manager	Appian Certified Analyst (or higher) Recommended 18+ months of active Appian project experience Agile project management certification (eg. SAFe Certification, PgMP and/or PMP)
Architect	Appian Certified Lead Developer Recommended 3-4 years of active Appian project experience Certified Scrum Master or equivalent certification
Lead Developer	Appian Certified Lead Developer Recommended 2-3 years of active Appian project experience Certified Scrum Master or equivalent certification
Low Code Developers	Appian Certified Senior Developer Junior team members- Appian Certified Associate Developer
Analysts and/or Testers	Appian Certified Analyst Note: These roles can be performed by Appian developers rather than specialists
UI/UX Engineers (optional)	Appian Certified Associate Developer Appian Pro UX Badge (Coming Soon) Implementing SAFe Certification Note: These roles can be performed by Appian developers rather than specialists

Project level resourcing

Appian Project Delivery Best Practices

Appian suggests that the following best practices be specified as part of a contract:

The delivery partner will implement the solution using only out-of-the-box Appian platform features and functionality unless otherwise confirmed by an Appian Architect.
Appian Health Check should be scheduled to automatically run every increment in all non-production environments. All the new high-risk findings must be addressed before the increment ends. Other findings should be added to the product backlog and prioritized along with other backlog items. The list of findings includes but is not limited to: failures to adhere to design best practices, performance issues, process sizing, system resource utilization, etc.
Appian Health Check should also be scheduled to automatically run every month in the production environment. All high-risk findings must be prioritized for remediation in the following increment and addressed before the next production deployment. Add other findings to the product backlog and prioritize along with other backlog items.
Architectural reviews and configuration peer reviews will be conducted as part of the implementation. The Senior Appian Designer or Appian Architect will validate that the implemented configurations adhere to the agreed-upon architectural direction and meet technical requirements. During Peer Reviews, the Designers, the Senior Appian Designer and/or Appian Architect review individual configurations ensuring that best practices are followed and that the solution will perform as required. For more information, please review Appian’s best practice readiness checks and application reviews.
All User Interfaces must follow Appian’s published UX Design Guide. The Appian Architect should ensure compliance against a project tailored User Interface Style Guide for all applications in the Appian platform.
The partner will create a high-level system design that describes process, data, integrations, and security for the system’s future state. The system architecture will describe the functional design of the system at a high level. This description will include key news events, tasks, records, reports, and actions
The partner will proactively collaborate with the stakeholder community to ensure that the project direction, requirements, and designs are aligned to the stakeholder’s vision and business needs. As required, the partner will use techniques to collaborate on and confirm direction including developing prototypes as necessary.
The partner will allow project stakeholders to provide feedback, and will gain on-going approval for completed product features.
The partner will collect system performance requirements and develop and execute automated performance testing scripts. Performance testing activities will be planned to occur throughout the delivery of the project life cycle, ensuring that issues are identified and corrected early.

Download full article e-book

community.appian.com/.../Right_5F00_Appian_5F00_Delivery_5F00_Partner_5F00_WP_5F00_Final.pdf

Get Started with Process Models

joel.larin — Wed, 01 Nov 2023 14:59:04 GMT

Revision 1 posted to Article by joel.larin on 11/1/2023 2:59:04 PM

fdasf

Get Started with Process Models

Get Started with Process Models

Security

Dynamic Display Names

Data Management

Alerts

Get Started with Process Models

Security

Dynamic Display Names

Data Management

Alerts

Get Started with Process Models

Security

Dynamic Display Names

Data Management

Alerts

Get Started with Process Models

Security

Dynamic Display Names

Data Management

Alerts

Get Started with Process Models

Security

Dynamic Display Names

Data Management

Alerts

Get Started with Process Models

Security

Dynamic Display Names

Data Management

Alerts

Get Started with Process Models

Security

Dynamic Display Names

Data Management

Alerts

Get Started with Process Models

Security

Dynamic Display Names

Data Management

Get Started with Process Models

Security

Dynamic Display Names

Scope

Services

Functional requirements

Non-functional requirements

Team Requirements

Role

Qualifications

Team/Delivery Manager

Architect

Lead Developer

Low Code Developers

Analysts and/or Testers

UI/UX Engineers (optional)

Project level resourcing

Appian Project Delivery Best Practices

Download full article e-book

Get Started with Process Models

Security

Dynamic Display Names

Scope

Services

Functional requirements

Non-functional requirements

Team Requirements

Role

Qualifications

Team/Delivery Manager

Architect

Lead Developer

Low Code Developers

Analysts and/or Testers

UI/UX Engineers (optional)

Project level resourcing

Appian Project Delivery Best Practices

Download full article e-book

Get Started with Process Models

Security