Please enable JavaScript.
Coggle requires JavaScript to display documents.
Unit 3: Constructive Quality Management - Coggle Diagram
Unit 3: Constructive Quality Management
Constructive Quality Management
Example:
• Sample document for a quality management plan with a predefined outline and instructions for completion that ensures that all important points are covered.
• Establishing programming guidelines that require, among other things, the naming of variables and making unit tests mandatory for every business function in the program code.
Activities:
Specifications for the project eliminate errors symptoms and remove cause of error
(Root cause analysis)
Define measures
monitor compliance
check effectiveness and adjust if needed
Root cause analysis techniques
Steps of root cause analysus
Step 1: Collection of all available information about the error and the erroneous behavior triggered by the error.
Step 2: Application of the 5–Why method.
Step 3: Identification of the places in the program code that must be changed to eliminate the error.
Step 4: Identification of possible QA measures (constructive and analytical) to prevent the error in the future.
Step 5: Introduction of the QA measures.
Step 6: Evaluation of the QA measures to determine whether they reliably prevented the errors.
5 Why method
“Ask ‘why’ five times about every matter.”
Timeboxing technique
Fixed timeframe for activities and procedures within project
Agile software dev, tool for meetings
Checklists technique
Ensure no required activities are forgotten
For recurring standard tasks (training new employee, setting up a dev environment, examining current step at quality gate)
Important when formulating checklists:
• One item on the checklist corresponds to exactly one objective; compound objectives should be avoided and divided among several items.
• Clear and simple wording of the checkpoints increases readability and understandability. A checklist should not be larger than an A4 sheet of paper so it can be easily printed out with any printer and all the checkpoints can be understood at a glance.
• The criteria required to fulfill a checkpoint must be transparent; if necessary, sub-checkpoints or separate checklists are created for individual checkpoints.
• Continuous monitoring
Measures for Constructive QM:
Prevent errors during design, operation, further development
Technical measures
Aspects related to specific software tech aspects in software process. Most important result artifact of software project - software system.
They include:
Methods
Techniques for completing tasks in a structures and systematic manner (ex: prioritization, user stories, etc)
Language
Language for programming logic (Java, C#, JavaScript, Python)
Programing language for specific components (JavaScript GUI, SQL DBs)
Modeling languages (UML, E/R diagrams, BMPN, ARIS, Data-flow diagram)
Tools
Dev environments (Netbeans, eclipse, Visual Studio)
Testing tools (JUnit, Selenium)
Frameworks
Pre-existing program code
Interpersonal measures
Qualifications
Development of personal and professional skills through training, coaching
Joint Activities
Team events, leisure activities
Design of working environment
Ex.: quiet zones for work
Kanban boards, etc
Organizational measures
- non-technical aspects that impact organization of work.
Они идут парой с measures of Consrtuctive QM
Organizational measures include:
Standards
Guidelines
ex. programming and behavior guidelines, conventions
scope for decision making
Timeboxing - guideline for organization of meetings
Checklists
Used for repeated standard tasks
briefing new employees, performing doc reviews, examining current process step at quality gates
Templates - generally company or project-specific templates for document structures and content (artifacts: requirements, specifications, documentation, source code)