| 🏠 Back to Exam Syllabus | 📺 RooCloud on YouTube | 🌐 RooCloud Practice Exams |
Project Governance & Management (Part 1 of 2)
This opening episode of the Project Governance and Management section of the ISACA Certified Information Systems Auditor (CISA) exam prep series introduces the foundations of how projects are governed and managed within an enterprise. It covers why projects need governance, how project teams are structured and who fills key roles, how time, money, and deliverables balance against each other, and how programs and portfolios organize work above the level of individual projects.
What this episode covers
- Why project governance is needed — the structures, policies, and controls that keep work aligned with business goals and risk appetite from charter to close.
- Project management defined — running a repeatable business process through the stages of initiating, planning, executing, controlling, monitoring, and closing.
- Three team structures — functional, projectized, and matrix structures and how authority is distributed in each.
- Key project roles — the steering committee, senior management, project sponsor, user management, project manager, quality assurance, systems development, security officer, and privacy officer.
- The triple constraint — how deliverables, duration, and budget pull against each other and the practical limits at each extreme.
- Programs and portfolios — how programs group related projects that share strategies and budgets, and how a portfolio encompasses the full enterprise project set.
- Project management office and benefits realization — the permanent governance body that lifts project quality, and the practice of tracking whether investment actually pays off over the life of a system.
Watch the full episode above for the worked examples and detailed explanations of each concept.
Frequently Asked Questions
What are the three common project team structures and how do they differ?
In a functional structure the project manager has no real authority; work stays inside departments and the manager can only advise. In a projectized structure the project manager holds full authority over budget, schedule, and team. In a matrix structure authority is shared between the project manager and department heads, blending elements of both approaches.
How do deliverables, duration, and budget constrain each other on a project?
The three elements pull against each other because demanding deliverables usually mean longer timelines and bigger budgets. Resources multiplied by duration tends to stay roughly constant, so using few people makes a project drag on while throwing many at it shrinks the timeline, but there are practical limits at both ends since too long is unacceptable and too many hands becomes unmanageable.
What is the difference between a project, a program, and a portfolio?
A project is a bounded piece of work with defined goals, budget, and deadline. A program is a tight group of related projects and tasks that share strategies, objectives, budgets, and schedules, and is typically bigger, longer, riskier, and more strategic than a single project. A portfolio is the complete set of all projects running in the enterprise at a given time.
What is benefits realization, and why does it matter?
Benefits realization makes sure a completed project actually delivers the value the investment was intended to produce by looking past the project close to the full life of the new system. It requires naming each benefit, setting a target, tracking it over time, documenting assumptions, and assigning someone to own each benefit.
📚 Master the ISACA CISA Exam!
Ready to test your knowledge? Access chapter-specific Multiple Choice Questions (MCQs) and full-length practice exams for the ISACA CISA certification at RooCloud.com. Solve the chapter-wise questions to reinforce this lesson before moving to the next episode.
Reference: This article is based on concepts discussed in Project Governance & Management (Part 1 of 2).