IT Project Governance Flashcards
7 cards from real CSI practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 IT Project Governance flashcards as text
A governance board wants to implement Key Performance Indicators (KPIs) for IT system integration projects. Which KPI BEST measures project delivery effectiveness?
Answer: Schedule Performance Index (SPI) and Cost Performance Index (CPI)
SPI and CPI from Earned Value Management directly measure schedule and cost efficiency relative to planned baselines.
What governance mechanism ensures that lessons from one IT integration project are applied to future projects within the same organization?
Answer: Project closure report filed in a shared knowledge base
A shared knowledge base containing lessons learned and closure reports enables organizational learning across projects.
A system integration project has three vendors with overlapping scopes. From a governance perspective, what is the MOST important document to establish?
Answer: Clear interface control documents with defined responsibilities per vendor
Interface control documents define technical and contractual boundaries between vendors, preventing scope conflicts and governance gaps.
Which governance practice BEST prevents 'zombie projects' — projects that continue consuming resources despite no longer delivering value?
Answer: Regular portfolio reviews with criteria-based termination authority
Periodic portfolio reviews with clear kill criteria empower governance bodies to terminate projects that no longer align with strategy or ROI targets.
An IT project governance framework requires all projects above $500K to have an independent quality assurance (IQA) review. A $480K project skips IQA. What governance issue is this?
Answer: A policy exception that should be formally documented and approved
Even when below a threshold, deviations from governance policy should be formally documented to maintain audit trails and accountability.
In agile IT projects, how does governance typically adapt compared to traditional waterfall projects?
Answer: Governance uses lightweight checkpoints and outcome-based reviews aligned with sprints
Agile governance shifts from document-heavy gates to frequent outcome reviews at sprint boundaries, balancing oversight with agility.
A CSI project's configuration management plan has not been updated for three months despite significant system changes. What governance risk does this represent?
Answer: Loss of baseline control, making audits and rollback unreliable
Outdated configuration management compromises the ability to audit, reproduce, or roll back system states, undermining integration integrity.