Projects that are a Good Fit for AgilePoint
The following types of processes are a good fit for AgilePoint.
Human-Centric Processes
Human-centric processes focus on human review, approval, etc. AgilePoint automation is especially effective when these processes require collaboration:
- Across departments
- Across geography
- Across multiple companies
Many Process Instances
Processes that are initiated frequently, transfer across departments, and need to be tracked are good fits for AgilePoint. AgilePoint can provide access to information regarding the time consumed for a task, to whom it is assigned, and the current status.
Requirements that Change Frequently
AgilePoint is a good fit for processes where requirements change frequently due to changes in legislation or company policy, and the process must change to adapt in days or weeks, rather than months or years.
Ambiguous Requirements
When you design the process, some elements may be unknown, but you know that the details will need to be added later. AgilePoint enables you to skip steps, roll back, or migrate to a new process model as requirements become clearer.
Complicated Processes
Similar to the case where requirements are ambiguous, complex processes may have many sub-branches where the details are not easy to determine up front. AgilePoint enables you to develop these sub-branches independently and improve them over time without affecting the main process. The sub-branches can be changed during runtime without interrupting the process flow.
Processes that Initiate Automatically
AgilePoint is a good fit if you want to trigger processes without human intervention – for example once a day, or triggered by an event, such as an email or a database change.
SOA is Desired
If SOA-based processes are desired in your application, AgilePoint is a good fit. AgilePoint processes invoke web services, instead of applications. SOA-based processes are excellent for human to system or system to system processes.