PMBOK® Guide: Define Scope Inputs T&T Outputs
ฝัง
- เผยแพร่เมื่อ 13 ก.พ. 2019
- 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
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.
I wish I had discovered your program when I started my PMP journey earlier this year. Yours are the most helpful videos that I have found so far. You keep my attention, provide great explanations, and most importantly, help me *understand* as opposed to just reading information to me that I have already read in the PMBOK guide. You have helped bridge the majority of my information gaps, and I will be recommending you to anyone who is willing to listen. Keep up the great work!
Thanks Roger for kind words!! You can join forum.izenbridge.com to discuss your queries. It is available to all. All the best for your exam!!
Roger Cruz I totally agree with you
you are the ultimate definition of professional teacher.
Glad you liked it!! You can explore our PMP program here - www.izenbridge.com/pmp/online-course/
It is complete and comes with an end to end support.
Nobody defined scope as defined by you! Great work...
Happy to know that you liked video!! To know more about Saket training programs, please visit - www.izenbridge.com/landing/youtube/Saket-Bansal/
Presently seeing your PMP video understood your involvement and dedication to teaching others, earlier I avoided video you are teaching the old method means not using digital. Wish you your service will reach many of them.
Thanks a ton
Thanks! You’ve got a knack of explaining things well and with clarity
Thanks for your kind words!! To know more about complete PMP program, please visit - www.izenbridge.com/pmp/online-course/
It is complete and comes with an end to end support.
thank you from SUDAN
You are welcome!! Keep exploring iZenBridge TH-cam Channel.
Hello Mr. Bansal. The way you teach is very helpful and understandable. thanks a lot. i was wondering if you can make a short video on collect requirements.
Hi Anu, we have videos on all PMP topics and packaged in the PMP program. It is a complete program and comes with an end to end support: www.izenbridge.com/pmp/online-course/
Very good
Thanks Engr Raliha for your kind words!! Keep exploring iZenBridge TH-cam Channel.
all requirement in documentation goes to in RTM ?
No, RTM is a table which links Business Case, stakeholders requirement, solution requirements and deliverables. For more details, please refer following video - www.izenbridge.com/blog/requirement-traceability-matrix-what-is-rtm-and-why-do-we-need-it/
Should be all requirements valid and genuine in requirement documentation ?
Requirement Documentation is a result of engaging stakeholders to understand their needs. All requirements may not be part of scope baseline. Requirements which are approved goes in scope baseline.
This guy is good but only issue is with procurement knowledge area, rest of the content is good.
Thank you!! Adrian for your valuable feedback. You can explore our new video on "Procurement Management Comparing Different Contract Types"-
th-cam.com/video/wiJNHcQMS2c/w-d-xo.html