PMP Terms 30

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
full-widthPodcast
1
Card Sorting

1/9

encourage image

There's no tags or description

Looks like no tags are added yet.

10 Terms

1
New cards

Monitor Risks

Tracks identified risks, checks whether planned responses are being carried out and working, and looks for new risks throughout the project. Risk identification is revisited as the team learns more; it is not limited to the initial planning session.

What it involves:

  • Reassess existing risks: have their likelihood, impact, or triggers changed?

  • Check whether responses were implemented and whether they reduced the risk.

  • Identify new risks, update the risk register, and revise responses when needed.

When to use:

Throughout the project, including at regular risk reviews and after significant changes or new information.

Example — Izzy’s Ice Cream:

The team reviews its risk that a vendor might deliver ordering tablets late. The tablets arrived, so that risk can be closed. During the same review, a pilot store reports unreliable Wi-Fi—a newly identified risk to the wider rollout. The team records it, assesses its impact, and plans a response before more stores go live.

Memory hook: Revisit old risks → check responses → find new risks.

2
New cards

Technical Performance Analysis

Compares measurable technical results achieved during the project with the technical targets expected by that point. A gap can provide early warning of a threat to the project’s objectives or reveal an opportunity.

What it involves:

  • Set objective measures and targets for technical milestones.

  • Measure actual results and compare them with the targets.

  • Investigate meaningful gaps and assess what they imply for future project risk.

When to use:

When technical performance can signal whether the project is likely to meet its requirements—not just whether the work is on schedule.

Example — Izzy’s Ice Cream:

The new ordering system is supposed to process an order in two seconds during a pilot. Testing shows that it takes five seconds when several stores order at once. The team investigates whether that gap threatens the planned companywide launch and updates its risk assessment.

Memory hook: Compare technical results with targets → spot risk early.

3
New cards

Monitor and Control Resourcing

Ensures the project’s physical and virtual resources are available when and where needed. It compares planned use with actual use, corrects shortages or overuse, and releases resources when they are no longer needed. Team member performance is addressed separately under Lead the Team.

What it involves:

  • Check availability and actual use of equipment, materials, facilities, software, licenses, testing environments, and services.

  • Resolve shortages or surpluses before they disrupt the work.

  • Update allocations and release resources at the appropriate time.

When to use:

Continuously during the project, especially when a needed resource is delayed, unavailable, or being used differently from the plan.

Example — Izzy’s Ice Cream:

The rollout plan assigns test tablets to three pilot stores, but one store has not received them and another has extras. The project manager confirms the inventory, moves the spare tablets where they are needed, and updates the allocation so testing can proceed.

Memory hook: Right resources → right place and time → release when done.

4
New cards

Value Stream Mapping

Draws the steps work passes through to deliver value, including handoffs, waiting, and rework. Seeing the whole flow helps the team find delays and waste that are easy to miss when each step is considered on its own.

What it involves:

  • Map the steps from a request or idea through delivery.

  • Show time spent doing work and time spent waiting between steps.

  • Locate bottlenecks, repeated handoffs, and loops back to earlier work; then improve the flow.

When to use:

When delivery is slow and the team needs to see where the time goes before deciding what to change.

Example — Izzy’s Ice Cream:

The team maps how the new ordering system reaches a store. Configuration takes two days and testing takes one, but stores wait eight days between those steps for approval to use the test environment. The map reveals that the approval queue—not the technical work—is the main source of delay.

Memory hook: Map the whole journey → find the waiting and rework.

5
New cards

Control Charts

Plot process results over time to help determine whether a process is stable and predictable. A center line shows the mean; statistically calculated upper and lower control limits show the range expected from normal process variation.

What to look for:

  • A point outside a control limit calls for investigation.

  • A nonrandom pattern can also signal a change, even if every point remains within the limits.

  • Specification limits come from requirements. They answer a different question: Is the result acceptable? A stable process can still miss a requirement.

When to use:

When repeated results—such as defects or service times—need to be assessed over time for unusual variation.

Example — Izzy’s Ice Cream:

Izzy’s requires orders to be ready within 12 minutes, but its chart has an upper control limit of 15 minutes. A 13-minute result is within the process’s control limit yet misses the requirement. Being within control does not mean meeting the requirement.

Memory hook: Control limits = what the process does. Specification limits = what is allowed.

<p>Plot process results over time to help determine whether a process is stable and predictable. A center line shows the mean; statistically calculated upper and lower <strong>control limits</strong> show the range expected from normal process variation.</p><p><strong>What to look for:</strong></p><ul><li><p>A point outside a control limit calls for investigation.</p></li><li><p>A nonrandom pattern can also signal a change, even if every point remains within the limits.</p></li><li><p><strong>Specification limits</strong> come from requirements. They answer a different question: <em>Is the result acceptable?</em> A stable process can still miss a requirement.</p></li></ul><p><strong>When to use:</strong></p><p>When repeated results—such as defects or service times—need to be assessed over time for unusual variation.</p><p><strong>Example — Izzy’s Ice Cream:</strong></p><p>Izzy’s requires orders to be ready within <strong>12 minutes</strong>, but its chart has an upper control limit of <strong>15 minutes</strong>. A 13-minute result is within the process’s control limit yet misses the requirement. Being <em>within control</em> does not mean <em>meeting the requirement</em>.</p><p><strong>Memory hook:</strong> Control limits = what the process does. Specification limits = what is allowed.</p>
6
New cards

Rule of Seven

Seven consecutive points on the same side of a control chart’s mean are a signal to investigate. They may indicate that the process has shifted, even when every point is still within the control limits. The seven points can be above or below the mean.

When to use:

When reading a control chart for patterns that a check of individual points might miss. Investigate the cause before deciding what corrective action, if any, is needed.

Example — Izzy’s Ice Cream:

Order times on days 8 through 14 are all above the chart’s mean, though none exceeds the upper control limit. Day 14 is the seventh consecutive point, so the team investigates whether something changed in how orders are prepared.

Memory hook: Seven together on one side → investigate the shift.


<p>Seven consecutive points on the <strong>same side of a control chart’s mean</strong> are a signal to investigate. They may indicate that the process has shifted, even when every point is still within the control limits. The seven points can be <strong>above or below</strong> the mean.</p><p><strong>When to use:</strong></p><p>When reading a control chart for patterns that a check of individual points might miss. Investigate the cause before deciding what corrective action, if any, is needed.</p><p><strong>Example — Izzy’s Ice Cream:</strong></p><p>Order times on <strong>days 8 through 14</strong> are all above the chart’s mean, though none exceeds the upper control limit. <strong>Day 14 is the seventh consecutive point</strong>, so the team investigates whether something changed in how orders are prepared.</p><p><strong>Memory hook:</strong> Seven together on one side → investigate the shift.</p><p></p>
7
New cards

Close Project or Phase

Finalizes the work of a project, phase, release, iteration, or contract—whether it succeeded or ended early. It confirms what was completed, what was formally accepted, and what still needs to be handed off or resolved.

What it involves:

  • Confirm completion or exit criteria and obtain appropriate acceptance.

  • Transition the finished product, service, or result to its recipient.

  • Finish remaining administrative and contractual work, capture lessons learned, archive records, and release resources.

When to use:

At the end of a project or defined portion of one, including when work is canceled before completion.

Example — Izzy’s Ice Cream:

The new ordering system has passed its acceptance checks. The project manager confirms the sponsor’s acceptance, hands the system and support instructions to operations, closes the vendor agreement, and archives the project records.

Memory hook: Confirm → hand off → close out.

8
New cards

Preparing the Final Report at Closure

Uses project records and performance data to establish what actually happened and explain the results. The report should be supported by evidence, including the original objectives, approved changes, measured performance, and lessons learned.

What it involves:

  • Review the charter, project management plan, business case, and relevant documents such as the assumption, change, issue, and lessons learned logs.

  • Analyze actual scope, quality, cost, schedule, risks, and issues against what was planned or approved.

  • Explain significant successes and variances, including their causes and effects.

When to use:

During closure, after enough final results are available to assess the project or phase.

Example — Izzy’s Ice Cream:

The rollout finished two weeks later than planned. The project manager checks the milestone dates, issue log, vendor records, and approved changes. The final report explains the delay and shows whether the ordering system met its agreed objectives.

Memory hook: Gather the records → analyze the results → explain what happened.

9
New cards

Final Product, Service, or Result Transition

Transfers what the project produced to the customer, operations team, or other group that will use, operate, or support it. The receiving group needs to know what it is accepting and what responsibilities it is taking over.

What it involves:

  • Confirm acceptance by the appropriate people and identify who receives the result.

  • Provide the documentation, access, training, and support information needed for use or operation.

  • Make outstanding items, deferred work, and relevant vendor or warranty arrangements clear to the recipient.

When to use:

During closure, when the accepted result is ready to pass from the project team to its ongoing owner or user.

Example — Izzy’s Ice Cream:

The sponsor accepts the new ordering system. The project team gives operations the administrator access, support instructions, vendor contact details, and completed training materials. It also identifies a reporting feature deferred to a later phase, so operations knows what is and is not included.

Memory hook: Accepted result → prepared recipient → clear handoff.

10
New cards

Final Report Contents

Summarizes how the project or phase performed against its objectives and what was achieved. It explains significant differences between planned and actual results rather than merely listing final numbers.

What to include, as applicable:

  • Scope and quality: What was delivered, the completion and quality criteria, and evidence they were met.

  • Cost and schedule: Actual results and reasons for significant variances.

  • Validation, risks, and issues: Acceptance or other validation evidence, important problems, and how they were addressed.

  • Business need and benefits: What value has been achieved at closure and which expected benefits still need tracking afterward.

When to use:

At closure, to give stakeholders and the organization an evidence-based account of the outcome.

Example — Izzy’s Ice Cream:

The report records that all planned stores received the accepted ordering system. It explains a two-week rollout delay, summarizes the resolved pilot issues, and notes that operations will measure whether order errors decline over the next three months.

Memory hook: What did we deliver, how did we perform, and what value follows?