Overview |  | Roles |  | Work Items |  | Views |  | CMMI |  | Index |  | Glossary |

Project Portal
| IPMO Meeting ( 3 : IPM : 2 : 2.2 ) ( 2 : PMC : 1 : 1.6 ) ( 3 : IT : 2 : 2.5 ) ( 3 : IPM : 2 : 2.2 ) ( 3 : IPM : 1 : 1.4 ) ( 3 : IPM : 2 : 2.3 ) IPM Officer
Activity: IPMO Meeting
IPM Officer
Sponsor
Project Manager
Development Manager
Test Manager
|  |  |  | Operational Management |  |
|  | Participating Roles Responsible: IPM Officer Sponsor Project Manager Development Manager Test Manager Accountable: IPM Officer Product Manager Consult: Any Informed: All
### Overview The purpose of an Integrated Project Management Office (IPMO) meeting is to integrate and synthesize the master schedule for the organization. This may involve reprioritization, resource load balancing, rescheduling, or development of proposals for additional resources or funding. In order to facilitate these negotiations, an IPMO meeting must include the sponsors for each project in the portfolio as well as each project manager and the functional managers for the organization. # Entry Criteria Project Plan The current project plan of record containing all aspects of budget, resources, schedule, and requirements commitments. Project Reports The Work Remaining report and other project indicators which reflect schedule and other project plan commitments. Issue Log Open issues for the project identifying significant program, portfolio, or organizational issues. Master Schedule The organizational master schedule for the program or project portfolio. When: Weekly # Sub-Activities
1 | Project Updates | Go around the room and ask each project manager in turn to report project status. Project status should be brief. It should report whether the project is on schedule or any schedule variance. It should also report issues where the IPMO or the wider organization can help. In other words, carefully select the project issue log for those with issues with the widest scope, reach, or impact, or those that are urgent and require extra resources. Status for each project should take no more than a few minutes.
2 | Update Master Schedule | Based on the information from the project status reports, the master schedule should be updated. Particular attention should be paid to the utilization and scheduling of shared resources. Shared resources are typically specialist functions such as database administrators or user experience staff. Identify any resource contention in the schedule. Identify any significant commitments in jeopardy.
3 | Negotiate Trade-offs | Based on resource contention or commitments in jeopardy, negotiate with the stakeholders across the portfolio of projects to make agreements on revisions to the schedule, resource allocations, and commitments. List any change requests that result from negotiation in the revised master schedule.
4 | Form Consensus on Updated Master Schedule | Following negotiation, formally agree a consensus around the new master schedule. Publish the updated master schedule and communicate it to each project team.
# Exit Criteria
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |