Did you know Cybrary has FREE video training? Join more than 2,500,000 IT and cyber security professionals, students, career changers, and more, growing their careers on Cybrary.
This lesson discusses how to define scope. The define scope process creates a written project scope statement which can be used in future project decision making. Essentially, this process breaks down a product so you understand what the requirements are, saying what the project is and what it is not, both of these things are very important. [toggle_content title="Transcript"] The next area is defining scope. The define scope process creates a ran project scope statement which can be used in future project decision making. It includes one project consist of, what the project is involved to create the project. And what is expected when complete. So this is more for historical documentation. Key inputs are the scope management plan, the project's charter, the requirements documentation and organizational processes assets. So the scope management plan is the basis for how you are going to do these procedures. The project's charter consists of your high-level requirements. And your requirements documentation when it was just created, is the basis on what the scope management is going to be. And if your organization has any tools or templates on how to do this, that's the input right there. So the project manager will use expert judgement which you will see this a lot for majority of the processes. Product analysis, alternative generation, and facility workshops. So product analysis is breaking down that product, so you understand what the requirements are. Alternative generation is brain storming or using lateral thinking. And facilitated workshops- are groups where you come together to understand what the requirements are. So your output is the project scope statement. This document helps with buying towards the scope. It usually includes the product scope description, the acceptance criteria, deliverables...exclusion. So now when you are seeing what the project is, you're also seeing what the project is not, which is just as important. And constraints and assumptions. So constraint is anything that limits what that product is. So a constraint could be this needs to be done by Christmas. You have a constraint of a timeline or a constraint could be this has to be under one million dollars. So now, you have a budget that you have to be within. [/toggle_content]