Assuming you don’t have a PMO, do you think you have what it takes to create one? There are many reasons to think that having a project management office is a great idea, but you should put a little soul searching into the effort to really determine if you're ready for it.
As organizations look to improve their performance, they often consider establishing a Project Management Office. The idea of creating a PMO is one thing; the actual implementation of it is entirely another. Taking a step-by-step approach and following some critical guidelines will help ensure your PMO’s chances for success.
Do you ever wonder how far to go with formal documentation on a given project? PMBOK gives us an extensive set for project management standards from which to draw, but we don’t always choose to apply the full extent of these standards to every project--nor would it be appropriate to do so. Meet Project Sizing...
The PMO needs to ensure that the information contained in that database of historical information is organized in a way that not just the data can be retrieved, but also that the context of that data can be understood. If we don’t, then not only may the information not help PMs, it could lead them to significant errors in their planning.
When things go crazy, how do you ensure that process doesn’t suffer? PMOs will benefit from having a “process-lite” concept that could be used in emergencies--and more importantly, a framework for determining when the approach could be used.
When the organizational environment is out of alignment with what the PMO believes it needs to achieve, how can you manage for success? One PM's struggle can hopefully provide lessons that will resonate with you as ways to improve your own efforts.
Given the fast-paced environment within which most project managers operate, it is only natural that the closeout phase of the project lifecycle is often addressed in a rush. A closeout survey using one of the many tools available today is one approach to consider.