Customer Management System

There are tons of systems out there trying to improve business processes of utility companies in general or electric companies in specific.

The key is still doing the re-engineering process well and the application system will just a tool to follow the processes. I put some of my thoughts about Electric Management System in this blog. Feel free to read and comment.

Monday, September 10, 2007

Why PMBOK is commonly used in project management?

In implementing a new system to a company, project management is the key in planning, staffing, executing and monitoring the whole process. Project implementors often use different approach to make sure that the system can be implemented with minimal risk. In general, this methodology for project management can be generalized into several steps. Most well known project management is PMBOK.

PMBOK stands for Project Management Body of Knowledge. It is combination of knowledge in the area of project management. It becomes a standard of project management because it has been proven in many project managements. It is a practice or methodology that is generally accepted. Generally accepted means that it could be applied to any projects in general. However, generally accepted means as well that in some of the projects, some methodologies are not obligatory.

PMBOK can be used by anyone interested in the project management, namely:
• Project managers
• Project team members
• Managers of project manager
• Customer of the project or project’s stockholder
• Consultant involved in the project management
• Trainers or educator in the area of project management

PMBOK can be summarized into 5 general processes:
1. Initiating Processes – in first step is to recognize that the project should begin. Commitment from all parties should be available to initiate the project.
2. Planning Processes – the process should define a workable scheme to achieve the goal of the project.
3. Executing Processes – in this process, the available human resources and other resources should be coordinated to carry out the plan.
4. Controlling Processes – measurement to detect any deviation from the goal and plan should be implemented. Necessary corrective action should be imposed to align the project into the plan.
5. Closing Processes – the project should end and acceptable by all parties. This step is related to formalize the closing of the project.

In next posts/articles, I will discuss in details about each processes and everything related to project management to ensure you do not miss the concepts of it. Make sure you sign up in our mailing list (you can find on upper left of the site) to be notified for any new post related to project management.

4 comments:

babawaya said...

Very true.. in a world full of procedures, rules and policies, PMBOK gets the work done efficiently with less confinement.

Project Management Software said...

A project is a temporary endeavor, having a defined beginning and end (usually constrained by date, but can be by funding or deliverables), undertaken to meet unique goals and objectives, usually to bring about beneficial change or added value.

Project Management Software said...

The attached document can help you as a guideline to plan for internal and external stakeholders in your Software product development process. The involvement parameters are based on standard RACI terminology.

Computer Networking LA said...

Pick a specific time to each task or group of tasks. Anything from 15 minutes to 2 hours. Chunks of 30 minutes or less work best.


Visitors