How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:55:40 GMT

Current Revision posted to Guide by Appian Max Team on 5/31/2024 6:55:40 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Understand the ‘Team of 3’ structure and its relevance to Appian projects
Define a T-shaped profile and how it applies to Appian development
Recognize common Appian developer speciality areas
Learn how Citizen Development can help non-technical roles contribute to Appian development

Holistic Software Development

In Appian, developers use visual tools to construct applications from pre-built components rather than developing in a traditional coding language. The platform includes tools for creating interfaces, business rules, process flows, data and integrations with external systems. While in a traditional development approach each of these aspects would be created by a specialized developer, with Appian developers are expected to be interdisciplinary capable of creating any/all aspects of an intended application.

This paradigm shift means that your developers no longer need to solely focus on technical depth to build architecturally sound applications. While technical acumen is beneficial, it’s far more important to hire individuals with a good mix of business analysis and technical skills and an appetite for learning new features; these will build the foundations for a holistic understanding of low code software development. As such, it is critical to plan your sourcing and training/upskilling strategies to include this broader range of skills in order to take full advantage of the Appian platform.

Key exception: On-premise installations are a specific instance where installing the Appian software will require a greater level of technical knowledge - the skills required for effective development of solutions are the same. These contexts generally require someone who is competent as a system administrator on the target operating system (Linux or Windows). This skill set is not required for cloud deployments.

Team Structure

Appian strongly recommends a ‘team of 3’ structure (core pod team) supported by a Delivery Manager and an Architect for most projects (as described in the Roles and Qualifications section). With larger projects or programs, the implementation can be organized with multiple small teams collaborating with each other. A team should be cross-functional such that anybody can take on any task, but some may be stronger in certain skills. Based on extensive Appian implementation experience, a team of 3 full-time committed professionals with the right skills can accomplish program objectives much more rapidly with great coordination and support from the management.

While Appian recommends the use of small teams, it does not mean Appian customers are limited to executing small projects. Customers can build larger projects by breaking projects down and running multiple teams in parallel. Appian recommends that, as new projects are added, all delivery teams should leverage a common methodology. If there is any domain overlap, the governance in place should identify dependencies and coordinate release cadence.

T-Shaped Skill Set

Appian development demands less technical expertise than traditional high-code development and typically involves more interdisciplinary projects. That means members of an Appian team must be versatile and capable of performing a variety of roles. We refer to it as ‘The Developer and ___’ approach, which encourages Appian developers to gain supplemental skills complementing their core development duties. This doesn’t mean that Appian team members don’t have specialization, but rather that they have a ‘T-shaped’ profile: moderate knowledge in a broad range of skills, with deeper knowledge in a few core areas. This is also referred to as being a ‘Generalized Specialist’.

Ideally, Appian team members are T-shaped and cross-trained on a range of business and technical skills, some of which may become speciality areas over time. For example, a developer with a business analyst background might have deep knowledge of requirements gathering, analysis, and testing, but they will also possess foundational skills in development, data design, etc. This balance of breadth and depth is what constitutes a T-shaped profile, as illustrated below.

This approach enables Appian teams to be small, while remaining adaptable, since each member is capable of stepping into different roles when needed. This results in fewer external dependencies and smoother project progression. Let’s look at some of the recommended speciality areas for Appian Developers.

Specialty Areas

Following are some key principles to keep in mind for developer speciality areas:

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Key Responsibilities

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Product design specialists ensure that the finished application is a joy to use, conforms to Appian UX best practices, and meets user expectations for aesthetic design and usability. They are extremely familiar with Appian UX guidance, design patterns, and performance implications of different design patterns. When users or other stakeholders disagree with Appian UX guidance, product design specialists work with them to find a healthy compromise. During project development, they also conduct UX reviews and demonstrations, as well as engage in discovery activities to help ensure the team is building the right thing.

Business Analysis

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Business analysis specialists look at application requirements and convert them into Appian user stories for later development. They spend much of their time focusing on discovery, estimation, and communication between the business, IT, and the development team.

Application Architecture specialists are also knowledgeable about integrations, intelligent automation features such as RPA and AI Skills, DevOps and Appian deployment practices. They develop organizational best practices for consistent and reliable functionality of their Appian implementations. Someone who continues to grow and develop this speciality may eventually become an Appian Architect as their full time role.

Application Architecture

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Application Architecture specialists have a firm knowledge of Appian design patterns and best practices, allowing them to serve as the first point of contact for technical issues and questions.They are very familiar with database management practices for scalability and performance, and integrating them into Appian design.

They are also knowledgeable about integrations, intelligent automation features such as RPA and AI Skills, DevOps and Appian deployment practices. They develop organizational best practices for consistent and reliable functionality of their Appian implementations. Someone who continues to grow and develop this speciality may eventually become an Appian Architect as their full time role.

Testing

Key Responsibilities

Ensure development team follows best practices for unit, integration, usability, regression, and exploratory testing (among others)
Verify that proper load and performance testing occurs on the application prior to deployment
Generate testing strategy utilized during the project lifecycle

Testing specialists ensure the development team follows best practices surrounding testing and quality assurance. As part of their role, they create the test strategy followed by the rest of the team. While individual developers execute unit and integration testing as a routine part of development, testing specialists verify that proper load and performance testing of the system occurs before deployment. They are also knowledgeable about the different types of testing and how to most effectively use them, including when and how to leverage automated testing.

Agile

Key Responsibilities

Facilitate agile ceremonies throughout the project duration
Ensure proper application of agile principles
Organize demonstrations of value delivered after each sprint as appropriate
Advise users / customers on how to operate in an agile fashion if they aren’t already familiar

Agile specialists ensure the development team understands and follows Appian’s delivery methodology. As part of that, they often facilitate stand ups, refinement sessions, retrospectives, and organize sprint demos with the team.

Project Management

Key Responsibilities

Deliver value to stakeholders through project success
Manage risk and schedule during the project lifecycle
Balance delivery with business development and talent development
Manage relationships with stakeholders during team engagement

Project Management specialists ensure stakeholders achieve their desired outcomes through successful project delivery. With each project, they manage budget and resource allocation, assess velocity, maintain the product backlog, and conduct disaster planning. Managing risk and clearing impediments are central to the project management specialty.

Accessibility

Key Responsibilities

Ensure compliance with published accessibility guidelines
Verify the project meets accessibility requirements in accordance with local or national law
Advise development team on best practices as required and perform peer reviews of results

Accessibility specialists ensure that Appian projects meet requirements for accessibility in accordance with applicable regulations, web standards, and general best practices. They are familiar with Appian’s accessibility tools, and advise developers on best practices, as well as design decisions that would negatively impact application accessibility.

Enablement

Key Responsibilities

Maintain project documentation throughout the project lifecycle and ensure every team member is generating it appropriately
Provide application training to users
Work with the Agile specialist to train users on Appian methodology when required

Enablement specialists ensure successful use of the application. They monitor documentation of the application during development so that others can effectively use it and expand on it. During or after the project, they may be responsible for training and supporting users in their design and architecture efforts.

Building a team of T-shaped, generalized specialists, can help drive business transformation in a way that pure technical resources cannot: they can re-imagine the future state business process, challenge underlying assumptions, interview key stakeholders to drive business value and work with integration partners to deliver programs more effectively.

Citizen Development

Low-code development platforms, like Appian, reduce the level of technical knowledge required to build powerful applications. As such, some organizations have sponsored citizen development programs: enabling the Appian up-skilling of non-technical roles, often embedded within business groups. These citizen developers can leverage the speed and power of the Appian platform to address various business challenges. The most frequently cited benefit of citizen development programs is the promise of empowering people closest to business challenges to use Appian to fix them without reliance on central IT resources, improving business speed and agility while enabling IT groups to scale.

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

These challenges can be overcome with a solid structure of support and accountability. Appian interviewed citizen development program leaders to find out how they set up their programs to meet these challenges and reap the rewards of citizen developers.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, teams, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:46:23 GMT

Revision 26 posted to Guide by Appian Max Team on 5/31/2024 6:46:23 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Understand the ‘Team of 3’ structure and its relevance to Appian projects
Define a T-shaped profile and how it applies to Appian development
Recognize common Appian developer speciality areas
Learn how Citizen Development can help non-technical roles contribute to Appian development

Holistic Software Development

Team Structure

T-Shaped Skill Set

Specialty Areas

Following are some key principles to keep in mind for developer speciality areas:

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Key Responsibilities

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Business Analysis

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Application Architecture

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Testing

Key Responsibilities

Ensure development team follows best practices for unit, integration, usability, regression, and exploratory testing (among others)
Verify that proper load and performance testing occurs on the application prior to deployment
Generate testing strategy utilized during the project lifecycle

Agile

Key Responsibilities

Facilitate agile ceremonies throughout the project duration
Ensure proper application of agile principles
Organize demonstrations of value delivered after each sprint as appropriate
Advise users / customers on how to operate in an agile fashion if they aren’t already familiar

Project Management

Key Responsibilities

Deliver value to stakeholders through project success
Manage risk and schedule during the project lifecycle
Balance delivery with business development and talent development
Manage relationships with stakeholders during team engagement

Accessibility

Key Responsibilities

Ensure compliance with published accessibility guidelines
Verify the project meets accessibility requirements in accordance with local or national law
Advise development team on best practices as required and perform peer reviews of results

Enablement

Key Responsibilities

Maintain project documentation throughout the project lifecycle and ensure every team member is generating it appropriately
Provide application training to users
Work with the Agile specialist to train users on Appian methodology when required

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, teams, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:40:37 GMT

Revision 25 posted to Guide by Appian Max Team on 5/31/2024 6:40:37 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

Team Structure

T-Shaped Skill Set

Specialty Areas

Following are some key principles to keep in mind for developer speciality areas:

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Key Responsibilities

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Business Analysis

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Application Architecture

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Testing

Key Responsibilities

Ensure development team follows best practices for unit, integration, usability, regression, and exploratory testing (among others)
Verify that proper load and performance testing occurs on the application prior to deployment
Generate testing strategy utilized during the project lifecycle

Agile

Key Responsibilities

Facilitate agile ceremonies throughout the project duration
Ensure proper application of agile principles
Organize demonstrations of value delivered after each sprint as appropriate
Advise users / customers on how to operate in an agile fashion if they aren’t already familiar

Project Management

Key Responsibilities

Deliver value to stakeholders through project success
Manage risk and schedule during the project lifecycle
Balance delivery with business development and talent development
Manage relationships with stakeholders during team engagement

Accessibility

Key Responsibilities

Ensure compliance with published accessibility guidelines
Verify the project meets accessibility requirements in accordance with local or national law
Advise development team on best practices as required and perform peer reviews of results

Enablement

Key Responsibilities

Maintain project documentation throughout the project lifecycle and ensure every team member is generating it appropriately
Provide application training to users
Work with the Agile specialist to train users on Appian methodology when required

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:38:41 GMT

Revision 24 posted to Guide by Appian Max Team on 5/31/2024 6:38:41 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Specialty Areas

Following are some key principles to keep in mind for developer speciality areas:

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Key Responsibilities

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Business Analysis

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Application Architecture

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Testing

Key Responsibilities

Ensure development team follows best practices for unit, integration, usability, regression, and exploratory testing (among others)
Verify that proper load and performance testing occurs on the application prior to deployment
Generate testing strategy utilized during the project lifecycle

Agile

Key Responsibilities

Facilitate agile ceremonies throughout the project duration
Ensure proper application of agile principles
Organize demonstrations of value delivered after each sprint as appropriate
Advise users / customers on how to operate in an agile fashion if they aren’t already familiar

Project Management

Key Responsibilities

Deliver value to stakeholders through project success
Manage risk and schedule during the project lifecycle
Balance delivery with business development and talent development
Manage relationships with stakeholders during team engagement

Accessibility

Key Responsibilities

Ensure compliance with published accessibility guidelines
Verify the project meets accessibility requirements in accordance with local or national law
Advise development team on best practices as required and perform peer reviews of results

Enablement

Key Responsibilities

Maintain project documentation throughout the project lifecycle and ensure every team member is generating it appropriately
Provide application training to users
Work with the Agile specialist to train users on Appian methodology when required

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:35:51 GMT

Revision 23 posted to Guide by Appian Max Team on 5/31/2024 6:35:51 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Team Structure

Specialty Areas

Following are some key principles to keep in mind for developer speciality areas:

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Key Responsibilities

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Business Analysis

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Application Architecture

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Testing

Key Responsibilities

Ensure development team follows best practices for unit, integration, usability, regression, and exploratory testing (among others)
Verify that proper load and performance testing occurs on the application prior to deployment
Generate testing strategy utilized during the project lifecycle

Agile

Key Responsibilities

Facilitate agile ceremonies throughout the project duration
Ensure proper application of agile principles
Organize demonstrations of value delivered after each sprint as appropriate
Advise users / customers on how to operate in an agile fashion if they aren’t already familiar

Project Management

Key Responsibilities

Deliver value to stakeholders through project success
Manage risk and schedule during the project lifecycle
Balance delivery with business development and talent development
Manage relationships with stakeholders during team engagement

Accessibility

Key Responsibilities

Ensure compliance with published accessibility guidelines
Verify the project meets accessibility requirements in accordance with local or national law
Advise development team on best practices as required and perform peer reviews of results

Enablement

Key Responsibilities

Maintain project documentation throughout the project lifecycle and ensure every team member is generating it appropriately
Provide application training to users
Work with the Agile specialist to train users on Appian methodology when required

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:27:15 GMT

Revision 22 posted to Guide by Appian Max Team on 5/31/2024 6:27:15 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Specialty Areas

Following are some key principles to keep in mind for developer speciality areas:

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Key Responsibilities

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Business Analysis

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Application Architecture

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Testing

Key Responsibilities

Ensure development team follows best practices for unit, integration, usability, regression, and exploratory testing (among others)
Verify that proper load and performance testing occurs on the application prior to deployment
Generate testing strategy utilized during the project lifecycle

Agile

Key Responsibilities

Facilitate agile ceremonies throughout the project duration
Ensure proper application of agile principles
Organize demonstrations of value delivered after each sprint as appropriate
Advise users / customers on how to operate in an agile fashion if they aren’t already familiar

Project Management

Key Responsibilities

Deliver value to stakeholders through project success
Manage risk and schedule during the project lifecycle
Balance delivery with business development and talent development
Manage relationships with stakeholders during team engagement

Accessibility

Key Responsibilities

Ensure compliance with published accessibility guidelines
Verify the project meets accessibility requirements in accordance with local or national law
Advise development team on best practices as required and perform peer reviews of results

Enablement

Key Responsibilities

Maintain project documentation throughout the project lifecycle and ensure every team member is generating it appropriately
Provide application training to users
Work with the Agile specialist to train users on Appian methodology when required

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:16:52 GMT

Revision 21 posted to Guide by Appian Max Team on 5/31/2024 6:16:52 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Specialty Areas

Following are some key principles to keep in mind for developer speciality areas:

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Key Responsibilities

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Business Analysis

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Application Architecture

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:16:09 GMT

Revision 20 posted to Guide by Appian Max Team on 5/31/2024 6:16:09 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Speciality Areas

Following are some key principles to keep in mind for developer speciality areas:

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Key Responsibilities

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Business Analysis

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Application Architecture

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:15:35 GMT

Revision 19 posted to Guide by Appian Max Team on 5/31/2024 6:15:35 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Speciality Areas

Following are some key principles to keep in mind for developer speciality areas:

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Key Responsibilities

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Business Analysis

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Application Architecture

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:14:30 GMT

Revision 18 posted to Guide by Appian Max Team on 5/31/2024 6:14:30 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Speciality Areas

Following are some key principles to keep in mind for developer speciality areas:

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Key Responsibilities

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Business Analysis

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Application Architecture

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:13:31 GMT

Revision 17 posted to Guide by Appian Max Team on 5/31/2024 6:13:31 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Speciality Areas

Following are some key principles to keep in mind for developer speciality areas:

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Key Responsibilities

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Business Analysis

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Application Architecture

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:09:28 GMT

Revision 16 posted to Guide by Appian Max Team on 5/31/2024 6:09:28 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Speciality Areas

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Key Responsibilities

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Business Analysis

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Application Architecture

Key Responsibilities

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:04:33 GMT

Revision 15 posted to Guide by Appian Max Team on 5/31/2024 6:04:33 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Speciality Areas

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Business Analysis

Investigate application requirements and translate them into user stories
Serve as a communication link between developer activities and the business
Identify opportunities for further expansion of Appian

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 18:02:14 GMT

Revision 14 posted to Guide by Appian Max Team on 5/31/2024 6:02:14 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Speciality Areas

Needs are implementation-specific: Not every speciality area will be needed, or needed to the same extent, for every project
Divide up responsibilities: Try to avoid having one person focused on multiple speciality areas at a time to ensure sufficient focus and to share responsibilities
Rotate to develop broader expertise: Speciality areas aren’t intended to be permanent or fixed designations. It’s good for each developer to get practice across these areas so to avoid becoming overly reliant on one team member
Speciality areas represent areas of expertise, not groups of tasks: Some recurring tasks may be rotated amongst developers, but don’t represent their own speciality

Although dedicated roles are not required, Appian teams have found over time and through many projects that developing several specialty area skill sets can be highly beneficial.

Product Design

Focus on overall usability of Appian applications, not just individual interfaces
Possess deep knowledge of Appian user experience (UX) guidance and practices
Balances the desire for attractive and simple design against enterprise performance requirements
Participate in peer reviews of stories to ensure team follows best practices

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Fri, 31 May 2024 17:55:07 GMT

Revision 13 posted to Guide by Appian Max Team on 5/31/2024 5:55:07 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Database configuration & management: SQL queries, inserts, storage, etc.
Appian Process and UX design
Data management: Data modeling, data normalization
Business analysis and business process mapping

Appian recommends that customers should balance team technical skills with the following professional and personal skills:

Passionate: Does this person have a passion for what they do?
Self-starter: Is this individual motivated? Are they action-oriented?
High work ethic: Are they willing to put in extra effort, if necessary, to get the job done?
Achievement-focused: Does this person care more about ensuring their project achieves desired outcomes, or are they more motivated by status?
Perseverance: Do they persist under challenging conditions?
Generous: Are they generous with their time, information, and assistance when working on a team?
Team-player: Are they more motivated more by team achievement than personal goals?

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

Appian Max Team — Tue, 23 Apr 2024 13:10:24 GMT

Revision 12 posted to Guide by Appian Max Team on 4/23/2024 1:10:24 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Because Appian development requires less technical depth compared to the traditional coding platforms and most Appian projects tend to be more interdisciplinary, Appian team members need to be able to function across all roles. This does not mean that Appian team members don’t have specialization, but that they often have a ‘T-shaped’ profile: moderate knowledge in a broad range of skills, with deeper knowledge in a few.

Ideally, Appian team members are T-shaped resources who have been cross-trained on a range of business and technical skills. For example, a T-shaped resource with a business analyst background may be an expert in analysis and testing, but a novice in development or data design. Building a team around T-shaped resources means that everyone on the team can help where and when it’s needed most. Most importantly, a team of T-shaped resources can help drive business transformation in a way that pure technical resources cannot: they can re-imagine the future state business process, challenge underlying assumptions, interview key stakeholders to drive business value and work with integration partners to deliver programs more effectively.

Beyond core Appian technical skills, Appian recommends that potential team members possess several additional technical competencies. For example, we recommend that at least one Appian team member have experience/competency in each of the following areas:

Database configuration & management: SQL queries, inserts, storage, etc.
Appian Process and UX design
Data management: Data modeling, data normalization
Business analysis and business process mapping

Appian recommends that customers should balance team technical skills with the following professional and personal skills:

Passionate: Does this person have a passion for what they do?
Self-starter: Is this individual motivated? Are they action-oriented?
High work ethic: Are they willing to put in extra effort, if necessary, to get the job done?
Achievement-focused: Does this person care more about ensuring their project achieves desired outcomes, or are they more motivated by status?
Perseverance: Do they persist under challenging conditions?
Generous: Are they generous with their time, information, and assistance when working on a team?
Team-player: Are they more motivated more by team achievement than personal goals?

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

joel.larin — Tue, 09 Apr 2024 20:26:03 GMT

Revision 11 posted to Guide by joel.larin on 4/9/2024 8:26:03 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Database configuration & management: SQL queries, inserts, storage, etc.
Appian Process and UX design
Data management: Data modeling, data normalization
Business analysis and business process mapping

Appian recommends that customers should balance team technical skills with the following professional and personal skills:

Passionate: Does this person have a passion for what they do?
Self-starter: Is this individual motivated? Are they action-oriented?
High work ethic: Are they willing to put in extra effort, if necessary, to get the job done?
Achievement-focused: Does this person care more about ensuring their project achieves desired outcomes, or are they more motivated by status?
Perseverance: Do they persist under challenging conditions?
Generous: Are they generous with their time, information, and assistance when working on a team?
Team-player: Are they more motivated more by team achievement than personal goals?

Team Structure

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

joel.larin — Mon, 08 Apr 2024 13:51:10 GMT

Revision 10 posted to Guide by joel.larin on 4/8/2024 1:51:10 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Database configuration & management: SQL queries, inserts, storage, etc.
Appian Process and UX design
Data management: Data modeling, data normalization
Business analysis and business process mapping

Appian recommends that customers should balance team technical skills with the following professional and personal skills:

Passionate: Does this person have a passion for what they do?
Self-starter: Is this individual motivated? Are they action-oriented?
High work ethic: Are they willing to put in extra effort, if necessary, to get the job done?
Achievement-focused: Does this person care more about ensuring their project achieves desired outcomes, or are they more motivated by status?
Perseverance: Do they persist under challenging conditions?
Generous: Are they generous with their time, information, and assistance when working on a team?
Team-player: Are they more motivated more by team achievement than personal goals?

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Team Structure

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

joel.larin — Mon, 08 Apr 2024 13:50:35 GMT

Revision 9 posted to Guide by joel.larin on 4/8/2024 1:50:35 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

Key exception: On-premise installations are a specific instance where installing the Appian software will require a greater level of technical knowledge - the skills required for effective development of solutions are the same. These contexts generally require someone who is competent as a system administrator on the target operating system (Linux or Windows). This skill set is not required for cloud deployments.

T-Shaped Skill Set

Database configuration & management: SQL queries, inserts, storage, etc.
Appian Process and UX design
Data management: Data modeling, data normalization
Business analysis and business process mapping

Appian recommends that customers should balance team technical skills with the following professional and personal skills:

Passionate: Does this person have a passion for what they do?
Self-starter: Is this individual motivated? Are they action-oriented?
High work ethic: Are they willing to put in extra effort, if necessary, to get the job done?
Achievement-focused: Does this person care more about ensuring their project achieves desired outcomes, or are they more motivated by status?
Perseverance: Do they persist under challenging conditions?
Generous: Are they generous with their time, information, and assistance when working on a team?
Team-player: Are they more motivated more by team achievement than personal goals?

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Team Structure

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

joel.larin — Mon, 08 Apr 2024 13:49:56 GMT

Revision 8 posted to Guide by joel.larin on 4/8/2024 1:49:56 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Database configuration & management: SQL queries, inserts, storage, etc.
Appian Process and UX design
Data management: Data modeling, data normalization
Business analysis and business process mapping

Appian recommends that customers should balance team technical skills with the following professional and personal skills:

Passionate: Does this person have a passion for what they do?
Self-starter: Is this individual motivated? Are they action-oriented?
High work ethic: Are they willing to put in extra effort, if necessary, to get the job done?
Achievement-focused: Does this person care more about ensuring their project achieves desired outcomes, or are they more motivated by status?
Perseverance: Do they persist under challenging conditions?
Generous: Are they generous with their time, information, and assistance when working on a team?
Team-player: Are they more motivated more by team achievement than personal goals?

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Team Structure

Additional Resources

Tags: program management, People

How to Skill and Structure Your Team

joel.larin — Thu, 27 Jul 2023 16:33:40 GMT

Revision 7 posted to Guide by joel.larin on 7/27/2023 4:33:40 PM

Skills Covered

This guide teaches you how to identify Appian development skill sets and how to structure that talent to build your development teams.

Skills Checklist:

Define a T-shaped profile and how it applies to Appian development.
Explain the difference between low-code and no-code.
Learn how Citizen Development can help non-technical roles contribute to Appian development.
Understand the ‘Team of 3’ structure and its relevance to Appian projects.

Holistic Software Development

T-Shaped Skill Set

Database configuration & management: SQL queries, inserts, storage, etc.
Appian Process and UX design
Data management: Data modeling, data normalization
Business analysis and business process mapping

Appian recommends that customers should balance team technical skills with the following professional and personal skills:

Passionate: Does this person have a passion for what they do?
Self-starter: Is this individual motivated? Are they action-oriented?
High work ethic: Are they willing to put in extra effort, if necessary, to get the job done?
Achievement-focused: Does this person care more about ensuring their project achieves desired outcomes, or are they more motivated by status?
Perseverance: Do they persist under challenging conditions?
Generous: Are they generous with their time, information, and assistance when working on a team?
Team-player: Are they more motivated more by team achievement than personal goals?

Citizen Development

Citizen Development programs are not without challenges. Some of the most frequently cited include:

Low-code is not ‘no-code’. Citizen developers still require some degree of baseline technical capability. Therefore, citizens need to be recruited selectively.
Protecting production integrity. Citizen development programs require clear governance guardrails to ensure citizen-built applications are architecturally sound and the overall technical environment is not endangered.
Setting support expectations. IT teams need to ensure citizens are fully aware of the support they will or will not get from central IT teams for applications they create.

S&P Global

See how S&P Global built a grassroots campaign around the promotion of citizen development to meet demand for Appian developers and to scale their business.

Read the full story here.

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank aims to source Appian developers from employees closest to the company’s business problems. Learn how they structure and support their citizen development program.

Read the full story here.

Team Structure

Additional Resources

Tags: program management, People