The AgilePoint application development committee completes the following tasks.
Categorize Processes
Define categories for processes, such as "sales" or "HR", and determine the scope of each project. In this way the committee creates a kind of taxonomy for processes.
Determine the Number of Applications
The solution architect determines the number of applications to create -- whether there will be only one application, or whether particular groups of processes will get different applications.
AgilePoint recommends having a portal-type user interface where users access the applications they require from a single web page. Applications are developed independently to support various types of processes, such as sales, customer support, or HR. AgilePoint BPMS operates as the engine serving all of these applications
AgilePoint BPMS can serve any number of required applications, so the decision is unimportant from the AgilePoint perspective. Likewise, any number of applications can be served from the same user-facing portal. So the decision is primarily a solution of architecture that depends upon your organization's requirements.
The following diagram shows a sample architecture with a middle layer that includes multiple applications, but with a single, shared entry point and AgilePoint BPMS.
Gather Process Requirements
The committee works with business users to gather and analyze process requirements, design the process, and document the process.
A best practice is to keep the process documentation in a SharePoint library.
Prioritize Processes for Automation
Assess which process is best to be automated using AgilePoint BPMS. For more information, see Principles for Identifying Your First AgilePoint Process.
Identify Shared Subprocesses
Determine subprocesses that can be modularized and shared. For more information, see Principles for Identifying Your First AgilePoint Process.
