Quality Management in Software Development

This assignment delves into the crucial aspects of quality management within software development projects. It emphasizes the need for a comprehensive quality management plan that addresses factors like cost-benefit analysis, identifying and rectifying processes deviating from quality standards, and implementing continuous improvement strategies. The plan involves executing quality assurance activities throughout the project lifecycle, validating deliverables against established requirements, utilizing quality control metrics to identify and address failures, and employing tools for root cause analysis and continuous improvement.

Surname 1
Name
Instructor
Course
Date
Manage IT Project Quality

Surname 2
TABLE OF CONTENTS
INTRODUCTION...........................................................................................................................3
TASK 1............................................................................................................................................3
1.1 Determine project quality requirements with reference to project scope and stakeholder
needs and expectations.................................................................................................................3
1.2 Adopting an organizational quality policy and quality standards with stakeholders.............4
1.3 Determine project quality management approach, including proposed quality assurance
processes and quality control measurement methods and benchmarks.......................................5
1.4 Negotiate project quality, cost, time trade-offs and changes to stakeholder expectations if
necessary......................................................................................................................................5
1.5 Develop a quality management plan for the project and obtain sign-off...............................5
2.1 Execute quality assurance activities as the project progresses according to the quality
management plan.........................................................................................................................6
2.2 Identification project processes not meeting quality standards agreed in the quality
management plan.........................................................................................................................7
2.3 Raise project change request to action process changes or corrective actions, update
project-management plan and quality baselines as necessary.....................................................7
3.1 Validate project processes and deliverables against quality requirements as the project
progresses.....................................................................................................................................7
3.2 Quality Control metrics and take action as necessary to investigate and understand the
reasons for failure.........................................................................................................................7
3.3 Quality management tools to determine failures and root causes and implement continuous
improvement processes................................................................................................................8
WORKS CITED............................................................................................................................10

Surname 3
INTRODUCTION
Quality IT management is a process that ensures the project activities necessary to plan,
design, and implement IT project is efficient and effective with respect to performance objectives
and meeting stakeholder requirements. To effectively manage IT project Quality, the following
components should put into consideration when making software products and services: quality
planning, quality assurance, quality control, and continuous assessment. It’s also important to
highlight the procedures, tools and techniques necessary for ensuring that the output and the
benefits satisfy the requirements of the customer. The objective of IT project should be designed
in a manner that it meets the requirements of the stakeholder as well as meeting their
expectations.
TASK 1
1.1 Determine project quality requirements with reference to project scope and stakeholder needs
and expectations
The below outlined project quality requirements are significant aspects in achieving the
desired objective:
 Functionality- Managing quality IT project should have a certain degree of performing
the intended function. This is important especially in complex IT projects and making
sure that the operation behaves as per expectation.
 Performance- IT products and services should be designed in such a way that it performs
the beneficiaries intended use. IT system applications should be designed with the ability
to reduce costs and increasing sustainability even in extreme and complex projects.

Surname 4
 Reliability- IT projects need to possess the ability to perform under normal conditions
without unnecessary failures. The information should be dependable and consistent.
 Relevance- The project needs to meet the actual needs of the beneficiaries; it should be
applicable, pertinent, and appropriate to the intended application or use.
 Timeliness- Time is a very important project characteristic especially in solving problems
so that stakeholders are not disappointed.
1.2 Adopting an organizational quality policy and quality standards with stakeholders
Quality planning is basically the first component involving a detailed preparation of a
quality plan. Quality management plan describes the metrics and processes to be used. Software
development requires preparations of quality planning so to achieve unique software systems and
engineering projects customized to meet customers’ expectations. As per ISO 9001
requirements, the top management should be actively in quality planning the software
management system.

Surname 5
At the company level, IT quality planning focuses on development, improving and
maintaining the overall system quality management.
1.3 Determine project quality management approach, including proposed quality assurance
processes and quality control measurement methods and benchmarks
IT Quality Assurance
IT quality assurance involves the process of designing an effective quality management
aimed at building stakeholders confidence with the assurance that the organization or the project
will be able to deliver quality IT products and services to the end users.
IT Quality Control
Quality control aims at testing the software development and intensive systems to
determine whether they have defects, and measuring the actual quality. In the context of software
development, the test assesses the specifications, descriptions, designs, executable software
modules, code listings, units, complete and subsystems.
1.4 Negotiate project quality, cost, time trade-offs and changes to stakeholder expectations if
necessary
The cost of entire project will be £5500 and time frame completing the work will be 5 months.
1.5 Develop a quality management plan for the project and obtain sign-off
 Quality goals and objectives- the overall goal of quality management programs it to
achieve measurable objectives.
 Quality management system scope- The software development should have incredible
impacts on the end users and therefore, the product scope, process scope, organization
scope needs greater attention.

Surname 6
 Responsibilities and organization- it is important to report relationships, observe
organizational structure, maintaining roles and responsibilities with the sole objective of
achieving the desired quality.
 Resource requirements- identifying appropriate resources and the right people required in
developing, maintaining, using, and improving software quality management system.
 Cost benefit analysis- an analysis of quality program cost benefit need to address certain
issues including the costs associated with poor quality, improvement costs, and measures
of achieving the cost benefits.
 Deliverables and activities- the elements necessary to develop quality management
system should be produced and improved as well as the required activities.
 Schedule- it is important to observe the time frames within which work need to be done
and the major milestones in quality management system that enables quick delivery,
deployment, and review.
 Risk analysis- Risk reduction should be of high priority analyzing possible unexpected
eventualities.
2.1 Execute quality assurance activities as the project progresses according to the quality
management plan
In the context of software system and development, the project should build confidence
by developing customized IT systems that meets the needs of the beneficiaries. In contracted
software development, stakeholders need an assurance that IT projects will produce products and
services capable of solving problems at an affordable price, and within a specific time frame.
2.2 Identification project processes not meeting quality standards agreed in the quality
management plan
Quality metrics will be used as a project process when the quality standards of IT project
not meet. It will help the project manager to guide and take decisions how to control and

Surname 7
maintain the quality of work. By this, it will become easy to track defects and other errors in the
software.
2.3 Raise project change request to action process changes or corrective actions, update project-
management plan and quality baselines as necessary
To make the changes in the project, the project manager will adopt change request
process which contains some steps that are as follows:
 Determine the required changes
 Indentify the impact of changes in project scope
 Create change request form
 Take approval or rejection confirmation
 Make changes in the plan
3.1 Validate project processes and deliverables against quality requirements as the project
progresses
The entire project plan completed within the given constrains. All expected deliverables
been achieved by the project manager from the following plan.
3.2 Quality Control metrics and take action as necessary to investigate and understand the
reasons for failure
Quality control activities should be performed throughout the life cycle of software
development. Defects discovered at early stages are less expensive to fix.

Surname 8
Quality control metrics indicators provide important data efficient for software development
process and a vital trigger for software improvement.
3.3 Quality management tools to determine failures and root causes and implement continuous
improvement processes
Quality Improvement Cycle
Continuous IT quality improvement is a fundamental requirement for checking the
performance of the quality of software management system. Quality improvement is a core
principle that needs to be a recurring process in the life of a software system. Without quality
improvement, the quality of a product or service deteriorates with time and the results could be
catastrophic.

Surname 9
IT Quality Policy
IT Quality policy simply describes the core beliefs that drives IT project to deliver
quality, intensive software system. It’s the project constitution informing the end users actions
especially where there are no specific guiding procedures. Also, a policy summarizes a measure
of success as well as indicating customer’s satisfactions. Additionally, an IT policy furthermore
describes the general quality principles including planning, monitoring and controlling,
documenting requirement, architectural design, coding, testing, and managing quality.

Surname 10
WORKS CITED
Lessard, Charles S, and Joseph Lessard. Project Management for Engineering Design. Morgan
& Claypool Publishers, 2007.
Pratt, David. The It Project Management Answer Book. Management Concepts P, 2012.
Schwalbe, Kathy. Information Technology Project Management. Course Technology, 2014.