Project Quality Management - Doc

Project Quality Management
Name
Date

1.1 Quality Planning
The website must meet the set standards for web content as defined in the ISO/IEC
40500:2012- W3C web content accessibility guidelines ('International Organization for
Standardization', n.d.). This will ensure content accessibility to a wide public, including
those with disabilities and also defines the success criteria The website must also meet
the software criteria as set in the ISO 9126 standard for functionality, reliability,
usability, re-usability, and portability along with efficiency and maintainability. The
website must meet the standards of website design principles based on human
Computer Interaction (HCI) principles as well as the Gestalt principles of interface
design (Shimpeno, & Ezer,, 2014). The website must also meet the stipulations of the
ISO/IEC 25022:2016 standard for quality metrics in use ('International Organization for
Standardization', n.d.)
1.1.1 Define Project Quality
The website will be developed to meet the needs of the users, based on the user
requirements document, within the stipulated time and budget, and perform as per the
desired functionalities for software quality as defined under quality planning
1.1.2 Measure Project Quality
The quality of the project will be measured based on the project constraints; the metrics
to be measured include on -time performance, cost control, defect frequency, and
failure rate. The measurement for timely delivery will be evaluated against the project
schedule baseline and will be monitored constantly to ensure project remains on
schedule. The cost control will be measured against the budget baseline where actual
cost versus budgeted cost and expected cost to complete will be evaluated. The
software will then be measured based on performance and the set objectives for
performance as described in the user requirements. The test for website performance

will be done periodically during the end of each sprint backlog and rectified
1.2 Quality Assurance
The website must meet the performance measures as set under ISO/IEC 25022:2016:
In addition, the website must be able to load seamlessly in different platforms
(operating systems and web browsers) without loss of quality or features. The website
must load fast even during heavy use (multiple requests). The website must seamlessly
integrate with other systems, including databases and web payment processors as well
as social media. The website must be available 99% of the time (no downtimes), and if
there is a downtime, then a cloud based backup must immediately be loaded. The
website must be user friendly and easy to navigate and this is to be evaluated and
measured through user reviews and comments. During development, testing will be
done at the end of every sprint and tested with users; any issues will be identified and
rectified , and then tested again before further development is done. This will ensure
the final product has as few defects as possible and maintainability is possible to plug
future problems. Scalability will be inbuilt into the website during its development
(Roseke, 2017)
1.2.1 Analyse Project Quality
Will be done through fit analysis of software to the user requirements. The seven basic
tools of quality will be used to evaluate root problems encountered, along with project
monitoring tools for consistency with the budget, cost to complete, and scope (Cano,
Moguerza, & Corcoba, 2015). The project scope will be controlled strictly to ensure
scope creep does not happen and that the scope changes are managed well
1.2.2 Improve Project Quality
The defined project quality metrics will be evaluated and tools such as the Pareto chart,
check sheets, cause and effect diagrams used for improving quality (Cano, Moguerza,

& Corcoba, 2015). The principles of TQM (total quality management) will be
incorporated in improving project quality, along with lean principles of continuous
improvement. Following the SCRUM agile methodology, improvements will be inbuilt
into the project management and website quality management
1.3 Quality Control
This will be performed iteratively during the end of each sprint backlog and inspection
of the website will be done through testing and making improvements to ensure defined
quality standards are met. Tools to be used include the Pareto chart and control charts

References
Cano, E. L., Moguerza, J. M., & Corcoba, M. P. (2015). Quality control with R: An ISO
standards approach. Heidelberg: Springer CHAM.
'International Organization for Standardization'. (n.d.). ISO/IEC 25022:2016 - Systems and
software engineering -- Systems and software quality requirements and evaluation (SQuaRE)
-- Measurement of quality in use. Retrieved from https://www.iso.org/standard/35746.html
Roseke, B. (2017, March 30). Project Quality Assurance According to the PMBOK.
Retrieved from http://www.projectengineer.net/project-quality-assurance-according-to-the-
pmbok/
Shimpeno,, P., & Ezer,, N. (2014, March). Improving the User Interface through Gestalt
Design Principles. Paper presented at The 26th Annual IEEE Software Technology
Conference, Long Beach, CA.