It’s an effort to create a unique product or service.People are involved in a project team who don’t work together as it is not a part of routine work. Project Management involves many elements in it, i.e. application of knowledge, needed tools, human resources,material resources & technological resources etc.
Project Management-Scope Management
The “Collect Requirement”. At this stage the project has started. Focus is maintained at collecting the details of the project based on the stakeholder. The inputs to be used would be the Project Charter and the Stakeholder Register.
The expected output of the Collect Requirement would be :
1) Requirement Management Plan
2) Requirement Document
3) Requirement Traceability Matrix
The Define Scope is the process of developing a detailed description of the project and product. The preparation of a detailed project scope statement is critical to project success and builds upon the major deliverable assumptions, constraints that are documented during project initiation.
Document the explicit project exclusions and inclusions that can assist in managing stakeholder expectation
For the documented requirement document the project deliverable and work required to create those deliverable
The inputs would be :
1) Project Charter
2) System Requirements
3) Organizational Process Assets –
– Policies, Procedures, and Templates for a Project scope statement
– Project files from a previous project
– Lessons Learnt from previous phase or project
The Create WBS process is the most important process in the Scope Management knowledge area because it’s where you figure out all the work that you’re going to do.
It’s where you create the Work Breakdown Structure (WBS) which is the main Scope Management output.
Organizational Process Assets
Creating WBS is all about taking deliverables and coming up with work packages that will create them. When you do that, its called decomposition and it’s the main tool you use to create WBS.
Decomposition is the most important tool in creating the WBS, but its not the only one. You can also use templates, the other Create WBS tool, to help you with the WBS. The most common way to do this is to use a WBS from a similar project you’ve done in the past as a starting point for the current one.
WBS is either done by phase or by deleverables.
WBS shows you the name of each work package. That’s not enough to do the work. You and your team need to know more about the work that has to be done. That’s where WBS Dictionary comes in handy. It brings along all the details you need to do the project work. WBS Dictionary is an important output of the Create WBS Process.
The WBS Dictionary contains all the details of every work package. It’s a separate output of Create WBS Process.
The Create WBS Process has three major outputs: the Work Breakdown Structure, the WBS Dictionary and the Scope Baseline.
When you create WBS, you usually figure out that there are pieces of scope that you missed, and you may realize that you need to change the project documents.
As the project goes on you will want to compare how you are doing to what you planned for. So the Scope Baseline is there to compare against. Its made up of the Scope Statement, the WBS and the WBS Dictionary. When work gets added to the scope through change control, you need to change the baseline to include the new work packages for that work.
When there is a change you need to take a new snapshot. Whenever a change is approved through change control, the baseline needs to be updated. Approved changes are changes to the scope management plan also, so its important that you re-baseline your project when they are approved. That way you will be comparing your performance to the most updated plan.
• Subdivided project deliverables and project work into smaller more manageable components.
• Hierarchical decompose Project work to increasing details with each decreasing level
• The lowest level WBS component is the work package
• Work Package can be scheduled, cost estimated, monitored and controlled
• Work (in WBS) refers to work product or deliverables that are the result of effort and not the effort itself
Scope Verification Process
When the team is done, what happens? You need to perform a vital step. You need to gather all stakeholders together and have them ensure that all the work has been completed as per the expectations. That is called Scope Verification Process.
Scope Control Process
There’s no way to predict every possible piece of work that you and your team are going to do in the project. Somewhere along the way, you or someone else will realize that a change needs to happen, and that change will affect the scope baseline. That’s why you need the Scope Control process. It’s how you make sure that you make only those changes to the scope that you need to make and that everyone is clear on what the consequences of those changes are.