Chapter 4

What is the technique used to plan the project work at various levels of detail depending upon the availability of information?

What do you call a WBS component at the bottom level of a branch of the WBS hierarchy for which some planning can be performed?

In rolling wave planning, work to be performed in the near future is planned at what level of the WBS?

When decomposing a work package into activities, who should be involved according to the text?

What makes the core of a project according to the text?

What is the primary purpose of the resource leveling technique?

What does resource leveling involve?

In project management, what does a what-if scenario analysis typically focus on?

When is risk planning often initiated during project management?

Which project management method factors in resource uncertainty?

What is the major task of the Define Activities process?

What is the purpose of fast tracking in project management?

In project management, what does changing the quantity of a resource committed to an activity affect?

Which technique analyzes cost and schedule tradeoffs to decrease project duration with minimal additional cost?

When measuring activity duration, what is the difference between work units and calendar units?

In project management, what is an example of crashing?

What serves as a baseline for tracking project progress in project time management?

What is the main limitation of crashing as a schedule compression technique?

Which process in project management involves determining dependencies among the activities in the activity list?

Why is it important to guard against misconceptions when applying crashing in project management?

What is the first step towards schedule planning after creating the WBS?

What serves as the starting point for defining activities in project management?

Which project management component provides key elements like deliverables, assumptions, and constraints useful in defining activities?

In project management, what is needed to define activities properly?

What technique plans project work at different levels of detail based on information availability?

What is the purpose of crashing in project management?

In project management, what does fast tracking involve?

What is the role of rolling wave planning in project management?

When defining activities in a project, what is the purpose of creating a Work Breakdown Structure (WBS)?

In resource allocation, what is an important consideration for a project manager dealing with a limited budget?

What is the purpose of decomposing a work package into activities?

What is a key constraint for sequencing activities in a project schedule?

What is the main focus of project time management?

In project management, what does WBS stand for?

Which technique plans project work at various levels based on the availability of information?

What is the consequence of not considering activity dependencies in project scheduling?

How are work packages transformed into activities in project planning?

What role does rolling wave planning play in project management?

What is the primary focus when estimating activity resource requirements?

Why is it important to control the project schedule once it has been developed and approved?

Expedite the execution is one of the actions taken to bring future schedule performance in line with the schedule baseline.

The project schedule is a static document that does not change throughout the project execution.

Root cause analysis is conducted to identify the causes of schedule variance.

Change requests for schedule-related corrective actions do not need to go through integrated change control for approval.

Schedule data is used to develop the project schedule, and it is a one-time process without any iterations.

The schedule baseline is a dynamic version of the project schedule that changes frequently during the project execution phase.

A schedule change at the project level is called a schedule revision.

Updates to project documents may include changes to resource requirements and project calendar.

All significant schedule changes must be reported only to the project team, not to stakeholders.

Crashing is a schedule compression technique that involves increasing the project duration with minimal additional cost.

The schedule performance analysis and progress report review cannot result in change requests to the project schedule baseline.

Fast tracking in project management involves completing activities in sequence to reduce project risk.

Lessons learned from the schedule control process cannot be documented for future projects.

Change requests in project management can impact the project schedule, requiring adjustments to the timeline.

The schedule management plan is not updated to reflect changes during the schedule control process.

Approved change requests can update the schedule baseline.

Progress reports play a key role in monitoring and controlling the project schedule.

Performance reviews use Earned Value Management (EVM) and Schedule Performance Index (SPI) to measure the schedule performance of a project.

Performance measurement techniques are used to analyze the schedule performance of a project.

Progress reports provide information on missed planned dates in a project.

Project management software may include a schedule change control system to evaluate and process schedule changes.

Performance measurements like schedule variance (SV) and schedule performance index (SPI) should not be documented or communicated to stakeholders.

Corrective actions in project management are solely focused on fixing past mistakes.

The output items of the schedule control process do not include recommendations for actions based on measurements and progress reports.

Schedule compression techniques, leads and lags adjustment, what-if scenario analysis are tools used in project scheduling.

Crashing and fast tracking are two techniques used in time-management processes to compress the project schedule.

Schedule data is not used in the development of the project schedule.

Performance measurements are not part of schedule control processes.

Change requests related to schedule modifications do not need to go through integrated change control for approval.

In project management, crashing involves adding additional resources to speed up activities and reduce project duration.

The approved project schedule is used as a baseline to track the project progress.

The schedule development process continues throughout project execution due to approved changes and risk occurrences.

Schedule data is used to develop the project schedule in a one-time process without any iterations.

Schedule baseline is a static document that never changes once approved.

Change requests for schedule-related corrective actions don't need to go through integrated change control for approval.

All significant schedule changes must only be reported to the project team, not stakeholders.

Fast tracking in project management involves completing activities out of sequence to reduce project risk.

Expedite the execution is one of the actions taken to bring future schedule performance in line with the schedule baseline.

The project schedule is a dynamic document that frequently changes during the project execution phase.

The main limitation of crashing as a schedule compression technique is that it increases the project duration with minimal additional cost.