Information Systems and IT Project Management
What this domain tests
Information Systems and IT Project Management tests how systems support business processes and how projects are planned and controlled. Expect IS components, project constraints, WBS, dependencies, critical path, risk, and stakeholder management.
Core rules and concepts
- An IS combines people, processes, data, software, and hardware. ERP integrates core business functions; CRM manages customer interactions.
- The triple constraint is scope, time, and cost, with quality affected by all three. Changing one requires rebalancing.
- A WBS decomposes deliverables into work packages. Dependencies determine sequence; the critical path is the longest path through the network and sets the minimum duration.
- Float (slack) is how long a task can slip without delaying the project. Critical-path tasks have zero float.
- Risk management identifies, analyzes, plans responses, and monitors. Change control prevents uncontrolled scope creep.
Worked example
Tasks: A=3 days; B=2 after A; C=4 after A; D=2 after B and C. Paths: A–B–D = 3+2+2 = 7 days; A–C–D = 3+4+2 = 9 days. The critical path is A–C–D at 9 days. B has 2 days of float because it can finish at day 5 while C finishes at day 7; D cannot start until C finishes.
Traps that cost marks
Choosing the shortest path as critical. Confusing crashing (add resources, raise cost) with fast tracking (overlap tasks, raise risk). Gold-plating features nobody requested. Ignoring stakeholders or failing to baseline scope.