Cisco®
Oracle
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
All Vendors
  2. Home
  3. Exams
  4. PMI
  5. CAPM

Free PMI CAPM Exam Braindumps (page: 50)

Page 50 of 276
PDF with 1163 Questions

Which process involves determining, documenting, and managing stakeholders' needs and requirements to meet project objectives?

  1. Collect Requirements
  2. Plan Scope Management
  3. Define Scope
  4. Define Activities

Answer(s): A

Explanation:

Process: 5.2 Collect Requirements
Definition: The process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
Key Benefit: The key benefit of this process is that it provides the basis for defining and managing the project scope including product scope.
Inputs
1. Scope management plan
2. Requirements management plan
3. Stakeholder management plan
4. Project charter
5. Stakeholder register

Tools & Techniques
1. Interviews
2. Focus groups
3. Facilitated workshops
4. Group creativity techniques
5. Group decision-making techniques
6. Questionnaires and surveys
7. Observations
8. Prototypes
9. Benchmarking
10. Context diagrams
11. Document analysis

Outputs
1. Requirements documentation
2. Requirements traceability matrix



Plan Communications Management develops an approach and plan for project communications based on stakeholders' needs and requirements and:

  1. Available organizational assets
  2. Project staff assignments
  3. Interpersonal skills
  4. Enterprise environmental factors

Answer(s): A

Explanation:

Process: 10.1 Plan Communications Management
Definition: The process of developing an appropriate approach and plan for project communications based on stakeholder’s information needs and requirements, and available organizational assets.
Key Benefit: The key benefit of this process is that it identifies and documents the approach to communicate most effectively and efficiently with stakeholders.

Inputs
1. Project management plan

2. Stakeholder register
3. Enterprise environmental factors
4. Organizational process assets

Tools & Techniques
1. Communication requirements analysis
2. Communication technology
3. Communication models
4. Communication methods
5. Meetings

Outputs
1. Communications management plan
2. Project documents updates



Perform Integrated Change Control is the process of:

  1. Reviewing, approving, and managing all change requests
  2. Facilitating change management, manuals, or automation tools
  3. Comparing actual results with planned results in order to expand or change a project
  4. Documenting changes according to the change control system by the change control board

Answer(s): A

Explanation:

Process: 4.5 Perform Integrated Change Control
Perform Integrated Change Control is the process of reviewing all change requests; approving changes and managing changes to deliverables, organizational process assets, project documents, and the project management plan; and communicating their disposition. It reviews all requests for changes or modifications to project documents, deliverables, baselines, or the project management plan and approves or rejects the changes.
Key Benefit: The key benefit of this process is that it allows for documented changes within the project to be considered in an integrated fashion while reducing project risk, which often arises from changes made without consideration to the overall project objectives or plans.

Inputs
1. Project management plan
2. Work performance reports
3. Change requests
4. Enterprise environmental factors
5. Organizational process assets

Tools & Techniques
1. Expert judgment
2. Meetings
3. Change control tools

Outputs
1. Approved change requests
2. Change log
3. Project management plan updates
4. Project documents updates



When painting a bedroom, preparing the walls can be done while the paint is being chosen. This is an example of a:

  1. lead
  2. lag
  3. mandatory dependency
  4. internal dependency

Answer(s): A

Explanation:

6.3.2.2 Dependency Determination
Dependencies may be characterized by the following attributes: mandatory or discretionary, internal or external, as described below. Dependency has four attributes, but two can be applicable at the same time in following ways: mandatory external dependencies, mandatory internal dependencies, discretionary external dependencies, or discretionary internal dependencies.
Mandatory dependencies. Mandatory dependencies are those that are legally or contractually required or inherent in the nature of the work. Mandatory dependencies often involve physical limitations, such as on a construction project, where it is impossible to erect the superstructure until after the foundation has been built, or on an electronics project, where a prototype has to be built before it can be tested. Mandatory dependencies are also sometimes referred to as hard logic or hard dependencies. Technical dependencies may not be mandatory. The project team determines which dependencies are mandatory during the process of sequencing the activities. Mandatory dependencies should not be confused with assigning schedule constraints in the scheduling tool.
Discretionary dependencies. Discretionary dependencies are sometimes referred to as preferred logic, preferential logic, or soft logic. Discretionary dependencies are established based on knowledge of best practices within a particular application area or some unusual aspect of the project where a specific sequence is desired, even though there may be other acceptable sequences. Discretionary dependencies should be fully documented since they can create arbitrary total float values and can limit later scheduling options. When fast tracking techniques are employed, these discretionary dependencies should be reviewed and considered for modifcation or removal. The project team determines which dependencies are discretionary during the process of sequencing the activities.
External dependencies. External dependencies involve a relationship between project activities and non- project activities. These dependencies are usually outside the project team’s control. For example, the testing activity in a software project may be dependent on the delivery of hardware from an external source, or governmental environmental hearings may need to be held before site preparation can begin on a construction project. The project management team determines which dependencies are external during the process of sequencing the activities.
Internal dependencies. Internal dependencies involve a precedence relationship between project activities and are generally inside the project team’s control. For example, if the team cannot test a machine until they assemble it, this is an internal mandatory dependency. The project management team determines which dependencies are internal during the process of sequencing the activities.



Viewing page 50 of 276
Viewing questions 197 - 200 out of 1163 questions



Post your Comments and Discuss PMI CAPM exam prep with other Community members:

CAPM Exam Discussions & Posts