Information and Technology for Project Management
This domain tests how project information is captured, secured, reported and automated, and how technology supports the practice. Expect questions on information quality, tooling choices, metrics and data protection.
Information the practice needs
Business case and benefits baseline, plans, risk/issue/change/stakeholder/lessons registers, gate documentation, acceptance records and reports. The governing rules: a single source of truth, accuracy and timeliness, appropriate access, retention, and security classification. Registers that are not updated are worse than none, because decisions are taken on stale data.
Technology
Portfolio and project tools, collaboration platforms, workflow automation, document management, dashboards and testing tools. The guiding principle optimize and automate applies: simplify and stabilize the process before automating it. Tooling should follow the value stream, not define it.
Measurement
Distinguish lead indicators (risk trend, milestone slippage, requirement volatility) from lag indicators (cost variance, defects found). Report by exception against baselines, and prefer outcome measures over activity counts.
Worked example
A board dashboard shows milestone status against plan, budget burn against baseline, the top five risks with trend arrows, aged issues, and the latest benefit forecast. It deliberately excludes the number of meetings held and hours logged, because those measure activity, not progress toward outcomes.
Traps
Choosing a tool before agreeing the process; measuring activity instead of outcomes; storing personal or commercial data without classification and access control; assuming a dashboard replaces decision-making; letting registers go stale between gates.