Professional Documents
Culture Documents
Phase :
Why ?
What ?
How ?
Outputs
Risks
1
Why ?
People Development Phase
At the end of the day, it is people that will make processes function
effectively and efficiently, no matter how much they are automated. If
you do not get the people ‘on board’ with the project and new
processes, then they will find a way to ensure that the processes either
do not work, or do not work efficiently
… if you put a good performance against a bad system, the system will win
almost every time
(Keen, 1997 : 65)
Even if the organization has their structure optimized, people are the ones
who execute the processes and make things happen. Without them, you have
nothing.
3
Technology Development
What ?
Integration of internal systems (business apps)
Automation of business processes
Collaboration with external entities
4
How ?
5
Step 1 :
Communications
• What is proposed?
• How will it be completed?
• How will it affect me?
• What input will I have into the outcomes?
• What if I do not like the outcomes?
• Will I keep my job with the new technology in place?
• What new skills will I need to adapt with the new technology?
• How will my job change with the new technology?
6
People Development – Step 2.1, 3.1, 4.1 :
People Strategy, Activity Definition, and Role Redesign
People Strategy
• Coordination with HR, Worker Union, Management to get approvals and buy-
in from the organization members
Activity Definition
• Based on the tasks created/re-designed during Improvement phase
• Activity is further broken-down into individual tasks performed by individual
roles within the organization
Role Redesign
• Grouping of activities into generic roles
• Maybe iterative process as feedback and discussions will affect the grouping
• After roles have been defined, role definitions can be produced :
7
People Development – Step 2.1, 3.1, 4.1 :
People Strategy, Activity Definition, and Role Redesign
RASCI model :
Responsible – Own the activity
Accountable – Approves the activity
Support – Can provide resources and information to support the activity
Consult – Has information required to complete the activity
Inform – Must be notified of the activity and its result, but need not be consulted
• Activity and role measurements Workgroup
8
People Development – Step 2.1, 3.1, 4.1 :
People Strategy, Activity Definition, and Role Redesign
RASCI model
People Development – Step 5.1 :
Performance Management and Measurements
Start with a few measures and keep it simple, use Capacity Planning from Elaboration Phase as
reference so performance targets can be kept realistic
After roles and activities have been designed, set performance measures
Make sure people understand their roles and rationale behind performance measurements
Management needs to listen to process executors for suggestions for process improvements
It’s appropriate for management to say ‘no’ to suggestions, but make sure the people understand
why the answer is ‘no’
“since people don’t do what you expect but what you inspect … you need to create a way
to measure results” 10
Louis Gerstner, 2002
People Development – Step 5.1 :
Performance Management and Measurements
(reproduced with the permission of MPM Group Pty Ltd, trading as TouchPoint Process Management Services)
11
People Development – Step 6.1 :
People Core Capability Gap Analysis
12
People Development – Step 6.1 :
People Core Capability Gap Analysis
(reproduced with the permission of MPM Group Pty Ltd, trading as TouchPoint Process Management Services)
13
People Development – Step 7.1 :
Organizational Structure
SOA Governance
• Maintained and monitored Service Level Agreements from each Business
Application
• Service network and service dependencies
• Proper management of service registries
16
Technology Development – Step 4.2 :
Develop Presentation Layer of the Solution
Familiar UI – is it a view that end-users are familiar with, and does it
have a logical look and feel (i.e. is it similar to existing/other systems or
does it have a logical flow of the screens)?
Role centric UI – different types of users will have different needs and
ways of interacting with the systems (for example, employees,
controllers, managers, etc.)
Technology and framework – used when developing presentation layer,
e.g. Enterprise Portal, Web 2.0, MVC Framework
Breakdown development priorities using MoSCoW approach from DSDM
(Dynamic Systems Development Method)
• Must have
• Should have if at all possible
• Could have this if it does not affect anything else
• Won’t have (in this release), but would like to have it later
17
Technology Development – Step 5.2 :
Solution Testing
Unit test
• Verifies a particular activity or step of the automated BPM solution meets the requirements
established in the design specifications
Integration test
• Verifies a function or an aspect of the automated BPM solution meet the requirements established in
the design specifications
System test
• Verifies the automated BPM solution or its components meets the requirement established in the
functional and quality specifications
Regression test
• Checks all part of the system still function correctly after the implementation or modification of an
automated BPM solution
18
Technology Development – Step 5.2 :
Solution Testing
19
People and Technology Development – Step 8.1, 6.2 :
Develop Training
Training Analysis
• A training needs analysis
• A training media analysis
• A training material development
• Just-in-time training vehicles – it is no use training people well ahead of time and then having them
forget the lessons learned
22
Technology Development – Risks
Risks Mitigation Strategy
Developed solution does Ensure that the stakeholders are involved throughout the
not meet business project and that they fully understand all the decisions
requirement made and the consequences, and work on the basis of
the agreed process architecture and business case
Some application work, There may be failed interfaces or connectivity. Make sure
however, the overall all interfaces and interoperability are thoroughly tested
solution does not work
Testing finds too many Ensure that the requirements (functional and technical
errors design) are explicit and clear enough to be used as bases
for the development , as well as preparing the test script
23
Discussion
Student’s Workbook
page 10 - 11
24