Subtitles of the Movie

This movie will focus on the workbook questions found within your work files. Specifically we will review questions relating to the Scope Definition Process, which contains a total of nine questions. The firs question asks for the purpose of the process and that is to develop a Detailed Project Scope Statement to base future project decisions on. Did you notice that the second process of the Scope Knowledge Area produces a Project Scope Statement just as the second process within the Integration Knowledge Area produced the Preliminary Project Scope Statement. Just a minor tip to help you remember the processes. The Project Scope Statement is a critical piece of the project overall and we'll review this a bit more in the coming questions. Question two through four review the inputs, the tools and techniques and the outputs. The major output is the Project Scope Statement and then we have the outputs that manage the changes to the scope, which also produce updates. Question five states the Detailed Project Scope Statement is a great resource for the project team. How does it assist the project team? I mentioned earlier how critical the Project Scope Statement is. During the Scope Definition Process movies, we covered four ways that it assists the project team and these included that it provides a common understanding among stakeholders, it enables detailed planning, guides the work during project execution and it's a baseline to measure requested changes. Moving on to question six, it says name ten items included in a Project Scope Statement. There are sixteen items you could have chosen from, so let's go through the list. The first is Project Objectives, which includes measurable success criteria of the project; Product Scope Description, which describes the characteristics of the product, service or result and is progressively elaborated; Project Requirements which are conditions or capabilities that must be met or possessed by the deliverables of the project to satisfy the formal documents; Project Boundaries, which detail what is and isn't included in the project; Project Deliverables, which are either outputs that make up the product or service of the project or are ancillary results. Then there's Product Acceptance Criteria, which defines the process and criteria for accepting the completed product; Project Constraints, which specify existing limitations on scope; Project Assumptions, which are assumptions associated with the project scope and what the impact is if the assumptions are wrong; the Initial Project Organization, which lists the members of the project team and identifies the stakeholders and also documents the organization of the project; the Initial Defined Risk, which include known risks, Schedule Milestone, which are milestone dates that are provided by the customer or the performing organization; Fund Limitations, which are limitations placed on project funding; Cost Estimates, which are factors in the project's expected overall cost preceded by modifiers for an indication of accuracy; Project Configuration Management Requirements, which describe the level of Configuration Management and Change Control to be implemented; Project Specifications, which identifies the specification documents that the project must comply with and lastly, it has Approval Requirements, which identify approval requirements that can be applied to project objectives, deliverables, and also documents of project work. Notice how this list is nearly a direct match of the Preliminary Project Scope Statement with a few modifications, including Cost Estimates as opposed to Wide Estimates. Question seven says what is included in Product Analysis? And there are six things that are included, which are: Product Breakdown, Systems Analysis, Systems Engineering, Value Engineering, Value Analysis and Functional Analysis. And moving right into question eight, which asks what are the two types of Alternative Identification? And these are brainstorming and lateral thinking. And finally question nine says what does Stakeholder Analysis do and how is it useful? And Stakeholder Analysis identifies the influences and interests of the identified stakeholders and it also documents their needs, wants and expectations. Then it selects and prioritizes and also quantifies those needs, wants and expectations. And that was our final question for review in this section of the workbook, which wraps up this movie on Scope Definition.