Project management is the discipline of organizing and managing resources (e.g. people) in a way that the project is completed within defined scope, ...

Project Management

PMBOK guide - Project Management Certification

The multi-dimensional role of a Project Manager is sometimes considered too complex to be taught but the Project Management Institute (PMI, which conducts the PMP certification assessments) has put together a common repository of best practices that is emerging as a definitive standard worldwide. Here is a brief rundown of the responsibilities of a PM as defined in PMI's Body of Knowledge (PMBOK).

PMBOK PROCESS
The Project Management Body of Knowledge (PMBOK) is the sum of knowledge within the profession of project management. The PMBOK includes proven traditional practices that are widely applied and accepted. In order for a Project to be successful, the project team must select appropriate processes that are required to meet the project objectives. The PMBOK guide defines the project management processes as follows

Initiating Process: Defines and authorizes the project

Planning Process: Plans the course of action required to attain project objectives and define the scope of the Project.

Executing Process: Integrates people and other resources to carry out the project plan for the project.

Monitoring and Controlling Process: Regularly measures and monitors the activities of the project so that corrective action can be taken when needed.

Closing Process: Formalize the acceptance of the Project and brings the Project to an orderly end

The responsibilities of a Project Manager across Processes.

Planning Process

· Spend 90% of your time here. Do not rush this phase.
· Prepare to run meetings with various Stakeholders
· Ensure that potential Project Risks/Issues identified and create a
· Risk Management Plan
· Identify Key Project constraints/Assumptions
· Identify and Define Project Team Organization Structure
· Identify list of all the Activities of the Project
· Construct Activity Sequences (Predecessor, Successor relationship)
· Identify the Duration of the each activity
· Determine the Skill requirements by type of work and identify suitable resource for it
· Determine the Costs for Individual Activities
· Define the Customer Quality Expectations
· Define Quality Management Plan for your Project
· Ensure that the Quality Activities of the Project are not overlooked
· Define Communication Management Plan to disseminate Project Information to stakeholders
· Define Procurement Management Plan for software/hardware requirements for your project
· Construct a comprehensive Project Plan by including Communication management/ProcureManagement/Risk/Assumptions/Constraints/Issues/Activities

Executing Process

· Approve all the Change Requests
· Approve the Project Plan
· Direct the technical Team to execute the work as defined in the Project Plan
· Direct the other Organizational interfaces to execute work as defined in the Project Plan
· Acquire Project resources and assign them
· Collect data/Metrics about the Project

Monitoring & Controlling Process

· Monitor Risks and see their Progress using Risk Management Plan
· Monitor each Project activity using the Project plan
· Disseminate Project status information to Stakeholders
· Produce Performance report with regard to Scope, Schedule, Cost, Resources, Quality and Risk
· Look for potential Change Requests and implement them using Change Control Procedure
· Control the Cost (possible using EVA(Earned Value Analysis ))
· Control the Quality by implementing quality review techniques and standards identified in the Quality Management Plan
· Manage the Project Team Members performance, Providing feedback, resolving issues to enhance Project performance
· Manage Stakeholders Expectations and resolve issue

Closing Process

· Formally terminate all activities of the Project
· Hand off the completed Deliverable/Product to Customer
· Release all the Project resources including software/hardware
· Create Lessons Learnt Document and share your experiences
· Archive all the Project Documentation

General Guidelines

· Always “Communicate, Communicate, Communicate”
· Understand Customers Language and give what they want. “No more, No less”
· Provide “True status” of the Project all the times
· Use Tools and Techniques to increase your Team Productivity
· Use Microsoft Project Plan for better planning
· Closely monitor Project Critical Path
· Identify Risks in every Project Phase and discuss them in all the Meetings
· Create a Daily Log for all your activities
· Mentor your Team members
· Success or Failure, You are Accountable