1

Managing Quality in Project Management

Group -11
 2

Table of Contents

Phases in Project Quality Management

I. Quality Planning

The success and failure of a project largely depend on the scope. If you are not keeping tabs of the
project scope, your project can slip out of control. It messes up the project schedule and has a poor
impact on your budget. This leads to project failure.
Project scope defines project goals and objectives and how the processes run. That’s where a project
scope management plan comes in. A project scope management plan helps you list the goals,
deliverables, requires resources, and all the other significant parameters of the project. Project scope
ensures that there is a systematic mechanism to incorporate changes. This helps fulfill new
requirements without putting any strain on the budget, schedule, and deadlines.
Project scope management plan is a solid and comprehensive plan to make sure that the project runs
smoothly, changes are included flexibly, and deliverables meet respective deadlines. Here’s how to
write an effective project scope management plan in 11 steps:
1. Study Project Charter and Project Management Plan
As you need to begin somewhere, nothing is better than reviewing the project core documents. These
mainly include project charter and the project management plan.
Project Charter
Project charter identifies statements of objectives, stakeholders, project goals, and roles and
responsibilities of each team member. It acts as a proper framework to guide through the scope
management plan. It includes key descriptions of the project as well as the characteristics of the
product that is being created.
Project Management Plan
A project management plan is a project schedule that enlists all the tasks of the project. It acts as a
baseline that shows the significance of formulating a scope management plan.
The project management plan includes several other helpful documents, such as a quality
management plan, project life cycle description, and development approach. Reviewing these
documents allows you to establish a sound basis for scope management.

2. Consider Enterprise Environmental Factors

Enterprise environmental factors need to be taken into account when planning the most important
processes of the project. As scope management is one of them, enterprise environmental factors can
make or break this plan. The most crucial enterprise environmental factors to consider are:
 Organization’s work culture i.e., formal, informal, mixed, or productive.
 Infrastructure, available resources such as tools and equipment
 Personnel to judge expertise, training, and capabilities
 Marketplace conditions to study the market growth, competitors, and intensity of competition.
 3
Once the project manager considers all of these factors, he is in a good position to define and create
an effective scope management plan.
3. Conduct Meetings
The next step is to hold meetings with the project team, project sponsors, and stakeholders. Regular
meetings allow you to identify loopholes and project constraints. Also, it offers an opportunity to
discuss the aspects related to the scope management plan.
Get Help from the Expert Judgement
Whenever you conduct a meeting to look into project scope management, make sure you invite
subject matter experts. These include stakeholders and other project-related experts from the industry.
The expert judgment allows better insight into project processes, and you get a good idea of how to
streamline the project through better scope management.
Gather and Analyze the Data
Data analysis is a handy technique when writing down a scope management plan. Implementing
various data analysis techniques helps you collect the project requirements, create a great product,
and control the overall project scope.
Look into Stakeholder Requirements
Considering stakeholder requirements is another important thing to do during meetings. If you so
prefer, you can hold meetings with stakeholders separately to identify and prioritize the requirements.
Missing a minor requirement can turn the project upside down. Therefore, look into the requirements
carefully, no matter the magnitude and significance. Various techniques, such as Requirements
Traceability Matrix can be really helpful.

4. Write Down the Scope Statement

The scope statement is the detailed listing of project goals, objectives, assumptions, and constraints. It
basically defines your entire project. The scope statement acts as the foundation and is the core
component of a scope management plan.
The scope statement mentions what is going to be part of the project and what is not. It is not possible
to include every nut and bolt of the project; however, spending some good time on the scope
statement is always a great idea. It has to be detailed and comprehensive to include requirements,
judge the results, and reduce the risk of any changes.
5. Design a Work Breakdown Structure (WBS)
The next step is to design a work breakdown structure, commonly known as WBS. In its most basic
form, it is a simple list of the project task, resources, and deadlines. 
But, you must know that EBS acts as the project guide and schedule. Therefore, it is best to have a
detailed mention of project activities and division of tasks according to their priority, project schedule,
and allocated resources.
The resources include equipment, tools, costs, human resource, and required hours. There are
several different formats to create WBS. You can either use graphical representation or tabular form to
create and represent WBS. The structure of WBS varies from project to project. Usually, the structure
is based on the categorization and sub-categorization of tasks.
6. Develop Maintenance and Approval Process for WBS
Creating WBS alone is not enough. The scope management plan includes a proper mechanism for the
approval and maintenance of WBS.
Approval of WBS depends on the project manager but, more significantly, stakeholders. Figure out
how the WBS will be approved. Is it going to be in a meeting, an email, or over a video conference?
 4
For quick approval, make sure you have focused on all the stakeholders’ requirements and have
incorporated desired changes.
When it comes to maintenance, the best way to maintain WBS is to create a WBS dictionary, which
includes the minimum yet significant amount of information such as task code, task description, and
responsible sector or individuals.
If you want more comprehensive and effective maintenance, you can include other information such as
start date, end date, budget, deliverable, and required resources.
7. Determine Roles and Responsibilities of Project Team
The scope management plan includes a detailed mention of all the individuals’ roles and
responsibilities directly or indirectly linked to the project. It includes your organization’s manager, HR
manager, project manager, development team, technical experts, engineer, and every other
concerned individual.
Although roles and responsibilities are determined before the beginning of the project, they might be
subjected to change if there is any change in the project scope. Therefore, they are a significant part of
the scope management plan.
8. Identify Your Deliverables
The next step and component of the scope management plan are deliverables. Once you are done
with creating WBS and assigning roles and responsibilities, it is now easier to identify your
deliverables.
Deliverables include physical tasks such as building the software, product design, and product report,
and so on. Sometimes, deliverables are non-physical such as improvement of the design, etc. No
matter the nature of deliverables, each deliverable must be identified as part of the scope
management plan.
9. Gather Feedback and Incorporate Changes
As you complete a project deliverable, you need to offer it to the stakeholders and gather feedback so
that the changes are incorporated right away. To do this, there has to be a process. Following a proper
process, you can be satisfied that your deliverable is formally accepted. 
The feedback also helps in making improvements in the other similar deliverables before they are
completed and delivered.
10. Establish Scope Control Mechanism
Scope control is the most significant aspect of scope management. Therefore, you need to establish
an effective scope control mechanism. As you design the scope control process, your scope
management plan is about to complete.
Scope control means the project manager will not have to face scope creep. You need to ensure that
no unauthorized task is added to the project as it can be really toxic. There has to be a proper
mechanism that looks into new processes and examines changes done to the project. Scope control
procedures allow efficient and effective communication and incorporation of the changes.

II. Quality Assurance (QA)

Review Activities - Quality Assurance (QA)

The Review Activities of software quality control process are as follows:
 5
Review Activities
a. Requirements Review
b Design Review
c. Coding Review
d. Test Plan Review
e Test Cases Review
f Deployment Review

The Review Activity is one type of static testing or verification process of the software documents to
prevent defect. It is process-oriented to improve the development process performed without program
execution. The requirement document, design review are part of it. It has multiple review activities like
requirements, design, coding, test plan, test cases and deployment within the software development
life cycle process. This is a process level verification to prevent the defect from the software
application documents

III. Quality Controls (QC)

The Testing Activities of the software quality control process are as follows:

Testing Activities
a. Unit Testing
b Integration Testing
c. System Testing
d. Acceptance Testing
e Release Testing
f Maintenance Testing

The Testing Activity is a one type of Dynamic in nature or validation process of the software
application to find the defects. It has product oriented to enhance the software product quality,
performed with program execution. The product testing is the main part of it and has multiple testing
activities like unit, integration, system, acceptance, release and maintenance testing phases within the
software development life cycle process.
In this activity we also use some extra functional levels of testing like smoke testing, sanity testing,
retesting, regression testing and some non-functional testing like performance testing, stress testing,
load testing, volume testing, endurance testing to improve the priority (urgency of fix the defect) and
severity (Impact of defect) of the developed software product quality. So the both QA(verification) and
QC(validation) process are internally related to the software quality control improvement process.

a. Unit Testing
The testing of the smallest independently executable parts /units/components of the software
application. It is also known as component testing. It is done by the development team early in the
development stage.
b. Integration Testing
In this testing, to find the defects or bugs in interfaces or interactions between components/units i.e. to
test the combined units are works or not. It is done by the Technology/Development Lead not done by
Testers. There are two approaches of Integration Testing i.e. Top Down and Bottom Up approach.
 6
Here test drivers and test stubs are used to assist the integration testing workflow. When there are
temporary programs in the applications to substitute programs in development, are called stubs and
drivers. The main program if replace is called a Driver and if the lower programs are replaced, then it is
called Stubs. When we have stubs and drivers we call the environment as Test Harness.
c. System Testing
Once deployment team sends a mail that software is installed into the test environment. We start with
build verification testing (Smoke test). Here we check if minimum features are working and send a mail
to the development team that we are accepting or rejecting the built. It is also called end to end testing
and performed by the testing team at testing environment. When two or more applications need to
operate together, there is one more level of testing between system testing and user acceptance
testing is called system integration testing.
d. Acceptance Testing / User Acceptance Testing
The objectives of this testing are:
 To gain confidence for release.
 To check if the software is fit for the purpose.
 Checking the software from a business point of view.
It is performed by the client. It has two types such as Alpha Testing and Beta Testing. The Alpha
Testing is called Business Acceptance Testing (BAT) or Factory Level Testing, performed by the client
in the development organisation site. The Beta Testing is called Product Verification Testing (PVT) or
Field Level Testing, performed by the client in the place where the software being used.
e. Release Testing
The release testing is a final testing phase of software product or application to verify, the developed
software to be release. Here the entire functionalities of that application should be tested to ensure the
readiness of the software application.
f. Maintenance Testing
The testing of the software which is in production, when there are changes to either the (i.e. defects or
modifications) software or to the environment. In this phase, we plan on Impact Analysis i.e.
the change control board (CCB) would be a group of architects, designers, developers and
testers, who can judge the impact of change asked by the client i.e. change request (CR). It is
also helpful for testing as it guides where to do most of the testing i.e. retesting and regression
testing. This type of testing done by the testers.

Software Quality Control Standards

There are some ISO standards to review/describes the quality of software developed product. The
ISO/IEC/IEEE having proposed a number 29119 for internationally standard in software quality control,
which followed by software development life cycle (SDLC) model of development process. It has
mainly five international levels of software quality control (QC) standards and some sub standards to
review both process level & product level of the application.
They are as follows:
1. International Software QC Standards
 ISO/IEC 29119-1: It indicates the concepts and definitions of software.
 ISO/IEC 29119-2: It indicates the different test processes in a software product.
 ISO/IEC 29119-3: It deals with testing related documents of the software application.
 ISO/IEC 29119-4: It describes the different testing techniques and plans for that software
product.
 7
 ISO/IEC 29119-5: It deals with different type’s keyword driven software testing.
2. Auxiliary Software QC Standards
 IEEE 730: It deals with software product verification i.e. Quality Assurance (QA).
 IEEE 830: It describes the accurate development of software application with proper
requirements.
 EEE 1008: This standard deals with unit testing of the developed application.
 IEEE 1012: It deals with the verification and validation of application.
 IEEE 1028: This standard deals with proper software application inspection purpose.
 IEEE 1044: It is used to check some inconsistency in application software.
 IEEE 1059: It deals with application guiding verification and validation.
 IEEE 1061: This standard is used for better quality of software product development i.e. to
deals with application quality metrics.
 IEEE 12207: It is used for used development life cycle processes of application.
Software Quality Control Techniques
The Quality control is a process followed by the IT organisation to develop extreme quality software
product and improve the organisation productivity as well as goals of software product. There are
multiple techniques/methods for software quality control of software application, but the PDCA (Plan
Do Check Action) technique is one of the best approach towards software quality control.
 Goal Question Centric Model
 Overall Risk Management Model
 The PDCA Model
 Overall Software Quality Control Model
 Quality Control By Spiral Model
 Control Management Model

PDCA Model
It stands for Plan-Do-Check-Action model. It is one of the simplest models of software development
process through which the quality control of the application done from the initial stage of the
development. The parameters like product/application, processes and resources are the influences the
quality control of the software application.
It contains four phases:
 Plan
 Do
 Check
 Action

1. Plan: During this initial phase the software quality control processes are initiated or planned. Here
 8
to set standard software quality goal and plan accordingly to get it.
2. Do: In this phase to start developing the software application according to the project plan
parameters to execute it i.e. work in progress state. 
3. Check: In this phase dedicated to the static and dynamic testing of the developed software
application to find defects to improve the quality of product. Here we validate the excepted output
values with actual parameter values.
4. Action: During this phase the corrective actions takes place to remove bugs or issues from the
developed software product i.e. the bugs are fixed and the rework action done if needed.
Advantages and disadvantages of Software Quality Control
Given below are the advantages and disadvantages:
Advantages
Below are the advantages
 It is used to validate the software application as per the client needs and exception.
 The software QC is used to identify the defects in the software application.
 It improves the productivity of software development team as well as software product quality.
 It enhances the organizational ability to produce a high quality software product.
 It makes the final software product ready to deliverable.
 Increased the build trust in project management and future level development.
 It used to reduce the re-development or re-work cost as the Software QC will impose from
scratch level of development phase.
 It boosts the customer satisfaction and efficiency of the software product.
 It is a reactive approach and separate testing team will involves finding defects.
Disadvantages
Below are the disadvantages
 It requires more time consuming process testing.
 The deployment of software product should be delay.
 It needs more resources for software product validation.
 Each individual of the team doesn’t take responsible of quality of own work.
 If the software application is rejected, then there is a big issue in budgeting for organisation.
9