analysis of processes and workflows, specification of requirements, project planning, and project control
Our Business Process Model contains the following elements:
- Statement of Scope – It’s very easy for one process to turn into several. Naming your process with a clear name in the [Verb] [Noun] syntax and writing a starts with / ends when statement will help you clearly identify the scope of the process.
- Desired Outcome – It’s easy for a process to get ingrained in “how we do it here” but lose its value over time. As a BA, it’s also very easy to jump into the details of what we do before stopping to consider why we do it. A clear answer to why we work through this process will guide your analysis.
- Process Flow or Activity Descriptions – This is the meat of the process model. It’s essentially a list of the steps completed by people in certain roles. This is the primary or most common path through the business process.
- Exceptions – In addition to the primary path, you want to include variations. What happens if information on a form is illegible, a required piece of information is not provided, or a special condition is met?
- Business Rules – Your process flow will presume a certain set of rules are followed or enforce those rules. As processes get more complex, it often makes sense to break the business rules out separately so they can be more easily managed as they change.
- Entry Criteria and Inputs – Entry Criteria identify what needs to be true in order for the process to start. Inputs identify any tangible work items someone executing the business process needs to have present-at-hand.
- Exit Criteria and Outputs – Exit Criteria identify what needs to be true when the process ends. Outputs identify tangible work items generated through the course of the business process.
- Workflow Diagram – While not required, often it makes sense to include a visual model showing the primary activity steps and exceptions. When multiple roles are involved, a swimlane diagram is a good choice.