APM - Module 7
- Created by: Daisy Parker
- Created on: 07-02-21 14:09
View mindmap
- Project Management - Quality Assurance in Projects
- What is Quality Management?
- Quality management is a discipline for ensuring that outputs, benefits, and the processes by which they are delivered, meet stakeholder requirements and are fit for purpose
- Processes
- Measure of processes and procedures deployed to manage the project itself
- Quality Planning
- Takes the definied scope of the project and specifies criteria to be used to validate that the outputs meet the requirements of the project sponsor
- As a result, a Quality Plan will be created and form a key part of the PMP
- The agreed acceptance criteria in the PMP will provide guidance to the team regarding requirements and essential conditions for deliverables
- The Quality Plan should include:
- Methods of verifying the requirements are met
- pass/fail criiteria for each method
- Frequency of checks/audits and tests
- Requirements for resources needed
- Quality Control
- Consists of inspection, measurement and testing to verify that the products meet the acceptance criteria defined
- Quality control may take place through: PAT Testing, Sampling, 'Walk-Throughs', User Acceptance Testing....
- Quality Assurance
- Attempts to build quality into the project through the consistent use of standard processes and procedures
- Methods to implement quality assurance include Lessons Learnt, Audits, Training, Supplier Accreditation..
- Quality Assurance must be performed by a person independant of the project, as to ensure no bias
- Activities to check quality assurance should begin as soon as the project starts management activity
- Continuous Improvement
- The correct use of feedback and using the lessons of the past to drive the actions of the future
- Can take place either: from lessons learned, at phase reviews and/or through formal processes e.g. Kaizen, Six Sigma
- Plan, Do, Check, Act (PDCA)
- Products
- Measure of the fitness of outputs agaisnt requirements
- Requirements Management
- The process of capturing, assessing and justifying stakeholders wants and needs.
- It should break down requirements in a hierarchical mannerm considering different conditions and scenarios
- Should show clear linkage between benefits, project success criteria, projects objectives and project requirements
- Requirements can be gathered through: Interviews, Surveys, Workshops, Focus Groups, Modelling and Simulation
- In order to prioritise requiements, it is common to use the MoSCoW approach: Must, Should, Could, Won't haves.
- In a worst case scenario, a project must still deliver the 'Must haves' in the form of a Minimum Viable Product (MVP)
- Change Control
- A process through which all requests to change the baseline of a projects are identified, evaluated, and then approved, rejected or deferred
- The change request should clearly highlight what the change is, who has requested the change and why the change is needed
- Managing chance correctly enables stakeholders to influence decisions of how to respond in the context of their objectives
- A process through which all requests to change the baseline of a projects are identified, evaluated, and then approved, rejected or deferred
- Configuration Management
- The technical and administrative activities concerned with the creation, maintenance, controlled change and quality control of the scope of the project
- Configuration Management Process
- Cofiguration Management includes various tasks
- Document Control: Ensuring that all the relevant people have access to the most up-to-date document and no-one can change the document without authority
- Document Identification: Uniquely identifying each document
- Status Reporting: What status is the document? Draft? Final version?
- Version Control: Ensure ‘one-version-of-the-truth’
- Configuration Management ensures confidence that the current items / resources are know, and there is documented traceability between versions
- Why is Quality Management Important?
- Reduces Faults: managing quality works to ensure minimal faults with product outcome and issues cause by processes
- Reduces Re-Work and Costs: Clear requirements and forecasts should allow for efficient project planning
- Creates Confidence: Effective quality planning allows stakeholders to have visibility in the project, and confidence in a high quality output
- Reduces Risk: Forward planning and confidence in processes should ensure fewer risks and issues with the delivery and final output
- Improved Efficiency: Quality Management is to ensure all processes and streamlined and beneficial, which leads to a better final product
- What is Quality Management?
- Plan configuration management processes and activities
- Identify Configuration items and dependencies
- Apply change control to configuration item changes
- Create records and reports to demonstrate traceability
- Verify integrity of configuration before use
- Plan configuration management processes and activities
- Identify Configuration items and dependencies
- Apply change control to configuration item changes
- Create records and reports to demonstrate traceability
- Verify integrity of configuration before use
- Verify integrity of configuration before use
- Create records and reports to demonstrate traceability
- Apply change control to configuration item changes
- Identify Configuration items and dependencies
- Plan configuration management processes and activities
- Verify integrity of configuration before use
- Create records and reports to demonstrate traceability
- Apply change control to configuration item changes
- Identify Configuration items and dependencies
Comments
No comments have yet been made