Chapter 3. Process discovery 91
simply described as
who does what, when does it needs to be done, and why it
needs to be done.
The who (and when): Process participant
For each task in the business process definition, much care should be taken
during process analysis to validate and document who can perform each activity
and when that activity must be performed. The
who is the process participant,
but should be elaborated on in the description if there is are particular
requirements such as seniority, licensing, or geography. For example, an activity
might be performed by a CSR, but only a CSR Level 2 licensed in California can
work on certain activities. Elaborate on the
when if there are particular
requirements (or no requirements) for when an activity must be (or can be)
started or completed. This information will be essential during implementation
when designing activity routing policy, due dates, escalation, user calendars, and
SLAs.
The what (and why): User story detail
Your process analysis should validate the user story detail to make sure that the
goal and output of the task, a description of what the activity must do, are clearly
documented. Do not leave the assessment of business value, the reason why
this task must be performed, up for assumption. Make sure that the business
value or business impact is also described in the documentation for the activity.
Without this, the process definition is incomplete and might miss opportunities for
additional key performance indicators and metrics. Without a clear statement of
business impact, there might also be inappropriate attention to detail during
implementation for this activity.
3.5.2 Playing it all back with Playback Zero
Playback Zero is a very important milestone in the life cycle of a business
process. For many participating in discovery and implementation, this will be
their first experience with a formal
playback. This might also be the team’s first
experience with IBM Business Process Manager and the end-user experience
with the Process Portal. Playback Zero might be the first time that the team has
experienced the newly designed business process from end-to-end with a
real-world business scenario.
Playback Zero is also a transition point between discovery and implementation
phases in the life cycle of a business process application. At this juncture,
stakeholders, including business owners and technology owners, have a
Do not skip Playback Zero: This first playback is a very important milestone
and transition point in the life cycle of your business process.

Get Scaling BPM Adoption from Project to Program with IBM Business Process Manager now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.