Examine the problem statement, and look for those problems that are described at the business level. For each
problem, if the problem expands beyond the scope of single business, and needs the help of third-parties to
fulfill the required result, then a B2B process sketch is needed, otherwise it is a simple process.
The business requirements will define a number of improvement results. For each significant result there must be a
sketched process in a Business Process Diagram.
If possible Business Process Diagrams should be combined to demonstrate multiple
results and a combined context. However care must be taken not to create too large a diagram which is
difficult to understand. Clarity and understanding is best.
Simple process sketches are those Tasks that are internal to the business and do not involve third-party vendors
or other businesses in which to complete the business requirement Result. Simple process sketches do not use Pools as the sequence flow does not extended the beyond the enterprise. Often
customers who participant in a process, are represented as a Lane in a simple process.
In B2B Business Process Diagrams, Messages flow between businesses (Pools).
More information can be found here Scope of Business Process Sketching
|