tag:blogger.com,1999:blog-6087062302879778963.post5597245109525624644..comments2012-12-09T18:40:58.384-08:00Comments on Instructor in Training: Analyzing Scope CreepDV808http://www.blogger.com/profile/11423530987538881176noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6087062302879778963.post-29744481010878646632012-12-09T18:40:58.384-08:002012-12-09T18:40:58.384-08:00Ah Dawn, I am very familiar with similar scenarios...Ah Dawn, I am very familiar with similar scenarios, especially with clients whom I've done work with and who know me personally. In such a situation, the request made to expand the scope has often been made with the best intentions or very politely. And often, I've agreed to accommodate such a request out of courtesy and a need to prove to the client that we could "do the job, no matter what it took." From that experience, as you learned, I now make sure I have change documentation reflecting the acceptance of the inclusion, exclusion or expansion of the scope and require signatures. In a few instances even, when presented with the change documentation and viewing how the perceived "small changes" would subsequently inflate the project schedule, budget or resources, I've had clients who just as politely backed down, and some who indignantly expected me to complete the work without the change documentation because "I said I would make accommodations." In other words, little changes often suggested somehow seem to have very large impacts in the long run, and like you, I feel that without following progressive steps as illustrated by Greer, we as Project Managers or team members are often eating the costs in hours, budget and time to please the primary stakeholders without any accountability on their part in presenting the change in the first place.Anonymoushttps://www.blogger.com/profile/05706428388498201243noreply@blogger.com