Project Scope Management Part 2
About the Lecture
The lecture Project Scope Management Part 2 by Whizlabs Software is from the course Project Management Professional - Training. It contains the following chapters:
- Create WBS
- Advantages of using WBS
- Decomposition
- Validate Scope
- Control Scope
Included Quiz Questions
The bottom most layer of WBS is called:
- Work packages.
- Control account
- Code of accounts.
- WBS dictionary.
The bottom 2nd last layer of WBS is called:
- Control account
- Work packages.
- Code of accounts.
- WBS dictionary.
Which of the following is not part of the Scope baseline:
- Statement of work
- WBS
- WBS Dictionary
- Project scope statement
As part of the scope management plan, the project management team:
- Decides the level of decomposition for WBS.
- Defines the scope
- Breaks down the work into smaller components
- Understands the requirements of the stakeholders
In a manufacturing project, the Project manager documents the following for each WBS component:
- Timeline to complete that component
- Primary & secondary responsible resource
- List of Activities to be done
- Code of accounts
Which of the following is not visible in WBS & WBS Dictionary?
- The dependency between activities.
- Component & subcomponents of project scope.
- Code of accounts
- Activity list for the work packages
While creating WBS, the project management team tries to limit work package duration within 2 weeks / 80 hours. This is an illustration of:
- Heuristics
- Organizational process assets
- Enterprise environmental factor
- Decomposition
The WBS for a software development project has been created & approved by all key stakeholders, including the sponsor and the customer. During the initial stage of execution, the customer raises a change request to add a new functionality to the product, which would increase cost. The customer claims that the functionality was explained as per of the vendor meetings and produces MOM for the meetings supporting the fact. Who should pay for the change?
- Customer, as the scope baseline has been approved by him/her.
- Sponsor, as the requirement was missed by the project team.
- Both, buyer & seller have to share the cost of change.
- The change can be accommodated by the sponsor to maintain a good relationship with the customer.
Which of the following technique can’t be used for “Collect Requirements”:
- Monte-carlo technique
- Brainstorming,
- NGT
- Focus groups
Based on a survey conducted by an external group, the industry-standard for IT cost expenditure of a medium scale Logistics Company is 6% to 8% of the total revenue generated by that company. Yours is a medium scale Logistics Company which spends 12% of the total revenue generated on IT. Based on this, you have been appointed as a project manager of a project to reduce IT cost to 8% of the total revenue generated. When your project is in planning stage, its found that the earlier survey was inaccurate and the industry-standard for IT cost expenditure of a medium scale Logistics Company is 10% of the total revenue generated by that company. What would be your next step?
- Rework the Project Charter
- Revise the scope baseline.
- Review the Scope Management Plan
- Follow integrated change control process.
Which is the primary output of the “define scope” process:
- Project Scope Statement
- Statement of work
- Scope management plan
- Scope baseline
Which is the primary benefit of using WBS?
- WBS helps prevent work ‘slipping through the cracks’
- It helps in estimation
- It helps manage scope by bifurcating the scope into work packages
- WBS is a good team building tool
Which of the following is an example of WBS:
- Project Breakdown Structure (PBS)
- Resource Breakdown Structure (RBS)
- Organizational Breakdown Structure (OBS)
- Bill of Materials (BOM)
‘Validate Scope’ uses the same tools & techniques as:
- Quality Control
- Control Scope
- Control Costs
- Control Schedule
A project manager has just been assigned to the project, while the project team is in the process of creating the Project Scope Statement. What should the project manager be most concerned with?
- Confirm that requirements have been collected from all stakeholders.
- QC parameters
- Understand scope of work.
- Review the charter
Halfway through the execution phase, a stakeholder from the senior management team has queried the project manager to explain how much work has been completed. Which document can be used by the project manager to explain this?
- WBS
- WBS dictionary
- Project Scope statement
- Project charter
Which of the tools & techniques is primarily used for “Control Scope”?
- Variance analysis
- Audits & inspections
- Integrated change control
- Validate scope
What’s the major benefit of using ‘Code of accounts’?
- It helps identify the WBS layer at which the WBS element would be found.
- It helps identifying the WBS elements in WBS dictionary
- It shows the dependencies between the work packages
- It is used for indexing
You have been working with a few common stakeholders within your organization. From your past experience, you know that a key stakeholder is prone to make many Change requests to project scope. What is the best option for you in this context?
- Ensure all the requirements are collected from this stakeholder & involve him in WBS sign-off process.
- Involve the concerned Stakeholder during ‘Create WBS’ process.
- Involve the concerned Stakeholder during ‘Define Scope process.
- Use Project Communication process to handle this stakeholder.
You are the project manager of a large project. You have outsourced a part of project scope as your organization lacks human resources with required skill set to complete this part of the project. Recently, you have observed that the vendor is going beyond the Scope of Project as originally defined. Which document should you ask the vendor to refer, in order to ensure that the project is delivered as per the defined scope?
- The Scope Statement, WBS, and any Approved Changes.
- Project Charter
- Contract statement of work
- Requirement documentation
Author of lecture Project Scope Management Part 2
Whizlabs Software
Customer reviews
5,0 of 5 stars
| 5 Stars |
|
5 |
| 4 Stars |
|
0 |
| 3 Stars |
|
0 |
| 2 Stars |
|
0 |
| 1 Star |
|
0 |
Excerpts from the accompanying material
... Project Scope. The work that must be done in order to deliver a product, service or result with specific features and functions is the project scope. Completion of project scope is measured against the plan. Product Scope. The features and the functions that are to be included in a product or service ...
... Requirement Management. Plan is the secondary output of this process. It´s a output of the Project management plan. The primary components of Requirement management plan include: How requirements would be gathered, tracked & included. Configuration management activities. Requirement prioritization process. Product metrics that will be used and rationale of using them. Traceability structure of requirements. 5.2 Collect Requirements. This is another planning process wherein ...
... Idea Mind Mapping/Affinity diagram: Group decision making: Uses unanimity, majority, plurality, dictatorship. Qs & surveys: Preferred over statistical analysis when quick turnaround is needed and your audience is broad. Observations: Similar to shadowing to discover what is going on. Prototypes: Supports concept of progressive elaboration. Requirement documentation: Requirement documentation can include business need, objectives, functional /non-functional requirements, training, support etc.. Requirements traceability matrix: Requirements traceability matrix links requirements to other documents ...
... is concerned with the generation of new ideas, with breaking out of the concept prisons of old ideas. This leads to changes in attitudes and approach; to looking in a different way at things, which have always been looked at in the same way. 5.4 Create WBS. The objective of this process is to create a scope baseline, which is a combination of the project scope statement that we created in the previous process, along with two outputs of this process: work breakdown structure and ...
... Sometimes we may have to wait until a deliverable or a sub component is clarified, in order to complete the WBS. This method is called a Rolling Wave Planning. There is a 100 % rule associated with the creation of WBS. Total of work at lower levels must be roll up to higher levels, with nothing left out. This means, all work to be done to complete the project deliverables should be identified as part of the WBS. The first level of WBS is most commonly same as the Project life cycle in SW projects. WBS is created with the help of the team members. It includes only work needed to create deliverables. ...
It i[s a oupovevt of the Project management plan Quantitative
... The same numbering system is used in a separate document, called the WBS dictionary, to describe those work components and document the details of those work components. It would contain information related to the WBS components, such as: who is that primary or secondary responsible for that work component; what are the activities ...
... The scope baseline, once it is approved by the sponsor, customer & other key stakeholders, is the basis for performance measurement of the project going forward during the monitoring and controlling the processes. 5.5 Validate Scope: This process is about obtaining the formal acceptance from stake holders ...
... be handled, if integrated change control process is followed and if master plan is amended to reflect the changes. Work Authorization: Process of sanctioning all project work. Work Authorization/Release: In cases where work is to be performed in segments due to technical or funding limitations, work authorization/release authorizes specified work to be performed during a specified period. Statement of Work (SOW): A narrative description of products or services to be supplied under ...
