Project MGT and Metrics

The Management Spectrum:
In software engineering, the management spectrum describes the management of a software

project. The management of a software project starts from requirement analysis and finishes
based on the nature of the product, it may or may not end because almost all software
products faces changes and requires support. It is about turning the project from plan to
reality.
The management spectrum focuses on the four P’s; people, product, process and project.
Here, the manager of the project has to control all these P’s to have a smooth flow in the
progress of the project and to reach the goal.
The Management Spectrum | 4 P’s in Software Project Planning

For properly building a product, there’s a very important concept that we all should know
in software project planning while developing a product. There are 4 critical components
in software project planning which are known as the 4P’s namely:
• Product
• Process
• People
• Project
These components play a very important role in your project that can help your team
meet its goals and objective. Now, Let’s dive into each of them a little in detail to get a
better understanding:
• People
The most important component of a product and its successful
implementation is human resources. In building a proper product, a well-
managed team with clear-cut roles defined for each person/team will lead to
the success of the product. We need to have a good team in order to save our
time, cost, and effort. Some assigned roles in software project planning
are project manager, team leaders, stakeholders, analysts, and other IT
professionals. Managing people successfully is a tricky process which a good
project manager can do.
• Product
As the name inferred, this is the deliverable or the result of the project. The
project manager should clearly define the product scope to ensure a successful
result, control the team members, as well technical hurdles that he or she may
encounter during the building of a product. The product can consist of both
tangible or intangible such as shifting the company to a new place or getting a
new software in a company.
• Process
In every planning, a clearly defined process is the key to the success of any
product. It regulates how the team will go about its development in the
respective time period. The Process has several steps involved like,
documentation phase, implementation phase, deployment phase, and
interaction phase.
• Project
The last and final P in software project planning is Project. It can also be
considered as a blueprint of process. In this phase, the project manager plays
a critical role. They are responsible to guide the team members to achieve the
project’s target and objectives, helping & assisting them with issues, checking
on cost and budget, and making sure that the project stays on track with the
given deadlines.
W5HH Principle
Barry Boehm gave a philosophy that prepares easy and manageable designs or outlines
for software projects. He also gave a technique to discuss objectives, management,
duties, and technical approach of the project and its necessary resources. Then he
named it the W5HH principle when few questions resulted in project properties,
definition, and resultant plan to make the project successful. Those questions are :
The W5HH principle in software management exists to help project managers guide
objectives, timelines, responsibilities, management styles, and resources. In this lesson,
we’ll explore each part.
W5HH questions :
Why the system is going to be developed?

For the purpose of software work, all stakeholders must assess the validity of the system
product/project. Here Barry questions that whether the project’s purpose will justify the
cost, time spent on it by people?
What is activities are needed to be done in this?
In this Barry questions what task is needed to be done for a project currently.
When is this done?

Project Scheduling is done by the team after recognizing when project tasks will be started
and when they enter into the final stage to reach the goal.
Who are the reasons for these activities in this project?

Every member who is part of the software team is responsible for this. And their roles are
defined.
Where are these authoritatively located?

Not only do software practitioners have roles in this but also users, customers, stakeholders
also have roles and responsibilities organizationally.
How is the job technically and managerially finished?

All technical strategies, management rules of the project are defined after knowing the
scope of the project which is being built.
How much part of each resource is required?

This is known by software developers after the estimation of each resource as per the needs
of customers/users.
This W5HH principle of Boehm is appropriate irrespective of the scale or difficulty of

software projects being developed. These questions help in planning the outline of the
project for the software team.
The W5HH principle outlines a series of questions that can help project managers more
efficiently manage software projects. Each letter in W5HH stands for a question in the series
of questions to help a project manager lead. (Notice there are five ”W” questions and two
”H” questions).
Why is the system being This focuses a team on the business reasons for
Why?
developed? developing the software.
This is the guiding principle in determining the tasks

What? What will be done?
that need to be completed.
When will it be This includes important milestones and the timeline

When?
completed? for the project.
This is where you determine which team member

Who is responsible for
Who? takes on which responsibilities. You may also identify
each function?
external stakeholders with a claim in the project.
This step gives you time to determine what other
Where are they
Where? stakeholders have a role in the project and where
organizationally located?
they are found.
How will the job be done

In this step, a strategy for developing the software
How? technically and
and managing the project is concluded upon.
managerially?
How How much of each The goal of this step is to figure out the number of
Much? resource is needed? resources necessary to complete the project.
Software Measurement and Metrics

Software Measurement: A measurement is a manifestation of the size, quantity,
amount, or dimension of a particular attribute of a product or process. Software
measurement is a titrate impute of a characteristic of a software product or the
software process. It is an authority within software engineering. The software
measurement process is defined and governed by ISO Standard.
Software Measurement Principles:

The software measurement process can be characterized by five activities-
1. Formulation: The derivation of software measures and metrics appropriate

for the representation of the software that is being considered.
2. Collection: The mechanism used to accumulate data required to derive the
formulated metrics.
3. Analysis: The computation of metrics and the application of mathematical
tools.
4. Interpretation: The evaluation of metrics resulting in insight into the quality
of the representation.
5. Feedback: Recommendation derived from the interpretation of product
metrics transmitted to the software team.
Need for Software Measurement:

Software is measured to:
• Create the quality of the current product or process.

• Anticipate future qualities of the product or process.
• Enhance the quality of a product or process.
• Regulate the state of the project in relation to budget and schedule.
Classification of Software Measurement:

There are 2 types of software measurement:
1. Direct Measurement: In direct measurement, the product, process, or thing
is measured directly using a standard scale.
2. Indirect Measurement: In indirect measurement, the quantity or quality to
be measured is measured using related parameters i.e. by use of reference.
Metrics:
A metric is a measurement of the level at which any impute belongs to a system
product or process.
Software metrics will be useful only if they are characterized effectively and validated
so that their worth is proven. There are 4 functions related to software metrics:
1. Planning
2. Organizing
3. Controlling
4. Improving
Characteristics of software Metrics:
1. Quantitative: Metrics must possess quantitative nature. It means metrics can

be expressed in values.
2. Understandable: Metric computation should be easily understood, and the
method of computing metrics should be clearly defined.
3. Applicability: Metrics should be applicable in the initial phases of the
development of the software.
4. Repeatable: The metric values should be the same when measured
repeatedly and consistent in nature.
5. Economical: The computation of metrics should be economical.
6. Language Independent: Metrics should not depend on any programming
language.
Classification of Software Metrics:

There are 3 types of software metrics:
1. Product Metrics: Product metrics are used to evaluate the state of the
product, tracing risks and undercover prospective problem areas. The ability
of the team to control quality is evaluated.
2. Process Metrics: Process metrics pay particular attention to enhancing the
long-term process of the team or organization.
3. Project Metrics: The project matrix describes the project characteristic and
execution process.
o Number of software developer
o Staffing patterns over the life cycle of software
o Cost and schedule
o Productivity
Advantages of Software Metrics :
1. Reduction in cost or budget.

2. It helps to identify the particular area for improvising.
3. It helps to increase the product quality.
4. Managing the workloads and teams.
5. Reduction in overall time to produce the product,.
6. It helps to determine the complexity of the code and to test the code with
resources.
7. It helps in providing effective planning, controlling and managing of the
entire product.
Disadvantages of Software Metrics :
1. It is expensive and difficult to implement the metrics in some cases.

2. Performance of the entire team or an individual from the team can’t be
determined. Only the performance of the product is determined.
3. Sometimes the quality of the product is not met with the expectation.
4. It leads to measure the unwanted data which is wastage of time.
5. Measuring the incorrect data leads to make wrong decision making.

Project MGT and Metrics

Uploaded by

Copyright:

Available Formats

Project MGT and Metrics

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project MGT and Metrics

Uploaded by

Copyright:

Available Formats

The Management Spectrum:

In software engineering, the management spectrum describes the management of a software

The Management Spectrum | 4 P’s in Software Project Planning

Why the system is going to be developed?

When is this done?

Who are the reasons for these activities in this project?

Where are these authoritatively located?

How is the job technically and managerially finished?

How much part of each resource is required?

This W5HH principle of Boehm is appropriate irrespective of the scale or difficulty of

This is the guiding principle in determining the tasks

When will it be This includes important milestones and the timeline

This is where you determine which team member

How will the job be done

Software Measurement and Metrics

Software Measurement Principles:

1. Formulation: The derivation of software measures and metrics appropriate

Need for Software Measurement:

• Create the quality of the current product or process.

Classification of Software Measurement:

Characteristics of software Metrics:

1. Quantitative: Metrics must possess quantitative nature. It means metrics can

Classification of Software Metrics:

1. Reduction in cost or budget.

Disadvantages of Software Metrics :

1. It is expensive and difficult to implement the metrics in some cases.

You might also like