PMI Updated CAPM Exam Questions and Answers by hayden

According to the PMBOK® Guide and the Agile Practice Guide, On-demand scheduling is an emerging practice used in adaptive environments, particularly those utilizing Kanban systems.

On-Demand Scheduling: This approach does not rely on a pre-defined schedule or " sprints " of a fixed duration. Instead, it pulls work from a backlog or a queue of outstanding tasks as resources become available. This is often based on Theory of Constraints and pull-based scheduling concepts to limit Work in Progress (WIP). The goal is to balance the demand for work against the team ' s delivery capacity.

Context: This is highly common in maintenance or operational environments where work is not easily grouped into iterations but must be addressed as it arises (e.g., bug fixes, support tickets, or continuous flow manufacturing).

Analysis of other options:

Iterative (Option A): Iterative scheduling (like Scrum) involves time-boxed periods (sprints) where a set amount of work is committed to and performed. It is " push-to-iteration " rather than a continuous " pull-as-available. "

Interactive (Option C): This is not a recognized PMI scheduling term. Interaction refers to communication methods or stakeholder engagement styles.

Quality (Option D): Quality is a project constraint and a knowledge area, but it is not a scheduling methodology.

Per PMI standards, on-demand scheduling is particularly effective when the work is highly variable and the team seeks to optimize the flow of value by reducing lead times and eliminating idle time.

According to the Agile Practice Guide and the Scrum Guide, Scrum is defined by three specific categories: Roles, Artifacts, and Events (also called Ceremonies).

Defining " Events " : The team member correctly pointed out that the " events " are missing. In Scrum, there are five formal events for inspection and adaptation: The Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.

Daily Scrum (Option A): A 15-minute event for the Developers to synchronize activities and create a plan for the next 24 hours.

Sprint Retrospective (Option C): An event held at the end of the sprint to plan ways to increase quality and effectiveness by inspecting how the last Sprint went with regards to people, relationships, processes, and tools.

Coaching the Team: The Scrum Master’s role is to ensure the team understands the framework. By identifying these missing events, the team completes the " heartbeat " of the Scrum process, allowing for the empirical process control of transparency, inspection, and adaptation.

Analysis of other options:

Option B (Increments): This is an Artifact, not an event. The Increment is a concrete stepping stone toward the Product Goal.

Option D (Sprint backlog): This is an Artifact, not an event. It is the set of Product Backlog items selected for the Sprint, plus a plan for delivering them.

Option E (Product backlog): This is an Artifact, not an event. It is an emergent, ordered list of what is needed to improve the product.

Per PMI standards, when a team is organizing their approach and identifies that events are missing, they must select from the timeboxed activities defined in the framework, such as the Daily Scrum and the Sprint Retrospective.

According to the PMBOK® Guide (6th Edition), because each project is unique, the project manager and the project team must tailor the way Project Risk Management processes are applied. Tailoring ensures that the level of risk management is commensurate with the importance of the project and the magnitude of the risks involved.

Project Complexity is a fundamental tailoring consideration for Risk Management. High-complexity projects—characterized by innovative technology, numerous shared dependencies, or difficult external environments—require a more robust, formal, and frequent risk management approach. Conversely, a simple, low-complexity project might use a simplified risk register and less frequent reviews.

Other Tailoring Considerations for Risk Management include:

Project Size: The project ' s budget, duration, or team size.

Project Importance: The strategic importance of the project to the organization.

Life Cycle Approach: Whether the project uses a predictive, adaptive, or hybrid methodology.

Analysis of Distractors:

B (Procurement criteria): While procurement involves risks, " criteria " refers to the selection process for vendors. This is a specific activity within Project Procurement Management, not a high-level tailoring consideration for the overall Risk Management framework.

C (Communication technology): This is a tailoring consideration for Project Communications Management. It refers to the tools available to transfer information among stakeholders.

D (Knowledge management): This is a tailoring consideration for Project Integration Management. it focuses on how the organization creates, shares, and utilizes knowledge to achieve project objectives.

According to the PMBOK® Guide (Project Procurement Management), the Conduct Procurements process is the process of obtaining seller responses, selecting a seller, and awarding a contract.

Seller Proposals are a critical input to this process. These are prepared by sellers in response to a procurement document package (like an RFP or RFQ) and form the basic information that will be used by an evaluation body to select one or more successful bidders (sellers). The proposal constitutes a formal response to the buyer ' s requirements.

Other key inputs to this process include:

Project Management Plan (specifically the Procurement Management Plan).

Procurement Documentation (Bid documents, Statement of Work).

Source Selection Criteria.

Make-or-Buy Decisions.

Analysis of Distractors:

A. Independent estimates: This is a tool and technique (specifically under Data Analysis) used during the Conduct Procurements process. The organization may prepare its own " benchmarks " to check the reasonableness of the seller proposals.

B. Selected sellers: This is a primary output of the Conduct Procurements process. Once the proposals are evaluated, the sellers are selected and contracts are awarded.

D. Resource calendars: This is an output of the Conduct Procurements process. Once a seller is contracted, the schedule and availability of their resources are documented in resource calendars to be used in the Develop Schedule process.