Scope and Requirements
"Pool all the statements, conversations, and modifications into one shared scope and requirements document that everyone on the project team can buy into. If a requirement is not recorded in this document, it is not within the scope of the project. This thread acts as a pressure release valve that needs to be managed to add or remove requirements, with appropriate buy-in, to meet the initiative delivery dates."
"The requirements must have a formal approval by the Executive Sponsor to establish a scope baseline. Any requirements that are added, changed, or deleted should be handled by the project change management process."
The above is an excerpt from a book written by Sanjiv Purba and
Joseph Zucchero, published by McGraw-Hill/Osborne, 2100 Powell Street,
10th Floor, Emeryville, California 94608 U.S.A. Sanjiv has over 20
years of experience managing large projects and many years engaged in
rescuing ailing projects.