Structures of Organisations and Projects Flashcards
Explain a Functional organisational structure
- Traditional department/discipline heads
- Work is routine
Benefits knowledge-sharing within departments.
Projects can be challenging if there’s a lack of commitment from team members, and the PM has no authority.
- Work is routine
Explain a Project organisational structure
- Cross-functional teams led by PMs
- Project Manager has authority over the work
Different functions integrate & work together better.
Inefficient resource use if staff are not 100% utilised on the project; knowledge sharing within functions is limited.
- Project Manager has authority over the work
Explain a Matrix organisational structure
- PMs have project authority; functional managers have authority for staff welfare & department efficiency
- Good for orgs that have projects and routine operations
More flexible - staff can be switched from functional to project when needed.
Can lead to conflicts between project & operational work.
- Good for orgs that have projects and routine operations
Explain what an Organisational Breakdown Structure is
The OBS shows the hierarchy of the project, e.g. workstream Project Managers reporting to the Programme Director.
Communicates the reporting structure to stakeholders.
Tasks in the Work Breakdown Structure get assigned to roles in the Organisational Breakdown Structure. Then you can create the Responsibility Assignment Matrix (which can be coded with RACI references: Responsible, Accountable, Consulted & Informed).
Project Manager role
Role: manage project & ensure successful delivery of outputs
Responsibilities: create project management plan; monitor progress; motivate team
Project Sponsor role
Role: own business case & support project manager
Responsibilities: support project manager in keeping other key senior stakeholders on side; monitor high-level progress
User role
Role: specify requirements & use deliverables
Responsibilities: explain project requirements & constraints; assist PM with handover
Project Team role
Role: carry out work packages in the WBS
Responsibilities: support PM to produce deliverables; report progress on their tasks
Project Steering Group role
Role: senior stakeholders who need to be updated with high-level progress, and approve whether project is fulfilling requirements
Responsibilities: receive high-level updates and raise any concerns with the business case
Product Owner role
Role: focus on product development and explain product needs to PM
Responsibilities: ensure project is aligned with business objectives; give feedback on work packages to team members
Embedded PMO
work controlled internally by Project Manager; for large projects that can justify the investment
Central PMO
central team servicing multiple project teams; flexible portfolio of smaller projects
Hub and Spoke PMO
central portfolio office linked to satellite embedded project/programme offices; works well when clear lines of communication & responsibility are defined
Why use project management governance?
Governance provides confidence to stakeholders that the project is being managed well and value is likely to be realised.
Why use processes in project management governance?
standardises ways of working & ensures consistent output across a large team