Ewan WaughProgram Manager| Resonate UCCAberdeen, United Kingdom
Hi everyone,
I have recently joined my company (We do deployment, management, support and consultancy in deploying Microsoft Teams & Skype) and as part of my development I have been tasked with building out the processes and procedures around the operations space to ensure that (as we expand) there is a clear set of processes and procedures for new employees to following.
Can I ask if there are any resources that the community here can recommend as a good up to date resource in the requirements around these structures to ensure a successful (and well scaled) PMO.
Any help appreciated thanks everyone! Cheers Ewan Saving Changes...
Hi Ewan,
That's a great question! Can I ask a few questions, first?
- What are the current processes in place?
- What is the maturity around these processes?
Regarding the resources available, there's a few things that I can think of but they're a little high level rather than the detailed that you're looking for. If you can let me know the maturity level, i'll see what i can find for you!
Best regards,
Emily Saving Changes...
Ewan WaughProgram Manager| Resonate UCCAberdeen, United Kingdom
Thanks for getting back Emily,
At present any processes that we use for setup & management of
Projects is based upon the collected best-practice and experience of the PMs that we have. This is documented in the templates we have from previous engagements and our own collected certification & documentation. So alot of experience and knowledge there just no formal wrapper around it in terms of how it is used.
In terms of maturity the company is about 5 years old so we have as I say alot of collected experience and best practices in terms of ways of working but its now time for us to formalise this.
Hope that helps and thanks for responding!
Ewan Saving Changes...
I'm a bit unclear as to the mandate for a PMO as this sounds much more operations-focused, in which case, libraries such as ITIL are likely to be a better fit?
In general, when setting up a PMO:
1. Ensure there is a clear mandate which has been shared and understood by all key stakeholders.
2. Plan and implement the PMO's setup like any other strategic project.
3. Focus on value over control - it is better to educate practitioners on control objectives and let them determine the way to achieve those than to be too prescriptive, especially in the early days.
Like Kiron, ITIL was what came to mind when reading your question. Perhaps, you meant program, rather than project, management office?
Capturing processes and procedures is a laudable goal. In these days of agile approaches, you might want to use a flexible approach that allows for the (r)evolution of your organizational process assets. Your new employees might find the documented processes and procedures stifling. Saving Changes...
Hello,
I agree with all (Emily ,Kiron and stephane).
-level of maturity (5 phases )
-Tie the PMO's objectives to organization's objectives
and strategy (to be aligned)
- Value over control.
-Be customer focused.
There is NO standards for how to organize PMO and there is NO standards process for PMO, (However PMO have varied success rate).
BR,
Mansour Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Creating a PMO is like creating any other business unit inside the company. It is a strategical decesion. Strategy is the way the company answer to environmental stimuli in order to achieve their objectives which basically are survive, growth and develop. So, the first question is: have the company decided that project management functions/process needs to be included as part of the strategy?. If the answer is yes, after selected what functions/process (at this time you will have to decide if stated by PMI, IPMA, GPM, or others) the company must decide if a new physical business unit deserves to be created or not (the process/functions will be located in different existent business unit). If the answer is yes then the business unit is created. Is time to create the architecture for the PMO. You have to take into account a pyramid: approach in the basement (Agile, Lean, PMI, etc etc), life cycle models to use (adaptative, prescriptive), life cycle process based on those models (waterfall, iterative, incremental, etc), methods based on those life cycle process (agile based, non-agile based, own method, etc), tools to support those methods (where tools are not software tools only). When you have the architecture then you can move forward. At the end, you are creating a solution for a business problem. Perhaps this helps: https://www.projectmanagement.com/blog-pos...-right-solution Saving Changes...
Ewan WaughProgram Manager| Resonate UCCAberdeen, United Kingdom
All - Thanks for all the responses much appreciated. Will proceed with the knowledge I have to hand and if I have any other specific questions revert back. Have a great weekend! Saving Changes...
