If you had a PMO with 12 team members, would you make a hierarchy for 2 teams with two team leaders? Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
No, or yes. To decide there are some factors to consider like budget and mainly the responsabilities of the leader that could determine the amount of work. For example, in my actual work place, I am the leader of teams with too much people than 12 and it works. If you ask me, without any other infomation then you posted, I will say no. Saving Changes...
To add to Sergio's feedback, I'd say you'd also need to understand the scope of work and what those 12 individuals will be doing.
Also, you use the term "PMO" - did you mean a project team, as the staffing model for a PMO is based on the services it provides to the organization and you could have one or multiple separate teams depending on those services.
Kiron Saving Changes...
Peter RapinSubject Matter Expect; Project Delivery| Independent ConsultantOntario, Canada
I would tend to let the project requirements drive the team structure rather than manipulate the projects to fit the tean structure. Structure's purpose is to manage and control rather than deliver.
Ask the question: "What is the best way to effectively deliver the projects?" rather than "How do I manage the projects to fit the structure?" Saving Changes...
Consider the workload on the team leader. If they must spend a lot of time working with individual contributors, such as to mentor a new teammate or to review and approve all work, then they may become overloaded and reduce the team efficacy.
The "management rule of 7" states that a manager is most effective when the maximum number of people reporting to them does not get too large, with the ideal number being about 7.
If most teammates can work independently and report to the leader through sub-teams, then the workload on the leader is less and larger teams can still be effective. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Mohannad,
my answer is no, if there isn't a reason coming from the environment you are working in (like 2 locations, 2 separate clients, WoW etc).
While the optimal team size is around 8, there normally is a wider spread of responsibilities in a PMO. Creating a hierarchy also has the risk of creating silos and less collaboration.
To enable teaming, trust, collaboration, communication, which I assume are the motivation for your question, there are other means.
For example, try out letting your team do a HUMM self assessment and form pairs of opposing temperaments.
This combines increasing diversity of thinking (by bringing together pairs of opposing temperaments) and adapting the concept of pair programming to your PMO tasks.
Mohannad,
When I worked in PMO's, we were more than 12 without issues. Can you explain us a little why you are considering a hierarchy? Saving Changes...
