Which document contains a deliverable oriented grouping of the work involved in a project that defines the total scope of the project quizlet?
|
-Difficult to create a good WBS Show -Project manager and team must decide as a group how to organize the work and how many levels to include in the WBS -Better to focus on getting the top levels of the WBS done well to avoid being distracted by too much detail -People confuse tasks on a WBS with specifications or think it must reflect a sequential list of steps -Focus on what work needs to be delivered, not when or exactly how it will be done 1. Planning scope management involves determining how the project's scope and requirements will be managed. The project team works with appropriate stakeholders to create a scope management plan and requirements management plan. 2. Collecting requirements involves defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them. The project team creates stakeholder requirements documentation, a requirements management plan, and a requirements traceability matrix as outputs of the requirements collection process. 3. Defining scope involves reviewing the project charter, requirements documents, and organizational process assets to create a scope statement, adding more information as requirements are developed and change requests are approved. The main outputs of scope definition are the project scope statement and updates to project documents. 4. Creating the WBS involves subdividing the major project deliverables into smaller, more manageable components. The main outputs include a work breakdown structure, a WBS dictionary, a scope baseline, and updates to project documents. 5. Verifying scope involves formalizing acceptance of the project deliverables. Key project stakeholders, such as the customer and sponsor for the project, inspect and then formally accept the deliverables during this process. If the deliverables are not acceptable, the customer or sponsor usually requests changes. The main outputs of this process, therefore, are accepted deliverables, change requests, work performance information, and updates to project documents. 6. Controlling scope involves controlling changes to project scope throughout the life of the project—a challenge on many information technology projects. Scope changes often influence the team's ability to meet project time and cost goals, so project managers must carefully weigh the costs and benefits of scope changes. The main outputs of this process are work performance information, change requests, and updates to the project management plan, project documents, and organizational process assets. Which statement best describes scope? -each level of work that is outlined in a work breakdown structure -end product created as part of a project that is delivered to the client -tasks that are decomposed into smaller tasks in a work breakdown structure -work involved in creating the products and the processes used to create them Which document should list and describe all of the deliverables required for the project quizlet?Project scope statements should include, at a minimum, a product scope description and detailed information on all project deliverables. The scope of a project should be clear and specific from the start.
Which task is at the lowest level of the WBS?The lowest level of the WBS is called a work package. It is a discrete deliverable.
When the project scope or requirements are changed without review and approval this is called?Scope creep is one of the most common project management risks. Generally, scope creep occurs when new project requirements are added by project clients or other stakeholders after the project execution has started. Often these changes are not properly reviewed.
What is the first process in project scope management?1. Planning scope management. In the first process in project scope management, you create a scope plan document that you can refer to in the later stages. The document mainly helps in defining, managing, validating, and controlling the project's scope.
|
