Change Management
Change Management
Project Scope Management refers to the set of processes that ensure a project’s
scope is accurately defined and mapped. Scope Management techniques enable
project managers and supervisors to allocate just the right amount of work
necessary to successfully complete a project—concerned primarily with controlling
what is and what is not part of the project’s scope.
Project lifecycle:
Initiation Phase
During the first of these phases, the initiation phase, the project objective or need is
identified; this can be a business problem or opportunity. An appropriate response to the
need is documented in a business case with recommended solution options. A feasibility
study is conducted to investigate whether each option addresses the project objective and
a final recommended solution is determined. Issues of feasibility (“can we do the
project?”) and justification (“should we do the project?”) are addressed. Once the
recommended solution is approved, a project is initiated to deliver the approved
solution and a project manager is appointed.
Planning Phase
The next phase, the planning phase, is where the project solution is further developed in
as much detail as possible and the steps necessary to meet the project’s objective are
planned. In this step, the team identifies all of the work to be done. The project’s tasks
and resource requirements are identified, along with the strategy for producing them.
This is also referred to as “scope management.” A project plan is created outlining the
activities, tasks, dependencies, and timeframes. The project manager coordinates the
preparation of a project budget by providing cost estimates for the labor, equipment, and
materials costs. The budget is used to monitor and control cost expenditures during
project implementation.
Closing Phase
During the final closure, or completion phase, the emphasis is on releasing the final
deliverables to the customer, handing over project documentation to the business,
terminating supplier contracts, releasing project resources, and communicating the
closure of the project to all stakeholders. The last remaining step is to conduct lessons-
learned studies to examine what went well and what didn’t. Through this type of analysis,
the wisdom of experience is transferred back to the project organization, which will help
future project teams.
Managing by deliverables:
Management by deliverables is a project management principle that calls for all project planning and monitoring
to be achieved through production of visible work products. The principle is applied on a project by judging
progress by what is produced rather than by someone's subjective opinion of project status. This notion is the
core tenant behind the Earned Value Management Discipline which places a baseline value on
each deliverable at project commencement and credits the project with that value when the deliverable is
completed. Refer Earned Value Management metric: Project Percent Complete
Scope processes:
Collect Requirements:
This is the first process group in scope management. It is the process of defining
and documenting stakeholders need to meet the project activities. The document
for collecting requirements is developed in the project planning phase.
Define Scope:
This is the process of developing a detailed description of the Project and product.
So, while Collecting requirement list, all the different requirements of the Project
and the resulting product or service are defined.
Create WBS:
Creating work breakdown structure is done using a technique called
decomposition. It is basically the process of subdividing project deliverables and
project work into smaller and more manageable components.
Verify Scope:
This is the process which is a part of project monitoring and control process group.
This process includes reviewing deliverables with the customer or sponsor to
ensure that they are completed satisfactorily and obtaining formal a cceptance of
deliverables by the customer or sponsor.
Control Scope:
Control Scope is the last process group of project scope management. It is again a
part of project monitoring and control process group. Control scope is the process
of monitoring the status of the project and Product scope and managing changes
to the scope baseline. This process ensures that all requested changes and
recommended corrective or preventive actions are processed through the
integrated change control process.
1. Plan Costs
2. Estimate Costs
3. Determine Budget
4. Control Costs
1. Units of measure: This part of management plan will cover all the units used for
measurement of resource quantities. These units be like length of wall will be measured
in feet, door thickness will be in inches, steel weight will be in kilograms, Height will
be expressed in meters, paint required will be quantified in terms of liters, volume of
concrete will be in cubic meters, Tiles will be measured in meters, and etc.….
2. Level of Precision: This will define how deeply activity cost estimates will be
rounded up or down. And this depth will be defined based on activities scope and
project magnitude. For Example: If amount of activity is 1025$ then it will be rounded
down to 1000$. And if activity cost is 975$ then it will be rounded up to 1000$.
3. Level of Accuracy: Accuracy will define the acceptable range in terms of
percentage. If a cost occurs against specific activity within defined range then it will
not be responded. If cost goes above that range then activity will be responded. For
Example: An activity cost is 100$ and accuracy level is +/- 5%. If cost during execution
occurs 104$ then it will be considered.
4. Organizational Procedural Links: Organizational procedural links will provide
the framework for cost management plan. This will define which resource will be
responsible for which specific part of work breakdown structure(WBS).
5. Control Threshold: This is variance thresholds for monitoring cost performance
against baseline plan. Actually, this defines the acceptable variation before some
action needs to be taken.
6. Reporting Formats: This part of cost management defines the formats of project
reporting and frequency of reporting. Either reports will be generated after every
week, month year or any other specified frequency.
7. Process Description: This part of cost management plan describes the various
processes of project cost management. A complete detail of each process will be
covered here.
Cost of Quality (COQ) includes money spent during the project to avoid
failures and money spent during and after the project due to failures. During
cost estimation, assumptions about the COQ can be included in the project
cost estimate.
What is 'Cost Control'
Cost control is the practice of identifying and reducing business expenses to increase
profits, and it starts with the budgeting process. A business owner compares actual
results to the budget expectations, and if actual costs are higher than planned,
management takes action. As an example, a company can obtain bids from other vendors
that provide the same product or service, which can lower costs.
What is Quality management?
Project quality management is all of the processes and activities needed
to determine and achieve project quality.
I like this simple definition of quality because it places the focus where it
should be, on the customer. This basic definition also implies that the
requirements of the project have been met since the requirements sho uld
reflect the customer's needs if collected properly.
1. Cause-and-effect diagram
Diagrams that define the inputs to a process or product to identify the potential causes of
defects are known as Cause and effect diagrams
This diagram is also referred to as Fish-bone analysis diagram. They are used to determine
what may have caused a defect. They are very helpful when we need to analyze the root
cause of a problem.
2. Control Charts
Control Charts are a way of visualizing how processes are doing overtime. Control Charts
measure the results of processes over time and display the result in graph form to show
whether the process variance is in control or out of control.
4. Histogram
A bar chart showing a distribution of variables over time, is called a Histogram. (Std. Def.)
Histograms give us a fair idea of how our data breaks down. It shows the distribution of data
over various streams ranging from resource allocation to budget distribution.
5. Pareto Chart
A bar chart ordered by the frequency of occurrence, that shows how many results were
generate by each identified. (Std. Def.)
Pareto charts help us to figure out which problems need our attention right away. They’re
based on the idea that a large number of problems are caused by a small number of causes
which is based on the Pareto Principle.
7. Scatter Diagrams
A scatter diagram, or scatter graph is a graphical representation of quantitative analysis on
mathematical statistics of two variables, using Cartesian coordinates.
Scatter diagrams show how two different types of data could relate to each other and show
the progress of work. Scatter diagrams use two variables, one called an ‘independent
variable’, which is an input and the other called the ‘dependent variable’, which is an output.