Основы управления качеством

• Quality standards provide requirements, specifications, or guidelines that can be used to ensure that products, processes, or services are fit for achieving the desired outcome. These standards must be met in order for the product, process, or service to be considered successful by the organization and the customer. You will set quality standards with your team and your customer at the beginning of your project. Well-defined standards lead to less rework and schedule delays throughout your project.

• Quality planning involves the actions of you or your team to establish and conduct a process for identifying and determining exactly which standards of quality are relevant to the project as a whole and how to satisfy them. During this process, you’ll plan the procedures to achieve the quality standards for your project.

• Quality assurance, or QA, is a review process that evaluates whether the project is moving toward delivering a high-quality service or product. It includes regular audits to confirm that everything is going to plan and that the necessary procedures are being followed. Quality assurance helps you make sure that you and your customers are getting the exact product you contracted for.

• Quality control, or QC, involves monitoring project results and delivery to determine if they are meeting desired results. It includes the techniques that are used to ensure quality standards are maintained when a problem is identified. Quality control is a subset of quality assurance activities. While QA seeks to prevent defects before they occur, QC aims to identify defects after they have happened and also entails taking corrective action to resolve these issues.

The goals of UAT

Important

UAT is testing that helps a business make sure that a product, service, or process works for its users. The main objectives of UAT are to:

• Demonstrate that the product, service, or process is behaving in expected ways in real-world scenarios.
• Show that the product, service, or process is working as intended.
• Identify issues that need to be addressed before project completion.

Best practices for effective UAT

In order to achieve these goals, UAT needs to be conducted thoughtfully. These best practices can help you administer effective UAT:

• Define and write down your acceptance criteria. Acceptance criteria are pre-established standards or requirements that a product, service, or process must meet. Write down these requirements for each item that you intend to test. For example, if your project is to create a new employee handbook for your small business, you may set acceptance criteria that the handbook must be a digital PDF that is accessible on mobile devices and desktop.

• Create the test cases for each item that you are testing. A test case is a sequence of steps and its expected results. It usually consists of a series of actions that the user can perform to find out if the product, service, or process behaved the way it was supposed to. Continuing with the employee handbook example, you could create a test case process in which the user would click to download the PDF of the handbook on their mobile device or desktop to ensure that they could access it without issues.

• Select your users carefully. It is important to choose users who will actually be the end users of the product, service, or process.

• Write the UAT scripts based on user stories. These scripts will be delivered to the users during the testing process. A user story is an informal, general explanation of a feature written from the perspective of the end user. In our employee handbook example, a user story might be: As a new employee, I want to be able to use the handbook to easily locate the vacation policy and share it with my team via email.

• Communicate with users and let them know what to expect. If you can prepare users ahead of time, there will be fewer questions, issues, or delays during the testing process.

• Prepare the testing environment for UAT. Ensure that the users have proper credentials and access, and try out these credentials ahead of time to ensure they work.

• Provide a step-by-step plan to help guide users through the testing process. It will be helpful for users to have some clear, easy-to-follow instructions that will help focus their attention on the right places. You can create this plan in a digital document or spreadsheet and share with them ahead of time.

• Compile notes in a single document and record any issues that are discovered. You can create a digital spreadsheet or document that corresponds to your plan. It can have designated areas to track issues for each item that is tested, including the users’ opinions on the severity of each issue. This will help you prioritize fixes.

Managing UAT feedback

Users provide feedback after performing UAT. This feedback might include positive comments, bug reports, and change requests. As the project manager, you can address the different types of feedback as follows:

• Bugs or issues: Users might report technical issues, also known as bugs, or other types of issues after performing UAT. You can track and monitor these issues in a spreadsheet or equivalent system and prioritize which issues to fix. For instance, critical issues, such as not being able to access, download, or search the employee handbook, need to be prioritized over non-critical issues, such as feedback on the cover art of the handbook.

• Change requests: Sometimes the user might suggest minor changes to the product, service, or process after UAT. These types of requests or changes should also be managed and prioritized. Depending on the type and volume of the requests, you may want to share this data with your primary stakeholders, and you may also need to adjust your project timeline to implement these new requests.

Managing UAT Feedback

Types of Feedback

Users provide different types of feedback after performing UAT, including:

• Positive comments
• Bug reports
• Change requests

Addressing Different Types of Feedback

Bugs and Issues

Critical vs Non-Critical

Users might report technical issues (bugs) or other types of issues after UAT. Track and prioritize these issues based on severity:

• Critical issues (high priority): Problems that prevent core functionality (e.g., inability to access or download)
• Non-critical issues (lower priority): Cosmetic or minor concerns (e.g., feedback on visual elements)

Tracking Process:

1. Create a dedicated spreadsheet or tracking system
2. Document all reported issues
3. Assess severity of each issue
4. Prioritize fixes based on impact
5. Monitor resolution progress

Change Requests

Managing Changes

Users may suggest modifications to the product, service, or process after UAT. Handle these requests by:

1. Documenting all requested changes
2. Evaluating impact and feasibility
3. Prioritizing based on value and effort
4. Communicating with stakeholders
5. Adjusting project timeline if needed

Best Practices for UAT Feedback Management

Key Recommendations

• Maintain clear communication channels with users
• Document all feedback systematically
• Establish a clear process for evaluating and prioritizing issues
• Keep stakeholders informed of significant changes
• Plan for timeline adjustments when implementing major changes
• Create a feedback loop to verify fixes

Quality Management Concepts

Core Quality Components

Key Elements

Quality management consists of several essential components:

1. Quality Standards
2. Quality Planning
3. Quality Assurance (QA)
4. Quality Control (QC)

Quality Standards

Standards provide requirements, specifications, or guidelines ensuring that products, processes, or services are fit for achieving desired outcomes. These must be met for project success and should be:

• Clearly defined at project start
• Agreed upon by team and stakeholders
• Measurable and verifiable
• Aligned with organizational goals

Quality Planning

Planning Process

Quality planning involves:

• Identifying relevant quality standards
• Determining how to satisfy these standards
• Creating procedures for quality achievement
• Documenting the quality management approach

Quality Assurance (QA)

QA is an ongoing evaluation process that:

• Reviews project progress toward quality goals
• Includes regular audits
• Ensures procedures are being followed
• Focuses on preventing defects before they occur
• Validates alignment with customer requirements

Quality Control (QC)

QC vs QA

While QA prevents defects, QC focuses on identifying defects after they occur. Quality Control:

• Monitors specific project results
• Determines if they meet quality standards
• Identifies defects after they happen
• Recommends corrective actions
• Validates fixes and improvements

Process Improvement Methodologies

DMAIC Methodology

Definition

DMAIC is a data-driven improvement cycle used to enhance, stabilize, and optimize business processes. It serves as the core tool for driving Six Sigma projects.

The Five Phases of DMAIC

1. Define

   • Identify the problem and improvement needs
   • Set clear, specific goals
   • Document project scope and boundaries
   • Establish stakeholder requirements

2. Measure

   • Quantify the identified issues
   • Gather baseline performance data
   • Validate measurement systems
   • Determine current process capability

3. Analyze

   • Determine root causes
   • Identify key process variables
   • Validate cause-and-effect relationships
   • Prioritize improvement opportunities

4. Improve

   • Develop potential solutions
   • Test and validate improvements
   • Implement change management
   • Document new procedures

5. Control

   • Monitor implemented changes
   • Ensure sustained improvements
   • Standardize successful changes
   • Document lessons learned

PDCA Cycle

Overview

The Plan-Do-Check-Act (PDCA) cycle is a fundamental model for continuous improvement, forming the foundation of Total Quality Management (TQM) and ISO 9001 standards.

Four Stages of PDCA

1. Plan

Planning Phase

• Analyze current inefficiencies
• Identify needs for change
• Assess implementation methods
• Evaluate costs and benefits
• Set clear objectives

2. Do

Implementation Phase

• Execute planned improvements
• Communicate changes clearly
• Manage resistance
• Document progress
• Collect data

3. Check

Evaluation Phase

• Compare results to expectations
• Measure effectiveness
• Identify any gaps
• Document findings
• Gather feedback

4. Act

Action Phase

• Standardize successful changes
• Address any shortcomings
• Plan next improvements
• Share lessons learned
• Update documentation

Quality Management Implementation

Best Practices for Quality Management

Key Success Factors

1. Leadership commitment
2. Employee involvement
3. Process approach
4. Continuous improvement
5. Evidence-based decision making
6. Customer focus

Quality Tools and Techniques

Documentation

• Quality Management Plan
• Process Documentation
• Standard Operating Procedures
• Quality Metrics Dashboard
• Audit Reports

Measurement Tools

• Control Charts
• Pareto Analysis
• Cause-and-Effect Diagrams
• Check Sheets
• Histograms

Quality Review Process

Review Components

1. Regular quality audits
2. Performance metrics tracking
3. Customer feedback analysis
4. Process compliance checks
5. Improvement opportunity identification

Continuous Improvement Cycle

Ongoing Process

The continuous improvement cycle involves:

• Regular assessment of processes
• Identification of improvement opportunities
• Implementation of changes
• Measurement of results
• Standardization of successful changes

Quality Management Integration

Alignment with Project Management

Integration Points

Quality management should be integrated with:

• Project planning
• Risk management
• Change control
• Stakeholder communication
• Resource allocation

Stakeholder Involvement

Engagement Strategies

• Regular quality status updates
• Involvement in quality reviews
• Feedback collection and analysis
• Clear communication of quality metrics
• Collaborative problem-solving

Documentation and Reporting

Key Documents

Maintain comprehensive documentation of:

• Quality standards and requirements
• Process documentation
• Quality metrics and KPIs
• Audit findings and actions
• Improvement initiatives
• Lessons learned

---

Навигация

• Назад: Как написать эффективное эскалационное письмо
• Наверх: Шпаргалка по управлению проектами (Project Management)
• Далее: Манифест Agile (Agile Manifesto)