A software development team is pulling work from its backlog to be performed immediately as they become available. What emerging practice for project scheduling is the team using?
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.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit