ABSTRACT
Every project, regardless of its constraints and/or justification criteria, requires a process and document that captures, documents and articulates what the project is all about-in other words, the project's initial boundaries. In project terms, you might know this focus as the project proposal, the user requirements, the grant application, the letter of engagement, the business requirement, the request for tender, the customer brief, the business case, the project proposal, the commercial quotation, the scope, the memorandum of understanding, the scope of work, the specification and so on. No doubt, while standard operating procedures, position descriptions, key performance indicators, operational plans, action plans, meeting minutes and performance reviews might provide some general sense of direction, they are not a direct equivalent of a scope management plan, which has as its focus the protocols, behaviours and approvals required to manage scope.
