Don't start the building without the blueprint

defining the scope of a project

NASA (United States National Aeronautics and Space Administration) failed to clearly define the Space Station Program project's scope before requirements were written, resulting in divergent activities and cost overruns. This is a common mistake that occurs in projects. This article suggests that spending more money up-front in the scoping process will be more than offset by savings resulting from performance improvements. Requirement authors needs to clearly understand a project's scope before they write requirements.
registered user content locked

Log in or join PMI to gain access

or Account Registration



Related Content


Publishing or acceptance of an advertisement is neither a guarantee nor endorsement of the advertiser's product or service. View advertising policy.