Exactprep PMP Questions

According to the PMBOK Guide, a project manager is responsible for leading and motivating the project team and ensuring their engagement with the project. A project manager should create an environment that encourages leadership, translates ambitions into growth opportunities, and rewards overtime workers when working with a project team composed of recent university graduates. This will help to inspire, empower, and recognize the team members, and to align their personal and professional goals with the project objectives. Creating an environment that encourages leadership, translates ambitions into growth opportunities, and rewards overtime workers is the best action that the project manager should take in this situation. Providing clear direction on the work to be done and its alignment to the major objectives of the organization, using technology to communicate (A) may be a necessary action, but not sufficient to ensure the team’s engagement, as it may not address their needs, interests, and expectations. Establishing a clear hierarchical environment and allowing them to navigate through the project faster using social networks (B) may not be effective or appropriate, as it may create a rigid or bureaucratic structure, and undermine the team’s collaboration and communication. Fostering proactive decision making and developing a hierarchy to approve decisions based on different levels of complexity © may be a good practice, but not the best one, as it may not create a conducive environment for the team’s development and growth. References: PMBOK Guide, 6th edition, pages 349-350, 361-362.

 A change log is a document that contains the list of changes that are made during the project. It tracks the progress of each change based on its review, approval, implementation, and closure. A change log is a useful tool for communicating the status of change requests to the stakeholders, as it shows the impact and outcome of each change. A risk log, a backlog, and an issue log are different documents that serve different purposes. A risk log records the identified risks, their probability, impact, and response strategies. A backlog is a list of features or tasks that need to be completed in an agile project. An issue log records the issues that arise during the project, their causes, effects, and resolution. References:

• Change Log - Project Management Knowledge
• Change Log Template - Project Management Docs
• Risks, issues, and changes–help, I’m drowning in logs!

According to the PMBOK Guide, 6th edition, one of the key processes of the Project Integration Management knowledge area is Close Project or Phase, which involves finalizing all activities across all of the project management process groups to formally complete the project or phase. One of the tools and techniques for this process is benefits transition, which involves transferring the ownership of the project’s benefits to the assigned business owner or sponsor, who will be responsible for sustaining and enhancing the value of the project outcomes. By confirming ownership for ongoing value realization, the project manager can ensure that the project team members understand the benefits of the project features and how they will be measured and monitored after the project closure. References: PMBOK Guide, 6th edition, pages 123-124, 129.

Velocity is a measure of the amount of work a team can complete in a given iteration. It is calculated by dividing the total number of story points completed by the team by the duration of the iteration. Velocity can vary from iteration to iteration due to various factors such as team size, complexity of work, technical issues, etc. Therefore, it is not advisable to use a single iteration’s velocity as a baseline for future planning. Instead, the project manager should ask the product owner to look at a minimum of four to eight iterations and use the average or median velocity as a more reliable indicator of the team’s performance. This way, the product owner can replan the velocity for the next iteration based on the team’s current performance and adjust the scope and schedule accordingly. This is consistent with the agile principle of responding to change over following a plan and the PMI-PBA practice of planning and monitoring the business analysis approach. References:

• PMBOK Guide, 6th edition, page 18, section 1.2.3.2
• Agile Practice Guide, page 36, section 3.3.2
• PMI-PBA Exam Content Outline, page 9, task 1.1
• PMI-PBA Certification Exam Prep Guide, page 63, section 3.2.1