PMBOK® Guide: Define Scope Inputs T&T Outputs скачать в хорошем качестве

PMBOK® Guide: Define Scope Inputs T&T Outputs

This video starts with the Inputs, Tools & Techniques and outputs of the process Define Scope. Define Scope is a process which gives scope to a project. This scope is primarily developed by the project management team, lead by the requirement gathering team. Inputs of this process are Project Charter, Project management plan, Project documents, Enterprise environmental Factors (EEF), and Organizational Process Assets (OPA). How do we develop the scope statement? We need to know project charter and requirement documents for discovering various requirements and details to help in creating the scope. Project Charter contains high-level requirement and also contains the approach details for the scope. The scope statement depends on the environment of your organization. It is different in case you are working in a very formal and process oriented environment. Organizational process assets - You need to look into lessons learned from previous projects to create the templates for scope statement. The scope management plan is a part of the Project Management Plan. Project documents include • Assumption log • Requirements documentation • Risk register Assumption logs are prepared, maintained throughout the logs, whenever you are working with stakeholders, whenever you are working with risk, whenever you are doing estimation for the project; you keep updating the assumptions in the Assumption Logs. Risk Register contains various risky things linked with the requirement and the way you should be implementing the solution. A requirement document which was created during the “Collect requirement” process is the primary source which has lots of information. Once you have this, you need to work on the approach. Scope Management Plan tells you the approach of developing the scope statement. Granularities, type of language, type of diagram, type of description, are to be used while preparing the scope statement so that everyone in the team understands the scope clearly. Tools and Techniques of Define Scope are Expert Judgment, Data analysis (Alternatives analysis), Decision making (Multicriteria decision analysis), Interpersonal and team skills, and Product analysis. An example of an interpersonal and team skills technique is facilitation. Facilitation is used in workshops and working sessions with key stakeholders who have a variety of expectations and are subject matter experts. Outputs of this process are Project scope statement and Project documents updates. Some of the requirement you receive may get rejected as they are no more feasible. So you update the requirement document and traceability matrix. Any requirement, captured in the requirement document is no guarantee that it will be taken up. Requirement Traceability Matrix provides the status of requirements (approved or rejected). Stakeholder register is also updated based on the final list of requirements. Project Scope statement should have details of deliverables and scope. It contains elaborated scope, acceptance criteria, assumptions related to the scope, section providing information which all areas need further exploration. Depending on the type of project and type of organization you are working in, you need to put relevant information in your project scope statement. Refer to the following link to register with us https://www.izenbridge.com/pmp/online... The Project Management Professional (PMP), PMBOK, The Agile Certified Practitioner (PMI-ACP), and The Professional in Business Analysis (PMI-PBA) is a registered mark of the Project Management Institute, Inc. PMBOK is a registered mark of the Project Management Institute, Inc. Materials in this video are based on the text, A Guide to the Project Management Body of Knowledge, (PMBOK® Guide) – Sixth Edition, Project Management Institute Inc., 2017. The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc.