Project Management Office (PMO)

PMO definition as per PMP:

A PMO is an organized body or entity assigned various responsibilities related to the centralized and coordinated management of those projects under its domain.

Why you need PMO?

Create Work Breakdown Structure (WBS)

Create WBS (Work Breakdown Structure) is the process of subdividing project deliverables and project work into smaller, more manageable components.

The Create WBS process is part of the Project Scope Management knowledge area in the PMP.

Inter personal skills of Project Manager

The “Interpersonal skills” also known as “Soft Skills” of the project manager make big difference in the project to build the team to improving the competencies, team interaction, and team environment and to achieve the goal of the project.

Inter personal is the important tool in the “Develop Project Team” process in the “Project Human Resource Management” knowledge area as per PMP.

Project Cost Estimation and Control

Project Cost Estimation and Control:

The cost estimation of the project involves estimate costs and control costs.

The below tutorial provides the example of cost estimation, monitoring and forecasting for the project.

The effort estimation, over head costs, software's and hardware's cost are not covered.

Stakeholder Management

A stakeholder is anyone who is affected either positively or negatively by the cost, time, scope, resources, quality, or risks of your project.

Use Case Point Estimation

Use Case Point Estimation:

Use case modeling is a popular and widely used technique for capturing and describing the functional requirements of a software system.

The designers of UML recommend that developers follow a use case driven development process where the use case model is used as input to design, and as a basis for verification, validation and other forms of testing.

A use case model defines the functional scope of the system to be developed. The functional scope subsequently serves as a basis for top-down estimates.

An important prerequisite for applying a use case based estimation method is that the use cases of the system under construction have been identified at a suitable level of detail and the division of the functional requirements into the use case. The use case model may be structured with a varying number of actors and use cases. These numbers will affect the estimates.

Risk Management

Risk is the net negative impact of the exercise of a vulnerability, considering both the probability

and the impact of occurrence.

Risk management is the process of identifying risk, assessing risk, and taking steps to reduce risk to an acceptable level.

Not all the risks are negative. Some events (like finding an easier way to do an activity) or conditions (like lower prices for certain materials) can help your project! When this happens, we call it an opportunity… but it’s still handled just like a risk.

As per PMP the project risk management process are:

Agile Iteration Planning

Agile iteration:

Agile iteration is a consistent time-box in which a delivery team plans, delivers and receives feedback on a product increment.

Conflict management

While no single definition of conflict exists, most definitions seem to involve the following factors:

That there are at least two independent groups, the groups perceive some incompatibility between themselves.

It’s probably no surprise that over half of conflicts come from priorities, schedules, and people. That’s why so many of the processes are focused on preventing conflicts.

Ground rules, good planning practices, and pretty much anything that has to do with communication are all there to prevent the most common reasons that conflicts happen.

Project Kickoff meeting

The kickoff meeting for a new project is your best opportunity to energize the group and establish a common purpose toward completing the work.

To thoroughly understand the role of the kick-off meeting on the success of a project, we must be clear about the purpose(s) of this first project meeting.