According to the PMBOK® Guide, specifically in the section regarding Trends and Emerging Practices in Project Schedule Management, the approach to scheduling changes significantly when moving from a predictive (waterfall) environment to an adaptive (agile) environment.
Tight Integration of Processes: In adaptive environments, the traditional scheduling processes—Define Activities, Sequence Activities, Estimate Activity Durations, and Develop Schedule—are so tightly linked that they are often performed simultaneously or as a single, continuous process. This is because the team works on small batches of work (increments) rather than planning the entire project in one go.
Rapid Iteration: Instead of a linear flow where one process must end before the next begins, adaptive teams refine their understanding of the work in real-time. As soon as a requirement is defined, it is estimated and placed into the schedule (sprint/iteration) almost immediately.
Collaboration: This " single process " view is facilitated by high levels of team collaboration and the use of tools like backlogs and Kanban boards, where work items move from definition to execution rapidly.
Why other options are incorrect:
Option B: While it is true that schedules remain flexible in adaptive environments, this is a general characteristic of the environment, not a " condition " or technical process description provided by the PMBOK Guide for how scheduling is performed.
Option C: This describes specific types of scheduling (Iterative and Pull-based/Kanban). While these are used in adaptive environments, they are listed as separate techniques in the Guide. Option A is the more fundamental description of how the standard scheduling processes are treated in such environments.
Option D: This is a vague statement about " adapting techniques. " While project management always involves tailoring, it does not specifically address the scheduling mechanics of an adaptive environment as clearly as the integration of processes mentioned in Option A.
