This is an interesting question. I'm surprised you have not had more responses by now, but I assume the project managers are busy doing...
Having spent about 20 years as a project manager, I've worked with companies at all stages of competence and maturity. Here are a few pointers to principals to keep you focused.
1. Focus is the key word, so keep your PMO and standards consistent, simple and sweet (the right amount of detail rather than two little or far too much). Use expection reporting and time banded reported to keep it fosucsed: About the Project, key documents: Plan/Interdependency/Budget, Risk/Issue Report (traffic light) ** see reference below
2. If you can't do it on one page, then you're unlikely to have most people getting through the rest. Meetings should be focused as well - whether you use Agile or other methods.
3. GIGO - beware of both "garbage in=garbage out" and people telling you what they think you want to hear so you'll go away.
4. The whole purpose of the PMO is to understand where you are, and communicate it to the project board/company board and everyone on the team. Then you need to communicate it everyone inside, outside the team who needs to be kept informed, appraised, enthused, etc about your project.
** Reference Resources: Prince2 principles (HMSO), etc.
Having spent about 20 years as a project manager, I've worked with companies at all stages of competence and maturity. Here are a few pointers to principals to keep you focused.
1. Focus is the key word, so keep your PMO and standards consistent, simple and sweet (the right amount of detail rather than two little or far too much). Use expection reporting and time banded reported to keep it fosucsed: About the Project, key documents: Plan/Interdependency/Budget, Risk/Issue Report (traffic light) ** see reference below
2. If you can't do it on one page, then you're unlikely to have most people getting through the rest. Meetings should be focused as well - whether you use Agile or other methods.
3. GIGO - beware of both "garbage in=garbage out" and people telling you what they think you want to hear so you'll go away.
4. The whole purpose of the PMO is to understand where you are, and communicate it to the project board/company board and everyone on the team. Then you need to communicate it everyone inside, outside the team who needs to be kept informed, appraised, enthused, etc about your project.
** Reference Resources: Prince2 principles (HMSO), etc.
No comments:
Post a Comment