767 New PMP Process Questions & Answers with explanation
321.
Match the project life cycle with its corresponding description of when planning occurs.
Matching
| Term | Description | |
|
Predictive
|
Planning occurs early in the project’s life. The plan is modified through each iteration, and work completed informs future work.
|
|
|
Iterative
|
Most of the planning occurs upfront. The team strives to identify as much detail about requirements as possible early on.
|
|
|
Incremental
|
Teams plan one or more subsets of the overall project. Completion of these deliveries informs the future wor
|
|
322.
Match the PMO type with its corresponding description.
Matching
| PMO Type | Description | |
|
Supportive
|
Serves in a management role. Assigns project managers to projects and directly manages projects
|
|
|
Controlling
|
Serves in a consultative role. Provides templates, best practices, training, and lessons learned from other projects
|
|
|
Directive
|
Serves in a supportive and compliance role. Provides project management and governance frameworks that are followed by PMs
|
|
323.
Match the term with its corresponding description.
Matching
| Term | Description | |
|
Burnup chart
|
The total time it takes to deliver an item, measured from the time the work is committed to the time it is completed
|
|
|
Lead time
|
The time required to process a work item
|
|
|
Velocity
|
A measurement of the schedule efficiency expressed as a ratio of earned to planned value
|
|
|
Cycle time
|
A visual depiction of the work completed
|
|
|
Schedule performance index
|
The sum of story point sizes for the features completed in an iteration
|
|
324.
Match the project manager’s level of authority based on the organizational structure type.
Matching
| Organizational Structure Type | Authority | |
|
Functional
|
High to almost total
|
|
|
Strong matrix
|
Low
|
|
|
Project-oriented
|
Little to none
|
|
|
Weak matrix
|
Moderate to high
|
|
325.
The characteristics of project life cycles vary and should be considered when determining which life cycle is the best fit for a project. Match the delivery life cycle approach based on where it falls on the continuum when considering frequency of delivery and degree of change.
Matching
| Life Cycle | Continuum | |
|
Predictive
|
High frequency of delivery and low degree of change
|
|
|
Iterative
|
Low frequency of delivery and high degree of change
|
|
|
Incremental
|
Low frequency of delivery and low degree of change
|
|
|
Agile
|
High frequency of delivery and high degree of change
|
|
326.
Match the Agile approach with its description.
Matching
| Agile Approach | Description | |
|
Scrum
|
Allows for continuous flow of work and value to the customer. This approach is less prescriptive and pulls single items through the process continuously.
|
|
|
Kanban
|
Used to meet the needs of a large software development project. This approach revolves around six core roles and is organized around five activities that are performed iteratively.
|
|
|
eXtreme programming
|
Used for software projects and features accelerated cycles and less heavyweight processes. This approach focuses on performing more iterative cycles across seven key disciplines and incorporates feedback before formal delivery.
|
|
|
Feature-driven development
|
A software development method based on frequent cycles. This approach attempts to distill a best practice into its simplest and purest form and then applies that practice continuously.
|
|
|
Agile unified process
|
A single-team process framework used to manage product development. This approach uses timeboxed sprints of one month or less and revolves around three core roles.
|
|
327.
Match the term with its definition.
Matching
| Term | Definition | |
|
Story points
|
A unit-less measure used in relative user story estimation techniques
|
|
|
Burndown chart
|
A visual representation of the work completed toward the release of a product
|
|
|
Burnup charts
|
The sum of story point sizes for features actually completed during the iteration
|
|
|
Velocity
|
A visual representation of the work remaining versus the time left in a timebox
|
|
328.
Match the quality theorist with the theory they are responsible for.
Matching
| Quality Theorist | Theory | |
|
Philip Crosby
|
Pareto Principle
|
|
|
Joseph Juran
|
Plan-Do-Check-Act
|
|
|
W. Edwards Deming
|
Total Quality Management (TQM)
|
|
|
Walter Shewhart
|
Zero Defects
|
|
329.
Match the project life cycle with its respective description.
Matching
| Life Cycle Name | Description | |
|
Predictive life cycle
|
A traditional approach where the majority of planning occurs up front, followed by execution of the work
|
|
|
Iterative life cycle
|
An approach that is both iterative and incremental to refine work items and deliver frequently
|
|
|
Incremental life cycle
|
An approach that provides deliverables to the customers to use immediately
|
|
|
Agile life cycle
|
An approach that allows feedback on unfinished work to improve and modify the work
|
|
330.
Match the name of the Project Management Knowledge Area with its description
Matching
| Knowledge Area Name | Description | |
|
Project Integration Management
|
Contains the activities required to manage the timely completion of the project
|
|
|
Project Schedule Management
|
Contains the activities to identify, acquire, and manage the resources needed for the successful completion of the project
|
|
|
Project Procurement Management
|
Contains the activities necessary to purchase or acquire products, services, or results needed from outside the project team
|
|
|
Project Resource Management
|
Contains the activities to identify, define, combine, unify, and coordinate the various processes and project management activities within the various process groups
|
|
|
Project Stakeholder Management
|
Contains the activities required to identify the people, groups, or organizations that could impact or be impacted by the project, analyze them, and develop strategies for engaging them
|
|