Project Management Tools, Metrics, and Professional Practice Syllabus

Tools, Metrics, and Professional Practice syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Tools, Metrics, and Professional Practice in Project Management, not a summary of it.

1. 1

   Project Management Software and Tools

   3 topics

   • Scheduling Tools (MS Project, Primavera)
   • Agile Boards (Jira, Trello, Azure DevOps)
   • Collaboration and Documentation Tools
2. 2

   Metrics and Performance Measurement

   3 topics

   • Key Performance Indicators (KPIs)
   • Agile Metrics (Velocity, Lead Time, Cycle Time)
   • Value Delivery and ROI Tracking
3. 3

   Change and Configuration Management

   3 topics

   • Integrated Change Control
   • Change Control Board (CCB)
   • Organizational Change Management (ADKAR, Kotter)
4. 4

   Project Closure and Lessons Learned

   3 topics

   • Closing the Project or Phase
   • Lessons Learned and Knowledge Transfer
   • Benefits Realization and Post-Implementation Review
5. 5

   Certification Pathways

   4 topics

   • PMP and CAPM (PMI)
   • PMI-ACP and Scrum Certifications (CSM, PSM)
   • PRINCE2 Foundation and Practitioner
   • Continuing Education and PDUs

Tools, Metrics, and Professional Practice flashcards for Project Management

24 of 50 cards from the Tools, Metrics, and Professional Practice deck — real questions with worked answers.

1. What is Microsoft Project primarily used for, and what scheduling technique underlies its Gantt views?

   MS Project is a desktop/cloud scheduling tool for building work breakdown structures, task dependencies, resource assignments, and timelines. Its Gantt charts and critical-path analysis are built on the Critical Path Method (CPM).

2. How does Primavera P6 differ from MS Project in terms of typical use case?

   Primavera P6 (Oracle) is an enterprise tool built for large, complex, multi-project portfolios (construction, engineering, energy) with advanced resource leveling and portfolio management. MS Project is lighter-weight and more common for small-to-medium single projects.

3. In scheduling tools, what does 'resource leveling' accomplish?

   Resource leveling adjusts task start/finish dates to resolve over-allocation so resource demand does not exceed availability. It often extends the schedule and can change the critical path.

4. What is a Kanban board, and which tools commonly implement it?

   A Kanban board is a visual workflow tool with columns representing workflow stages (e.g., To Do, In Progress, Done) through which cards move. It is implemented in Jira, Trello, and Azure DevOps to visualize work and limit WIP.

5. What is the purpose of a WIP (Work In Progress) limit on an Agile board?

   A WIP limit caps the number of items allowed in a workflow stage at one time, exposing bottlenecks, reducing multitasking, and improving flow so work is finished before new work starts.

6. Contrast Jira and Trello for project management use.

   Trello is a simple, card-based Kanban tool suited to lightweight tasks. Jira is a robust Agile tool supporting Scrum and Kanban boards, backlogs, sprints, story points, burndown charts, and detailed reporting for software teams.

7. What is Azure DevOps Boards used for in Agile delivery?

   Azure DevOps Boards provides work-item tracking (epics, features, user stories, tasks, bugs) with Scrum and Kanban boards, backlogs, and sprint planning, integrated with source control and CI/CD pipelines.

8. Name three common categories of collaboration and documentation tools in project management.

   1) Communication (Slack, Microsoft Teams), 2) Documentation/knowledge (Confluence, SharePoint, wikis), and 3) File sharing/co-authoring (Google Workspace, OneDrive).

9. What is a KPI (Key Performance Indicator)?

   A KPI is a quantifiable metric used to evaluate the success of a project or organization against defined objectives. Good KPIs are SMART: Specific, Measurable, Achievable, Relevant, and Time-bound.

10. Distinguish a leading KPI from a lagging KPI.

    A leading KPI is predictive and measures activities that drive future results (e.g., number of tasks started). A lagging KPI measures outcomes after the fact (e.g., final cost, on-time completion), confirming past performance.

11. In Agile, what is Velocity and how is it calculated?

    Velocity is the amount of work a team completes in a sprint, measured in story points (or completed items). It is the sum of the points of stories fully completed in the sprint: $$\text{Velocity} = \sum_{i=1}^{n} \text{points}_i$$ averaged over recent sprints for forecasting.

12. Define Lead Time and Cycle Time in Agile/Kanban metrics.

    Lead Time is the total elapsed time from when a work item is requested/created until it is delivered. Cycle Time is the time from when work actually starts on an item until it is completed. Cycle Time is a subset of Lead Time.

13. State Little's Law as used in Kanban flow metrics.

    Little's Law relates average work-in-progress, throughput, and cycle time: $$\text{WIP} = \text{Throughput} \times \text{Cycle Time}$$ Rearranged: $\text{Cycle Time} = \dfrac{\text{WIP}}{\text{Throughput}}$.

14. What does a Cumulative Flow Diagram (CFD) reveal?

    A CFD plots the number of items in each workflow state over time. Widening bands signal bottlenecks/growing WIP; the horizontal gap approximates lead time and the vertical gap approximates WIP.

15. What is Throughput as an Agile metric?

    Throughput is the number of work items (or story points) completed per unit of time (e.g., per sprint or per week). It measures the team's delivery rate/output.

16. What is a burndown chart, and what does its ideal line represent?

    A burndown chart plots remaining work (points or hours) on the y-axis against time on the x-axis. The ideal line is a straight descent to zero at sprint end; the actual line above it means the team is behind, below it means ahead.

17. What is Return on Investment (ROI) and how is it calculated?

    ROI measures the profitability of an investment relative to its cost: $$\text{ROI} = \frac{\text{Net Benefit}}{\text{Cost of Investment}} \times 100\%$$ where Net Benefit = Total Benefits $-$ Cost.

18. Define Net Present Value (NPV) and its decision rule.

    NPV is the sum of discounted future cash flows minus initial investment: $$\text{NPV} = \sum_{t=0}^{n} \frac{C_t}{(1+r)^{t}}$$ Rule: accept the project if $\text{NPV} > 0$; among options, choose the highest NPV.

19. What is the Internal Rate of Return (IRR)?

    IRR is the discount rate $r$ at which a project's NPV equals zero: $$\sum_{t=0}^{n} \frac{C_t}{(1+r)^{t}} = 0.$$ A higher IRR is preferable; accept if IRR exceeds the required rate of return.

20. What does 'value delivery' mean in modern (PMI) project management?

    Value delivery is the focus on producing measurable business outcomes and benefits for stakeholders throughout the project—not just outputs. PMI frames projects as part of a value delivery system connecting strategy to realized benefits.

21. What is the Payback Period, and what is its main limitation?

    The Payback Period is the time required for cumulative benefits to recover the initial investment: $\text{Payback} = \dfrac{\text{Initial Investment}}{\text{Annual Cash Inflow}}$ (for even flows). Limitation: it ignores the time value of money and cash flows after payback.

22. What is Integrated Change Control (ICC) in PMI's framework?

    Perform Integrated Change Control is the process of reviewing all change requests; approving, deferring, or rejecting them; and managing changes to deliverables, documents, and the project management plan in a coordinated way across all knowledge areas.

23. What are the four possible dispositions of a change request in integrated change control?

    A change request can be Approved, Rejected, Deferred (postponed), or sent back for more information. Approved changes are then implemented and verified.

24. What is a Change Control Board (CCB), and what is its role?

    A CCB is a formally chartered group of stakeholders responsible for reviewing, evaluating, approving, deferring, or rejecting change requests to a project, and for recording those decisions. Its authority is defined in the change management plan.

See more Tools, Metrics, and Professional Practice flashcards →

Planning Tools, Metrics, and Professional Practice for Project Management

Tools, Metrics, and Professional Practice (Project Management) FAQ