This exercise contrasts the core philosophies of predictive (plan-driven) and agile (change-driven) project management.

• Predictive: This approach, often called "waterfall," is built on detailed upfront planning. Requirements are fully defined at the start. Because the plan is paramount, Changes are undesirable and thus constrained. Risk and Cost are managed via a detailed initial plan. Key Stakeholders are typically involved at major sign-off points or milestones.
• Agile: This iterative approach is designed to embrace change. Requirements are expected to evolve and are elaborated frequently in small batches. Changes are welcomed and incorporated in real-time during development sprints or iterations. Key Stakeholders (like a product owner) are continuously involved to provide constant feedback. Risk and Cost are managed iteratively as new information and requirements emerge.

MIT OpenCourseWare. (2016). 16.852J / ESD.36J System and Project Management. Fall 2016. Lecture 3: Project Life Cycles & Processes.

Reference: This lecture material explicitly contrasts predictive (e.g., Waterfall) and adaptive (Agile) lifecycles. It notes that predictive models fix requirements early, while adaptive models allow requirements to be elaborated throughout the project. It also describes stakeholder involvement as periodic in predictive models versus continuous in adaptive models.

Tripp, J., & Armstrong, D. J. (2018). "Agile Methodology: A Review of the Literature and Project Management Framework." Journal of Information Systems Education, 29(3), 147-156.

Reference: Page 148 discusses how Agile methodologies, unlike traditional predictive models, "welcome changing requirements, even late in development." This supports matching "incorporated in real-time" with Agile changes and "constrained" with Predictive changes.

Serrador, P., & Pinto, J. K. (2015). "Does Agile work?—A quantitative analysis of agile project success." International Journal of Project Management, 33(5), 1040-1051. https://doi.org/10.1016/j.ijproman.2015.01.006

Reference: Page 1041, in its comparison of "Traditional" (Predictive) and "Agile" methods, highlights that stakeholder engagement in traditional models is "Limited, at start and end," whereas in Agile it is "Constant." This supports the placement of "involved at specific milestones" (Predictive) and "continuously involved" (Agile).

Project Management Institute (PMI). (2017). Agile Practice Guide.

Reference: Section 3.1 (Page 18-19), "Characteristics of Project Life Cycles," contrasts predictive and agile approaches. It states predictive life cycles involve "up-front planning" for scope, time, and cost, supporting the "controlled by detailed planning" match. In contrast, it describes agile life cycles as having requirements "elaborated in iterations," supporting the "elaborated frequently" match.