Please enable JavaScript.
Coggle requires JavaScript to display documents.
Task #2 Team 4, References Project Management Institute, Inc.. (2017).…
Task #2
Team 4
:check:
Project quality management:
8.1 Quality indicator :check:
It documents how the project is going to demonstrate the accomplishment of the standards of quality.
Provides direction about the management of quality in the project.
Plan Quality Management: process in which the quality requirements/standards as well as the deliverables of a project are identified.
8.1.2 Tools and Techniques
8.1.2.2 Data Gathering
(techniques)
Benchmarking:
It involves comparing planned or actual project practices or also the project´s quality standards ito those comparable projects.
Brainstorming:
Used to gather data from team members to develop a quality management fited to the project.
Interviews
:
Identify the project and product quality expectations and needs, formal and informal by interviewing stakeholders, experienced project participants.
8.1.2.3. Data Analysis
(techniques)
Cost benefit analysis:
Financial analysis tool to estimate the weaknesses and strenghts of alternatives to determine the best one related to the benefits it provides.
Cost of quality:
It consists of the following costs for products, deliverables or services of the project:
Preventions costs:
related to the prevention of poor quality.
Appraisal costs:
related to measuring, evaluating, testing and auditing.
Failure costs:
realted to the nonconformance to the expectations or needs of the stakeholders.
8.1.2.1 Expert Judgement
The expertise from groups or individuals with specialized knowledge in topics like quality control, assurance, mesurements, among others should be considered.
8.1.2.4 Decision Making
Multicriteria decison analysis:
Its tools like the priorization matrix can be used in order to identify suitable alternatives and also key issues to be prioritized as a set of decisions for implementation.
8.1.2.5 Data presentation
Flowcharts:
They display the sequence of steps and the branching possibilities that exist for a process that transforms one or more inputs into one or more outputs. They show the activities, decision points, and the overall order of processing by mapping the operational details of procedures that exist within a horizontal value chain
Logical data model:
Are a visual representation of an organization’s data, described in business language and independent of any specific technology. The logical data model can be used to identify where data integrity or other quality issues can arise
Matrix Diagrams:
Help find the strength of relationships among different factors, causes, and objectives that exist between the rows and columns that form the matrix
Mind Mapping:
Used to visually organizing information. A mind map in quality is often created around a single quality concept, drawn as an image in the center of a blank landscape page, to which associated representations of ideas are added
8.1.2.6 Test and Inspection Planning
During the planning phase, the project manager and the project team determine how to test or inspect the product, deliverable, or service to meet the stakeholders’ needs and expectations, as well as how to meet the goal for the product’s performance and reliability
8.1.2.7 Meetings
Project teams may hold planning meetings to develop the quality management plan. Attendees can include the project manager, the project sponsor, selected project team members, selected stakeholders, anyone with responsibility for project quality management activities, and others as needed
8.1.3 Outputs
8.1.3.3 Project Management Updates
Risk Management plan:
The decisions on the quality management approach may require changes to the agreed-upon approach to managing risk on the project, being recorded here
Scope baseline:
May change as a result of this process if specific quality management activities need to be added. The WBS dictionary also records quality requirements, which may need updating
8.1.3.4 Project Document Updates
Lesson learned register:
The lessons learned register is updated with information on challenges encountered in the quality planning process.
Requirements traceability matrix:
Where quality requirements are specified by this process, they are recorded in the requirements traceability matrix
Risk register:
. New risks identified during this process are recorded in the risk
register and managed using the risk management processes
Stakeholder register:
Where additional information on existing or new stakeholders is gathered as a result of this process, it is recorded in the stakeholder register
8.1.3.2 Quality Metrics
Describes a project or product attribute and how the Control Quality process will verify compliance to it. Some examples of quality metrics include percentage of tasks completed on time, cost performance measured by CPI, failure rate, number of defects identified per day, etc.
8.3.1 Quality Management Plan
It describes how applicable policies, procedures, and guidelines will be implemented to achieve the quality objectives. It describes the activities and resources necessary for the project management team to achieve the quality objectives set for the project
8.1.1 Inputs
8.1.1.2 Project Management Plan Components
Risk management plan:
Provides the approach to identify, monitor and analyze risks.
Stakeholder engagement plan:
Provides the method in which the needs and expectations of the stakeholders are going to be documented.
Requirements management plan:
Provides the approach for managing. identifying and analyzingthe requirements that will be referenced in the quality management plan.
Scope baseline:
The scope statement includes the criteria of acceptance for the deliverables documented in the project as well as the implemnte processes for quality review.
8.1.1.3 Project Documents
Requirements documentation:
It contains the requirements that the project should achieve in order to meet the stakeholders expectations.
Components:
quality requirements of the project and product.
Requirements traceability matrix:
This matrix links the requirements of the product to the deliverables. It gives an overview of the tests that are required to verify the requierements.
Assumption log:
It contains assumptions and also constraints in respect of the standard compliance and the quality requirements.
Risks register:
It has information about opportunities and threats that may have an impact in the quality requirements.
Stake holder register:
It helps to identify the stakeholders that impact the quality of the project or to identify the stakeholders with special interest in it, taking into account the expectations and need of customers and project sponsors.
8.1.1.1 Project Charter
It provides the description of the project.
It contains factors that will influence the quality management of the product Like the approval requirements and its mesurable objectives
8.1.1.4 Entreprise Environmental Factors
Some factors that can have an inluence in the Plan Quality Management:
Marketplace conditions
Cultural perceptions
Regulations of Governmental agency
8.1.1.5 Organizational Process Assets
Some assets that influence in the Plan are:
Historical databases
Organizational quality management (guidelines, policies, etc.)
:check:
Risk management:
11.2 Identify risks and their responses :check:
Identifies and documents individual and overall project risks.
Individual project risk:
uncertain event or condition that, if it occurs, has a positive or negative effect on
one or more project objectives.
Overall project risk:
uncertainty on the project as a whole, including individual risks, representing the exposure of stakeholders to the implications of variations in project outcome, either positive or negative.
Gives information to all the team members on how to deal with the risks
11.2 Identify Risks
.2 Tools & Techniques
.2 Data gathering
Processes like: brainstorming, checklists and interviews
.3 Data analysis
Techniques like: Root cause analysis, Assumption and constraint analysis, SWOT analysis and Document analysis.
.4 Interpersonal and team skills
Improves the effectiveness of many of the techniques used to identify individual project risks and
sources of overall project risk
.5 Prompt lists
Predetermined list of risk categories that might give rise to individual project risks and that could also
act as sources of overall project risk
.6 Meetings
To undertake risk identification, the project team may conduct risk workshops.
.1 Expert judgment
Experts identify and consider all aspects of individual project risks and overall project risk, based on their previous experience and areas of expertise.
.3 Outputs
.1 Risk register
The results of Perform Qualitative Risk Analysis, Plan Risk Responses, Implement Risk Responses, and Monitor Risks are recorded in the risk register as those processes are being done.
.2 Risk report
Presents information on sources of overall project risk, and a summary information on identified fied
individual project risks
.3 Project documents update
Can be updated as a result of this process includes: Assumption log, Issue log and Lessons learned register.
.1 Inputs
.3 Agreements
Includes: brainstorming, checklists and interviews threats or opportunities
.4 Procurement documentation
Procurement documents are used to solicit proposals from prospective sellers.
.2 Project documents
Project documents provide the project team with information about decisions that help better identify project risks.
.5 Enterprise environmental factor
Enterprise environmental factors refer to conditions, not under the control of the project team, that influence, constrain, or direct the project.
.1 Project management plan
The project management plan provides baseline or current state of risk-affected areas including scope, schedule, and cost.
.6 Organizational process assets
The organizational process assets that can influence the Identify Risks process
References
Project Management Institute, Inc.. (2017). Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th Edition). Project Management Institute, Inc. (PMI). Retrieved from
https://app.knovel.com/hotlink/toc/id:kpGPMBKP02/guide-project-management/guide-project-management
