Project Management Configuration
About 21% of the CIS-SPM exam — see all 10 domains.
The other heaviest domain. This is PPM, the execution layer for funded work.
Project Workspace. The modern, configurable workspace that unifies planning, resourcing, financials, risk, and reporting for a project in one connected UI. Areas include the planning page (data grid and Gantt timeline), Resources, Financials, RIDAC (risks, issues, decisions, actions, change requests), and Status reports. Project Workspace has no board view of its own; boards come from Collaborative Work Management.
Work Breakdown Structure (WBS) & Planning Console. The Planning Console is the central interface giving the project manager a hierarchical view of the project: sub-projects and project tasks shown as a work breakdown structure (WBS), with a Gantt chart, milestones, dependencies/relations (e.g., finish-to-start), critical path, baselines, and rollup of dates/effort. Zurich documents the Planning Console as legacy; the Project Workspace planning page is the current experience. The Planning tab in Project Workspace brings WBS, Gantt, milestones, and task dependencies together.
Project methodology & states. Projects can run Waterfall, Agile, or Hybrid. Project states are the State field choices: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, Closed Skipped; the state rolls up from project tasks, and custom states are added per state type with dictionary overrides. Status report health (overall, schedule, cost, resources, scope) is shown in green, yellow, and red.
Status reports. Project managers publish periodic status reports capturing overall status, schedule/cost/scope/resource health, accomplishments, and upcoming work; newer releases offer AI-generated status report drafts. Status feeds portfolio dashboards.
Project tasks & scheduling. Tasks carry planned/actual start and end, % complete, planned duration, planned effort, assignment, and dependency relations (Finish to Start and others, with lag). Planned duration and planned effort are separate estimates; parent planned effort becomes read-only and rolls up from child tasks, and percent complete is entered or rolled up from child tasks (time cards update actual effort, not percent complete). The Time constraint field offers only Start ASAP, Start on specific date, Start no earlier than, and Start no later than; there are no finish constraints and no backward scheduling. A project uses Automatic or Manual calculation, and Start ASAP tasks are scheduled from the project's constraint date (its planned start, changed with Move Project).
Configuration topics likely tested: project templates, the planning console (rescheduling, relations, top-down vs. bottom-up tasking), project state flows, status report cadence/configuration, copying/templating projects, Project Workspace configuration, and conversion from demand to project.
Sample questions from this domain
Three of the 63 in this domain, with the reasoning. The full set is in the question bank.
Which structure organizes a project's deliverables into a hierarchy of phases, tasks, and milestones?
- A. Project task checklist items
- B. Work Breakdown Structure (WBS) ✓
- C. Program Workbench timeline view
- D. Portfolio Planning roadmap item
Why: The Work Breakdown Structure hierarchically organizes a project's phases, tasks, and milestones (each task carries a WBS number, which is also used in dependency values such as 1.1fs+0). Project task checklists list items to complete inside a single task, the Program Workbench shows the projects and demands of a program, and a Portfolio Planning roadmap item places planning items on a strategic timeline. None of them is the project's task hierarchy.
A project milestone is best described as:
- A. A summary task whose dates and duration roll up from the child tasks placed beneath it
- B. A task using the Start on specific date constraint so dependencies do not shift it
- C. A zero-duration marker representing a significant point or deliverable in the schedule ✓
- D. A schedule baseline line drawn in gray beneath the task bars on the Gantt chart
Why: A milestone is a project task with a duration of zero that marks a key point such as a decision, approval, or deliverable, and it appears as a diamond on the Gantt chart. A summary (parent) task rolls up dates and duration from its children, the Start on specific date constraint fixes a task's start but does not make it a milestone, and the gray lines under task bars show schedule baseline dates.
Which task dependency type means a successor task cannot start until its predecessor finishes?
- A. Start-to-Finish (SF)
- B. Finish-to-Finish (FF)
- C. Finish-to-Start (FS) ✓
- D. Start-to-Start (SS)
Why: Finish-to-Start (entered, for example, as 1.1fs+0) means the successor starts only after the predecessor finishes; it is also the only type supported for external dependencies between projects. Start-to-Start, Finish-to-Finish, and Start-to-Finish link other combinations of start and finish dates, so none of them makes the successor's start wait for the predecessor's finish.