Two-Minute Drill

---

Selecting Projects

q	Projects are selected based on many different conditions: opportunity, need, customer demands, and so on. The project purpose and business need must be identified so the project scope can be created to support this purpose.
q	When there are multiple projects up for approval, management may use one of two methods to choose between them: benefit measurement methods (which are comparative models), or, for large complex projects, constrained optimization methods (which focus on complex mathematical equations).

Authorizing Projects

q	Once a project is selected, it moves through the initiation processes. One of the major outputs of initiation is the project charter; it's major because it provides authority for the project. Specifically, the project charter provides authority, names the project title and the project manager. The charter defines the business needs the project product will satisfy.
q	The charter should be written in open terms and dialogue so it does not have to be re-written because it is too narrow. The charter should be written and signed by senior management in order to gain access to the necessary project resources.
q	A project does not exist until a charter has been created.

Project Scopes

q	Projects move through product-orientated processes to create the project's product. These processes are typically marked by phases unique to the project work. For example, foundation, framing, roofing, finishing, and so on. Project management processes are the activities universal to all projects.
q	There are two scopes: the project scope and the product scope. The project scope is the work to be completed to create the product. The product scope describes the features of the product and its characteristics.
q	Scope management is the process that follows the scope management plan. It ensures that the scope includes all of the required work-and only the required work-to complete the project. It documents how changes may enter into the scope, and how frequently the scope is expected to change.
q	At the end of the project or project phase-or even at major deliverables within the project-scope verification happens. Scope verification is the process of formally accepting the project work as defined in the product documentation, the project scope, or in the contractual agreement, if relevant. Formal acceptance requires signoff for acceptance of the product.

---