The Implementation of BPR Pertemuan 8 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.

Slides:



Advertisements
Similar presentations
Organizational Governance
Advertisements

The Commitment Initial training will centre around short, foundation training in the theory and practice of sustainability as related to the Water Corporation.
Roadmap for Sourcing Decision Review Board (DRB)
Develop an Information Strategy Plan
Session 2.3: Skills for Supportive Supervision
RAMIRI2 Prague 2012 Project management and the RI Life Cycle.
Module 2 Objectives At the end of the session, participants will have an understanding of: The issue and the impacts How to encourage employees to take.
The CRM Textbook: customer relationship training Terry James © 2006 Chapter 11: Management.
Self-Service Business Intelligence for the Product Management Department (Concurrency Corporation)
ITIL: Service Transition
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Leadership in the Baldrige Criteria
Adjusting EPLC to your Project Colleen Robinson & Teresa Kinley Friday, February 6, 2009.
B&O Committee May 2015 iTRAK - Change Management An Agency Adapting to Change.
By Saurabh Sardesai October 2014.
IS&T Project Management: Project Management 101 June, 2006.
Coaching Workshop.
Change Management Chris Colomb Trish Fullmer Jordan Bloodworth Veronica Beichner.
Charting a course PROCESS.
Release & Deployment ITIL Version 3
Solution Overview for NIPDEC- CDAP July 15, 2005.
Managing Fast – Tracked Projects: A Review of ECI Report Dr
Developing an IS/IT Strategy
SMS Operation.  Internal safety (SMS) audits are used to ensure that the structure of an SMS is sound.  It is also a formal process to ensure continuous.
Year 12 Business Management Management roles, styles & skills (Chapter 5)
Software Project Management Introduction to Project Management.
West Impl 1© The Delos Partnership 2005 Integrated Enterprise Leadership Implementation.
Why do we … Life cycle processes … simplified !!!.
Overview of the workout TimeContentMethod / Person 10 minutesWelcome & objectives Trainer led 20 minutes Coaching – what it is; why it’s so important;
Introduction- Project Management By Ctrl+C & Ctrl+V 1.
Module N° 8 – SSP implementation plan. SSP – A structured approach Module 2 Basic safety management concepts Module 2 Basic safety management concepts.
BPR PHASE IV IMPLEMENTATION NOAA Business Process Re-Engineering Current Status: June 21, 2006 NESDIS Cooperative Institute Directors and Administrators.
1. 2 Business Process Reengineering (BPR) “the fundamental rethinking and redesign of processes to achieve dramatic improvements in critical, contemporary.
1 Project Management Introduction. 2 Chap 1 What is the impact? 1994: 16% of IT projects completed “On-Time” 2004 : 29% of IT projects “On- Time” 53%
Business Process’s Blue Print Pertemuan 3 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
Ch 4 - Learning Objectives Scope Management You should be able to: n Discuss the relationship between scope and project failure n Describe how strategic.
Copyright 2008  Project management process groups progress from initiating activities to planning activities, executing activities, monitoring and controlling.
IT Infrastructure Management IT Infrastructure Library Best Practice.
Teambuilding For Supervisors. © Business & Legal Reports, Inc Session Objectives You will be able to: Recognize the value of team efforts Identify.
Planning for security Microsoft View
© 2001 Change Function Ltd USER ACCEPTANCE TESTING Is user acceptance testing of technology and / or processes a task within the project? If ‘Yes’: Will.
The Implementation of BPR Pertemuan 10 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
The Development of BPR Pertemuan 6 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
Project Management Planning Minder Chen, Ph.D. CSU Channel Islands
SHRM Thought Leaders Conference Scottsdale, AZ October 5-6, 2009.
Project Management Starting out. What makes projects different to BAU (Business as Usual)?  Change - Projects are the means by which we introduce change.
PPTTEST 12/26/ :41 1 IT Ron Williams Information Technology Management Project Management.
The Implementation of BPR Pertemuan 9 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
1A FAST EXCELLENCE THROUGH FACILITATION Gary Rush The FAST Process MGR Consulting
State of Georgia Release Management Training
MGT 461 Lecture #27 Project Execution and Control Ghazala Amin.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Phase-1: Prepare for the Change Why stepping back and preparing for the change is so important to successful adoption: Uniform and effective change adoption.
ITIL: Service Transition
Project Management Processes
WHAT IS COACHING CULTURE ?
Coaching.
Guidance notes for Project Manager
2014 WIC EBT Users Group Implementing EBT & MIS Together
By Jeff Burklo, Director
How to keep your Enterprise GIS Project on Track
Pertemuan 08 Materi : Buku Wajib & Sumber Materi :
Project Management Processes
Roles and Responsibilities of a Project Manager
Re-Purposing and Reusing Training Materials Online
Lecturette 1: Leveraging Change through Strategic Planning
Lecturette 1: Leveraging Change through Strategic Planning
SDLC (Software Development Life Cycle)
Project Name Here Kick-off Date
Presentation transcript:

The Implementation of BPR Pertemuan 8 Matakuliah: M0734-Business Process Reenginering Tahun: 2010

Deployment Phase Deployment Phase :  Why ?  How ?  Outputs  Risks 3

Why ? 4 All solution and process improvement that has been designed and developed are brought to life All people change management activities take place

How ? 5

Step 1 : Communications 6 Maintain two-way communication with users in the project to solicit feedback and suggestions from them Deal with feedback, do not ignore it

Step 2 : Deployment Strategy Big Bang 7 The proposed change is introduced in one major overhaul The proposed change is introduced step by step (e.g. by location or business unit), with the next roll-out starting before the previous one is finished Parallel Relay The proposed change is introduced step by step, with each roll-out only starting once the previous one has been completed Combination A combination of the abovementioned implementation approaches – perhaps a small pilot and then building up to larger implementations

Step 2 : Deployment Strategy 8 AdvantageDisadvantage Fast to implementThe risk of disruption to the business is high AdvantageDisadvantage A relatively fast implementation, and the ability to make use of lessons learned from preceding implementations is valuable Additional resources will be required to assist with overlapping implementations, and the coordination of these simultaneous roll-outs will be high and potentially complex

Step 2 : Deployment Strategy 9 AdvantageDisadvantage Quality, as the lessons learned from the preceding roll-out(s) can be fully taken into account and the same implementation team can be used Lack of speed, as this implementation could, depending upon the circumstances, take some time to complete AdvantageDisadvantage Provides the organization with the benefits of tailoring the roll-out to the specific situation; flexible and yet still manageable

Step 3 : Train Staff Implementation of Training developed in People and Technology Development Phase 10 May take in a form of formal courses or on-the-job training, mentoring and coaching may continue during business tests and pilots Suggestions : Small doses of just-in-time training Individual training sessions, ensuring that people know when their session is scheduled Test competencies after training Monitor job performance after an appropriate period of time Training aspects Key activities of automated solutions Impacts of the proposed solution Which existing bottlenecks will be tackled Any new bottlenecks the participants expect to arise during the implementation period The benefits and possibilities of the proposed solution

Step 4 : Business Tests and Pilots User Acceptance Tests by Business Users 11 Involve customers and suppliers, where appropriate Have strong project management of the testing steps Have a feedback mechanism that is easy to use Listen and communicate honestly Have a mechanism to measure and share the results of the tests Always be prepared to make changes ‘on-the-fly’ and feed these back into the deliverables (development) cycle Communicate results of pilots and testing Get testimonials from staff, customers and suppliers Celebrate success and reward team members (project team and business) Important Considerations:

Step 5 : Rollout, back-out and contingency plans 12 Complete individual plans for each business unit involved in the roll-out Develop plans collaboratively with management and staff Plan for multiple planning session, ensuring that the project accommodates mistakes and continually learns and adjusts the plans accordingly Ensure that individual expectations of people are crystal clear, so there is no room for any misunderstanding Have a ‘dry’ run (practice) of the back-out or roll-back and contingency plans, make sure that it works and continue these ‘dry ‘ runs until any doubt is removed

Step 6 : Marketing Programs 13 Run a formal marketing campaign of your process improvement in the marketplace, specifically targeting external stakeholders Use multiple approaches to marketing and have your top customers informed by senior executives as much as possible

Step 7 : Roll Out 14 Make sure old processes and supporting systems are decommissioned after complete successful roll out of the new process Reporting relationship and organization structure changes may require some to time to take place, as will the initiation of any new roles and incentive schemes based on performance results

Outputs  Trained and motivated staff  Improved or new processes that work satisfactorily 15

Risks Mitigation Strategy Business training/testing becomes show-stopper Ensure that the requirements are discussed and clarified with the business, key users and stakeholders as early as possible Project team can not deal with all problems and inquiries at the start of deployment and during early stages Involve super users and ensure they are capable, available, and willing to help Stakeholders are not kept informed Communicate, communicate, communicate Lack of expertise in business to complete UAT Business may need some coaching in completing UAT, project team must provide coaching and guidance Testing is neglectedTesting should never be compromised. If required, extend deployment date to allow for proper testing 16