Selected CAPM CAPM Questions Answers

According to the Agile Practice Guide and the PMBOK® Guide, the choice of an adaptive lifecycle depends on the nature of the work. Support and maintenance environments are characterized by high variability and the need for a " pull-based " system.

Why Choice C is correct: Kanban is the ideal method for " continuous flow " work where tasks cannot be planned in time-boxed iterations (like Scrum Sprints).

Work in Progress (WIP) Limits: The scenario states the team cannot start new issues until they finish existing ones. This is the core principle of WIP limits in Kanban. By limiting how much work can be " In Progress, " the team prevents bottlenecks and ensures they focus on completing tasks before taking on new ones.

On-Demand Planning: Since support issues are unpredictable, Kanban allows the team to pull the next highest-priority item from the backlog as soon as capacity becomes available, rather than waiting for a new sprint cycle.

Analysis of other options:

A (SAFe®): The Scaled Agile Framework (SAFe®) is designed for large-scale, multi-team development. The description provided in the option ( " it does not allow for scaling " ) is factually incorrect, as SAFe is specifically built for scaling.

B (Extreme Programming - XP): XP is a software development methodology focused on technical excellence (e.g., pair programming, test-driven development). While it emphasizes quality, it does not fundamentally dictate the flow of work for unpredictable support issues as effectively as Kanban.

D (Scrum): Scrum relies on Sprints (time-boxes). If a team cannot plan their work even for a week, Scrum ' s " Sprint Planning " becomes impossible. Furthermore, the statement that Scrum allows for " completing the whole architecture up front " is incorrect; that describes a Waterfall/Predictive approach, whereas Scrum is iterative.

In a production support environment, the Lead Time and Cycle Time metrics used in Kanban provide the visibility needed to manage a reactive workload without the overhead of rigid sprint structures.

According to the PMBOK® Guide, specifically within the Plan Resource Management process, the Project Organization Chart is the formal tool used to document and communicate project roles and reporting relationships.

Definition: A Project Organization Chart is a graphic display of project team members and their reporting relationships. It provides a visual representation of the project hierarchy, ensuring that every team member understands who they report to and who is responsible for specific tasks or segments of the project.

Purpose: The primary goal of this chart is to clarify the command structure and minimize confusion regarding authority and communication channels. It can be formal or informal, highly detailed or broadly framed, based on the specific needs of the project.

Data Representation: While other tools like the Resource Responsibility Matrix (RAM) or RACI chart show the relationship between work packages and team members, the Organization Chart focuses specifically on the reporting hierarchy of the people involved.

Choice A, B, and D are incorrect because they use non-standard terminology. While they sound plausible in a general business context, they are not the specific terms defined in the PMBOK® Guide or the PMI Lexicon of Project Management Terms.

In the PMBOK® Guide, a project manager often acts as a negotiator and facilitator when there are conflicting requirements or perspectives between key stakeholders. This scenario highlights a conflict between Quality/Compliance (Testing Manager) and Business Utility (Business Unit Manager).

Why Choice B is correct:

Stakeholder Management: The first step in resolving any conflict is to facilitate communication. By bringing both managers together, the Project Manager allows them to align on the " Definition of Done " and the " Minimum Viable Product " (MVP).

Understanding Trade-offs: The Business Unit Manager might find the software " good enough " for immediate needs, while the Testing Manager might be worried about long-term stability or technical debt. A meeting allows for a risk-based decision: can the rollout proceed with known issues, or are the missing features critical?

Conflict Resolution: According to PMI, Collaborating/Problem Solving (win-win) is the preferred conflict resolution technique. This meeting provides the platform to reach a consensus or a compromise without immediate escalation.

Analysis of other options:

A (Escalate to the PMO): Escalation should be a last resort. The PMO provides guidance and templates, but they are not typically responsible for resolving functional disputes between mid-level managers until the Project Manager has attempted to facilitate a resolution.

C (Resolve all open issues): While this sounds proactive, it ignores the Business Unit Manager ' s request to start the rollout now. It also assumes the project has the time and budget to fix everything immediately, which may not be the case in an iterative environment where some features are intentionally deferred to future iterations.

D (Escalate to the sponsor): Similar to Choice A, skipping straight to the Sponsor (the person providing the money/resources) is premature. The Sponsor expects the Project Manager to manage stakeholder expectations and only bring " unresolvable " issues to their attention.

Key Concept: The Project Management Institute (PMI) emphasizes that a Project Manager must be an Integrator. By organizing a meeting (Choice B), the PM ensures that the rollout decision is informed by both technical quality standards and business necessity, ensuring that the final path forward is documented and agreed upon by both parties.

According to the PMBOK® Guide, the Control Procurements process is the process of managing procurement relationships, monitoring contract performance, making changes and corrections as appropriate, and closing out contracts.

The two key benefits identified in the PMI standards are:

B. Ensures that contract performance meets the terms of the legal agreement: This process involves both the buyer and seller. It ensures that the seller’s performance meets the project ' s requirements and that the buyer performs according to the terms of the legal contract (such as making timely payments). It involves reviewing and documenting how a seller is performing to ensure the desired results are achieved.

D. Assures that legal agreements guide contract closings: Control Procurements includes the administrative activities involved in finalizing a contract. It ensures that all deliverables have been accepted, all payments have been made, and all contractual obligations have been fulfilled before the contract is formally closed.

Analysis of other options:

A and E (Make-or-buy decisions and contract type selection): These are key benefits and activities of the Plan Procurement Management process. These decisions must be made during the planning phase, well before a contract is active.

C (Vendor selection): This is the primary focus of the Conduct Procurements process, which involves receiving seller responses, selecting a seller, and awarding a contract.

Per the PMI standards, Control Procurements is unique because it has a significant legal component, requiring the project team to be aware of the legal implications of the actions taken when managing the relationship with the seller.