Skip to main content

PMO and PM

A project management office (PMO) is a team or department that sets and maintains standards for project management throughout an organization and in charge of creating procedures and best practices that will help operations. 

PMO helps you learn from the past projects, they will give you the templates and guideline you need make sure your project takes right approach.

There are three ways PMO helps you.


Supportive:

provides all the templates for the project:

  • BRD
  • Project initiation check list
  • Planning, Execution, Close out check list
  • Go-Live check list
  • MoM check list
  • Project Proposal document
  • etc..

Controlling:

PMO's that control the way project management is done in a project (company) will analyze below and share report.

  • Resource utilization (Productive resources, non-billable resources, Bench time resources)
  • Enhancements status report
  • Aging report
  • Project schedule variance
  • Project Effort deviation
  • Project Cost deviation

Directive:

PMO's that take directive approach actually provide project managers (you) to project teams.

In this approach PM will report to PMO directly.

The reporting structure makes sure that the project managers follow the framework and templates prescribed by the PMO.

Directive PMO's have lot of control over the project.

Labels:

Comments

Post a Comment

Popular posts from this blog

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - archite
Post a Comment
Read more

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir
Post a Comment
Read more

Lessons learned from sprint retrospective meeting

Scenario: Team Missed Sprint Goals Challenge: A development team consistently missed its sprint goals, leading to frustration and a drop in morale. Team members felt overwhelmed by the workload and struggled to communicate effectively. Retrospective Insights: During the retrospective, team members openly discussed their challenges and frustrations. They identified bottlenecks in communication, unclear priorities, and unrealistic expectations. The team realized that individual workloads were not evenly distributed, causing burnout for some members. Lessons Learned: Effective Communication Matters: The team recognized the importance of clear communication. They committed to regular stand-up meetings, where everyone shared progress, blockers, and priorities. Balancing Workloads: The retrospective highlighted the need to distribute tasks more evenly. They decided to monitor workloads and adjust assignments accordingly. Setting Realistic Goals: The team acknowledged that setting achievable
Post a Comment
Read more