Appian a good choice for agile process development.
September 05, 2017

Appian a good choice for agile process development.

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with Appian

They have responded quickly and adequately to the problems that have been raised. Support for product upgrades and upgrades has been fast and effective. Migration to higher versions has been smooth. Its learning platform provides the basic technical knowledge to get you started with the product.
We also have an Appian technician to solve the most urgent problems.
We are carrying a process of migration and re-engineering of the current back office processes. We are talking about 100 processes such as customer registration, transfers, and checks. These processes include both manual tasks and automatic tasks that connect to other systems in the bank. The development is carried out by a mixed technology and business team. The goal is to turn Appian into the bank's BPM engine.

  • Friendly and powerful development sutie.
  • Easy handling of parallelization and subprocesses.
  • Rapid development of forms and processes.
  • Improve the version control of components in a project.
  • Improve the integration with non-product frontends.
  • It is difficult to extend the product with ad-hoc components.
  • We are still in the development phase but expect a 5% reduction in operating costs.
The main advantage of Appian is the ease to design, develop and implement processes and forms in a relatively short time. By using WebServices as the primary integration mechanism, it integrates seamlessly with other systems.

Development in jBPM and webMethos requires more work, however they provide much more powerful integration and customization mechanisms than Appian.
Appian is suitable for projects:
  • Whose requirements evolve over time.
  • With non-complex frontends.
  • Make use of standard integrations (eg WebServices).
  • With subprocesses and parallelism.
  • Use agile methodologies
Not suitable for projects:
  • With excessively complex frontends.
  • With specific integrations.
  • With many components and/or subprocesses.