Revisits scope, time, and cost baselines in the context of agile methodologies. Because agile includes several methodologies (like Scrum, Kanban, Extreme Programming, Feature-Driven Development) we will not concern ourselves with any specific agile methodology but will focus on the high-level principles that guide how scope, schedule, and cost considerations are addressed in the agile context.

1. What are your thoughts and impressions about how estimates and predictions are handled in agile vs. traditional approaches? Do you believe that one approach does a better job of handling these estimates? Why or why not?
2. As a project manager, how would you modify or replace the traditional approach when developing and reporting your project schedule and cost estimates?
3. How would you structure your report (cited in #2 above) to convey the most information in the least space and why might you want to strive to do this?