Minggu, 29 Mei 2011

How to evaluated EPM

How to evaluated EPM

What should be evaluated?
- Number of customer complaints
- Completion cycles for task
- Numbers of errors
- response time
- Number of hot line calls
- Number of customer served
- Reduction in expenses
- Increases in revenue
- Number of transactions handled
- Average length of time to handle transactions
- Reductions in questions or problem
- Improvement in customer service
- Additional tasks or outcomes achieved

Eight steps to success

Project implementation: Eight steps to success
By Tom Mochal

1. Prepare the infrastructure. 
Many solutions are implemented into a production environment that is separate and distinct from where the solution was developed and tested. It is important that the characteristics of the production environment be accounted for. This strategy includes a review of hardware, software, communications, etc. In our example above, the potential desktop capacity problem would have been revealed if we had done an evaluation of the production (or real-world) environment. When you are ready for implementation, the production infrastructure needs to be in place.

2. Coordinate with the organisations involved in implementation. 
This may be as simple as communicating to your client community. However, few solutions today can be implemented without involving a number of organisations. For IT solutions, there are usually one or more operations and infrastructure groups that need to be communicated to ahead of time. Many of these groups might actually have a role in getting the solution successfully deployed. Part of the implementation work is to coordinate the work of any other groups that have a role to play. In some cases, developers simply failed to plan ahead and make sure the infrastructure groups were prepared to support the implementation. As a result, the infrastructure groups were forced to drop everything to make the implementation a success.

3. Implement training.  
Many solutions require users to attend training or more informal coaching sessions. This type of training could be completed in advance, but the further out the training is held, the less information will be retained when implementation rolls around. Training that takes place close to the time of implementation should be made part of the actual implementation plan.

4. Install the production solution. 
This is the piece everyone remembers. Your solution needs to be moved from development to test. If the solution is brand new, this might be finished in a leisurely and thoughtful manner over a period of time. If this project involves a major change to a current solution, you may have a lot less flexibility in terms of when the new solution moves to production, since the solution might need to be brought down for a period of time. You have to make sure all of your production components are implemented successfully, including new hardware, databases, and program code.

5. Convert the data. 
Data conversion, changing data from one format to another, needs to take place once the infrastructure and the solution are implemented.

6. Perform final verification in production. 
You should have prepared to test the production solution to ensure everything is working as you expect. This may involve a combination of development and client personnel. The first check is just to make sure everything is up and appears okay. The second check is to actually push data around in the solution, to make sure that the solution is operating as it should. Depending on the type of solution being implemented, this verification step could be extensive.

7. Implement new processes and procedures. 
Many IT solutions require changes to be made to business processes as well. These changes should be implemented at the same time that the actual solution is deployed.

8. Monitor the solution. 
Usually the project team will spend some period of time monitoring the implemented solution. If there are problems that come up immediately after implementation, the project team should address and fix them.

Ruang lingkup Proyek meliputi:

Ruang lingkup Proyek meliputi:
1. Menentukan waktu proyek dimulai
2. Perencanaan lingkup proyek yang akan dikerjakan
3. Pendefinisian ruang lingkup proyek
4. verifikasi proyek serta kontrol atas perubahan yang mungkin terjadi saat proyek 
tersebut dimulai.

Benefits Of Project Management

Benefits Of Project Management


There are some people who feel that a project’s success is achieved merely by chance and luck. But the truth is far from that. The reality is- success of a project is accomplished through an integrated process of project creation, effective planning, execution, supervising and control, and at last closure of the complete project. Some companies depend heavily on a coordinated and coherent project management methodology to attain their goals. Some methodologies are dependent on policies and processes, whereas others are evolved around forms, guidelines and checklists.

To accomplish a well defined work flow, project management services are required. One of the goals of this structured methodology is to ease the task of incorporating the work throughout all the various operable units to meet project objectives. Moreover, project management improves efficiency and profits are generally expected to rise upon its implementation. These days it’s almost impossible to carry forth a project without having project management services.

Following are few of the benefits of project management service discussed, that explain why it can be of such crucial value to you:

(a) Efficiency: Project management services help us execute more work in lesser time, with fewer resources, and without making any compromises with the quality. This is one of the most important reasons, why one should go ahead and take up the assistance of a Project management services company for any projects.

(b) Scope Changes: It also facilitates effective upfront planning, which in turn drastically lowers the number of expensive scope changes on projects. It’s basically related to IT project management, but at the same time it’s advantageous for handling any type of project.

(c) Stability: Project management services allow work to flow in a multidirectional way, and generally lead to high efficiency, effectiveness, and stability of the organization. Instead of working in an exclusively old mannered style, it helps in approaching the solution from all the possible ways.

(d) Closeness to Customers: Project management always takes into account the customer satisfaction and it allows us to work close to the customers, resulting in a high degree of customer satisfaction.

(e) Problem Solving: It also allows better problem solving and most of the times in a shorter period of time. If time is something that you can’t afford to lose on your project, Project management services are indispensable for you.

(f) Application: Project management services can be applied to all projects, irrespective of the size or scope of the projects. Its versatility makes the reason why everybody these days goes for project management.

(g) Quality: Efficient application of project management services can enhance the quality without a resultant increase in cost. Quality comes at a price which is easy on the pockets- At least this is the case with Project management.

(h) Authority Issues: Project management contrary to general thinking, actually lowers the authority and power issues in organizations.

(i) Cost of Using Project Management: The cost of implementation and employing project management is quite low, while the result is an increase in business rather than a decrease.

(j) Solution Provider: Project management services help companies function as standalone solution providers instead of merely suppliers of products.

(k) Sub optimization Risks: Last but not the least; Project management facilitates us to make decisions which are in the best interest of the company as well as the project.

OVERVIEW OF A CASE STUDY: PROCESS CHANGES FOR A MANUFACTURING COMPAN

OVERVIEW OF A CASE STUDY: PROCESS CHANGES FOR A MANUFACTURING COMPANY

This paper will provide a high level overview of a case study of a manufacturing company that saw the value in taking a project management approach to a process change initiative.

Overview

Company XYZ has been aware that their production of widgets will not continue to satisfy clients' demands. They have seen an increase of 10% year after year for widgets over the last 5 years with no end in sight for the increase in demand. The CEO had asked an internal team to review current manufacturing processes and propose changes to the processes, along with upgrades to equipment to meet the demands for the future. When the team's proposal was submitted to the CEO, it recommended an upgrade to manufacturing equipment and a redesign of the production line with no solid metrics relating to the number of anticipated increases. Also missing (and critical to the outcome) was an analysis of what would happen in procurement, delivery, as well as warehousing, if these changes were made to the manufacturing process, and whether these departments would be able to manage those changes. After seeing such deficiencies in the team's plan, and with past experiences in such projects at another company, the CEO chose to engage a project management consulting company, ABC Projects, to outline a project plan for this initiative. ABC Projects specialised in process improvement initiatives. The CEO knew that these efforts were more likely to be successfully implemented when run as a well-managed project.

The Project Plan

ABC Projects outlined a project plan with tentative timelines and cost ranges until discovery was completed. The project plan included the discovery and identification of needs for increased production, as well as identification of affected departments and/or processes if the increase in production were carried out.
ABC Projects knew from experience that other areas besides the manufacturing line would be affected. For example, procurement had a set budget for purchases. The expenditure necessary for materials that were not ready to be used in manufacturing would wreck havoc on cash flow and require consideration of how to store materials until they are ready to be used by manufacturing. Further, additional vendors from which to purchase the materials would need to be identified, should the current vendors be unable to meet procurement's increased demands. Alternative vendors needed to be in place before any supply issues arose. It was evident that the processes for procurement must be very closely integrated with the manufacturing processes to maintain an ongoing flow of materials to production.
The project team developed a detailed plan for identifying the stakeholders and how they would proceed to gather the data necessary to accurately document the manufacturing processes. The plan included a detailed list of questions to ask each stakeholder to ensure that all interviewers asked the same questions and gathered the same data. The project team knew from experience that documenting processes required a thorough understanding of the business, because, when being interviewed, individuals often unintentionally skipped relevant details. Thus, experienced people were required to extract information needed for an accurate and detailed documentation of processes.
The project team also developed a plan for potential risks and strategies for managing them should they come to fruition. They wanted to be sure that once they determined the options for making changes to the manufacturing processes, that they could accommodate potential changes to other processes. They knew that changing one process would likely have a domino effect throughout the company. For example, during one of the scenario planning sessions, the project team found that if procurement was unable to fulfill the material needs of manufacturing from one vendor, without a back up vendor in place, there would potentially be a shortage of materials which would cause a delay in production or costs would increase by at least 30%. This would be unacceptable and would ultimately cause customer dissatisfaction which could lead to a loss of business to competitors.
The team also put together a change management plan; because a major component of the project would be communicating changes company-wide and ensuring the appropriate people were on-board and prepared to work with the new processes. Additionally, the project team needed the individuals involved on the production line to be willing to test new processes as well as new equipment with no interruption in meeting current client demand. Without support from these individuals, this would be an impossible task and one that had a high potential of risk associated with it.
Additionally, the project team sent out a company-wide communication so that employees knew what was happening and why, and they asked for suggestions from employees. By getting the input of the individuals who were doing the job day in and day out, they increased the likelihood of success on the project.
The Work Breakdown Structure included several milestones to allow the company to move forward with working with new processes and upgrades to equipment without interrupting the current production schedule. At each milestone, there were several tasks for measuring progress and comparing it to expected results and baselines. Assessments were completed regularly to ensure the current plan held true to the objectives. At any point during the project, if the assessments showed deficiencies from the objectives, then an evaluation of the process design and, if necessary, a correction occurred. The Work Breakdown Structure included training time to get individuals up to speed on new equipment.
The Risk Management Plan included contingencies should current employees be incapable of learning the new equipment and performing their role in a timely fashion. Part of the contingency plan was to use employees who adapted quickly to the new equipment on the new production line and maintain the old production line with employees who learned less quickly, until they were able to get up to speed. An integrated team concept, including mentoring, was put in place to assist people in getting up to speed on new equipment.
Regular status meetings were scheduled with manufacturing, procurement, delivery and other departments to maintain lines of communication and general awareness of the project status. These meetings also served to ensure that employees were comfortable with change and were able to participate in decisions that would affect how they perform their job.

Project Results

Prior to undertaking the project, Company XYZ was producing 250 widgets per day. At the time of the undertaking of the process improvement initiative, client demand had just reached 250, and demand had increased by 10% annually over the last five years and it appeared that the increase would continue for the foreseeable future.
The directive from the executives was to improve manufacturing processes through changes in processes as well as upgrading equipment, toward a goal of producing up to 400 widgets per day. Based on current projections, the company would experience a five year timeline before having to undertake another increase in production to satisfy growing client demand. At that point, if client demand continued to increase, the company would be in a better position to invest in another manufacturing site in order to meet demands after the five year mark.
Additionally, in the current production line there was, on average, a 3.6% defect rate in widgets produced. One of the directives specific to this project was to attempt to reduce this defect rate by at least half within the next two years.
The following were discovered during the project:
  • Capacity for procurement was limited due to cash flow and budgetary issues, as well as storage. Any new process needed to take this into consideration once production increased and would have to allow for a smooth flow between procurement and manufacturing.
  • It became apparent that once the number of widgets manufactured increased, demands on warehousing and delivery would increase accordingly. A plan was put in place to change warehousing and delivery processes to reduce the strain on these functions.
The project had run slightly over the projected timeline, but did remain within budget. The increase in the timeline resulted from an underestimate of the space required to store manufactured widgets prior to delivery. This occurred to a great extent because the decrease in the defect rate was .06%, significantly exceeding the goal of 1.8%, thus causing an increase in the number of widget units to be stored. Although this was not anticipated in a contingency plan it did not cause the executives to be unhappy. It was a good problem.

SUMMARY

A project management approach enabled the company to meet their production needs for the future, while at the same time not disrupting their current production to fulfill client demand. There was never a glitch in the production line while new processes were being tested and evaluated. Continuous communication ensured that everyone was in the loop on changes to processes and actually had the benefit of increasing participation from employees on how to improve processes to better meet client needs. Additionally, continuous review and adjustments to the risk management plan ensured that the end result was well thought out and tested and ensured that any glitches in proposed changes were caught immediately and could be addressed.
Adhering to a standard project management methodology enabled this company to implement a very high risk project efficiently, on budget and within reasonable time to meet long term strategic goals.

The Role of Consultants in BPR projects

The Role of Consultants in BPR projects

New reengineering teams typically consider the use of a consultant for their project. This module addresses some guidelines and tips to think about when evaluating the use of consultants. We also present benchmarking findings on the use of consultants from two separate studies.


What consultants bring to the table?

1. Consultants can play a valuable role in your project.
- They are objective and immune to internal politics.
- They have followed the process before.
- They bring information and best practices from other companies.
- They are good communication paths between front line workers and customers, and the leaders of the company or organization.

2. Consultants can also unintentionally create barriers by:
- having the solution being viewed as "theirs" and not "yours"
- taking too strong a lead role and disengaging the organization

3. The team leader and stakeholders must decide the role they want the consultant to play, and let that influence the consultant selection process. Three very different roles are:
*Role A - a strong facilitator and experienced practitioner who brings a methodology with them. If you need this type of support, look for consultants who have strong facilitation skills and in-depth process design knowledge.
*Role B - a team member; can be an objective and unbiased contributor to the solution; may fill a gap in your team that cannot be filled from within the organization; should be someone knowledgeable in your industry.
*Role C - a subject-matter expert with knowledge of performance levels and best practices of similar organizations and processes; able to perform specific tasks for the team.

Teams that have strong internal facilitators and experienced process design leaders should lean toward Role B or Role C. If the organization lacks internal skills to facilitate the team, then Role A may be required. You may need a combination of these roles.

Whichever roles you choose, define the responsibilities clearly. For example, will your consultant be responsible for:
- writing project documentation?
- leading the project and facilitating meetings?
- making presentations to stakeholders and associates?
- making decisions for the project?
- contributing subject-matter expertise in your organization’s work processes?

The better these roles are defined, the better your relationship with the consultant. 

manajemen proyek

Pengertian dari manajemen proyek adalah cara mengorganisir dan mengelola sumber penghasilan yang penting untuk menyelesaikan proyek. Hal pertama yang harus dianggap sebagai manajemen proyek adalah bahwa proyek ini diantarkan dengan batasan yang ada.Sedangkan hal kedua adalah kemungkinan terbaik distribusi sumber daya.
Pada dasarnya manajemen proyek meliputi semua tahap, aktivitas dan tugas yang diperlukan melalui siklus implementasi. Tugas-tugas yang diimplementasikan meliputi :
* Planning - Penjadwalan dan prioritas bekerja dengan menggambarkan perencanaan termasuk estimasi dan alokasi dan sumber penghasilan.
* Risk Management – Analisa dan monitoring resiko untuk mengurangi imbasnya dari keadaan yang tak terduga sebaliknya .
* Issue Management – Manajemen yang tepatguna dan pengawasan dari setiap masalah proyek.
* Status Reporting – Koordinasi komunikasi diantara anda, tim proyek, dan para supplier sebagai pihak ketiga.
* Project Administration - Administrasi proyek yang menggunakan tools proyek manajemen.
* Project Change Management - Evaluasi, penjadwalan dan pengaturan untuk setiap perubahan order yang muncul.
- Karakteristik manajemen proyek:
1.Kegiatan manajemen proyek dibatasi oleh waktu;yang sifatnya sementara, diketahui kapan mulai dan berakhirnya
2.Dibatasi oleh biaya/budget
3.Dibatasi oleh kualitas
4.Biasanya tidak berulang-ulang
- Contoh manajemen proyek:
1.Pembuatan rumah
2.Pembuatan jalan raya
3.Pembuatan jembatan
4.Pembuatan iklan perusahaan
5.Pembentukan tim evaluasi lokasi baru perusahaan
6.Pembuatan prototipe produk baru