Three original implementations of the quality assurance role in two different companies. How creative management can solve the problem of making QA be both a career path and a positive influence in the process improvement path.
Understanding the who, what, why, and when of quality is essential in implementing an effective Quality Program. It requires a combination of distinct disciplines: Quality Assurance, Quality Control, and Quality Improvement. They are three unique disciplines which, when used together, can improve the efficiency and effectiveness of any organization leading to reduced cost and increased customer satisfaction.
Understanding the who, what, why, and when of quality is essential in implementing an effective Quality Program. It requires a combination of distinct disciplines: Quality Assurance, Quality Control, and Quality Improvement. They are three unique disciplines which, when used together, can improve the efficiency and effectiveness of any organization leading to reduced cost and increased customer satisfaction.
=>Concept of Governance
=>Risk and Control (GRC) as applicable to IT operational risk
=>Importance of documentation
=>DATA FLOW DIAGRAM for every application
=>Review of changes in the Data flow, reporting, etc.
=>Parameters for review
=>Importance of review on SLA compliance
=>Reporting to IT Strategy committee, Board etc.
Product audits have been an indispensable tool in the automotive industry for evaluating and improving product quality in the interest of the customers for many years.
A Guide to the Forthcoming 2012 Revision of the IEEE Software Quality Assuran...dheimann5
The IEEE is in the process of updating and adding significant content to its IEEE-730-2002 standard on Software Quality Assurance (SQA). The new version will coordinate with the four process areas and sixteen SQA tasks in the IEEE-12207-2008 standard “Systems and Software Engineering: Software Life Cycle Processes”, providing detailed elaborations for these areas and tasks.
The presentation provides a brief overview of these areas and tasks, discuss the difference between SQA and testing, and cover the annexes in IEEE 730 that provide industry-specific information as well as the relationships with software process approaches such as CMMI, Agile, SPICE, CSQE, PMBOK, and VSEs.
White paper quality at the speed of digitalrajni singh
Our modern testing practices help speed up the current scope of quality assurance with help of a cognitive approach. Here is the link to download my published whitepaper on "Quality at the Speed of Digital" https://www.nagarro.com/qa-at-the-speed-of-digital #qualityassurance
Atlassian is unveiling a new dashboard that will be added to all of our products, based on the OpenSocial specification. This session explores Atlassian's use of OpenSocial, and details the new Atlassian dashboards and Gadgets.
Atlassian Speaker: Tim Moore
Key Takeaways:
* Overview of OpenSocial
* Deep-dive on Atlassian dashboards and Gadgets
* Demos, how-tos and more
Capybaras are the largest rodents in the world. They are related to guinea pigs, but are the size of a big dog or small pig. They live in South America, and they're pretty damn cute.
Capybara is also the name of a Ruby gem written by Jonas Nicklas. It helps you write integration tests for web apps by pretending to be a user with a web browser. It takes a black box approach to testing, letting you go to URLs, click links and buttons, fill in forms, and check that the rendered page contains what you think it should have in it.
This talk is about Embracing Capybara: how to understand Capybara, train it to do new tricks, and discipline it when it misbehaves.
=>Concept of Governance
=>Risk and Control (GRC) as applicable to IT operational risk
=>Importance of documentation
=>DATA FLOW DIAGRAM for every application
=>Review of changes in the Data flow, reporting, etc.
=>Parameters for review
=>Importance of review on SLA compliance
=>Reporting to IT Strategy committee, Board etc.
Product audits have been an indispensable tool in the automotive industry for evaluating and improving product quality in the interest of the customers for many years.
A Guide to the Forthcoming 2012 Revision of the IEEE Software Quality Assuran...dheimann5
The IEEE is in the process of updating and adding significant content to its IEEE-730-2002 standard on Software Quality Assurance (SQA). The new version will coordinate with the four process areas and sixteen SQA tasks in the IEEE-12207-2008 standard “Systems and Software Engineering: Software Life Cycle Processes”, providing detailed elaborations for these areas and tasks.
The presentation provides a brief overview of these areas and tasks, discuss the difference between SQA and testing, and cover the annexes in IEEE 730 that provide industry-specific information as well as the relationships with software process approaches such as CMMI, Agile, SPICE, CSQE, PMBOK, and VSEs.
White paper quality at the speed of digitalrajni singh
Our modern testing practices help speed up the current scope of quality assurance with help of a cognitive approach. Here is the link to download my published whitepaper on "Quality at the Speed of Digital" https://www.nagarro.com/qa-at-the-speed-of-digital #qualityassurance
Atlassian is unveiling a new dashboard that will be added to all of our products, based on the OpenSocial specification. This session explores Atlassian's use of OpenSocial, and details the new Atlassian dashboards and Gadgets.
Atlassian Speaker: Tim Moore
Key Takeaways:
* Overview of OpenSocial
* Deep-dive on Atlassian dashboards and Gadgets
* Demos, how-tos and more
Capybaras are the largest rodents in the world. They are related to guinea pigs, but are the size of a big dog or small pig. They live in South America, and they're pretty damn cute.
Capybara is also the name of a Ruby gem written by Jonas Nicklas. It helps you write integration tests for web apps by pretending to be a user with a web browser. It takes a black box approach to testing, letting you go to URLs, click links and buttons, fill in forms, and check that the rendered page contains what you think it should have in it.
This talk is about Embracing Capybara: how to understand Capybara, train it to do new tricks, and discipline it when it misbehaves.
CMMI (Capability Maturity Model Integration) is a proven industry framework to improve product quality and development efficiency for both hardware and software
Software organizations that want to maximize the yield of Software Testing find that choosing the right testing strategy is hard, and most testing managers are ill-prepared for this. The organization has to learn how to plan testing efforts based on the characteristics of each project and the many ways the software product is to be used. This tutorial is intended for Software professionals who are likely to be responsible for defining the strategy and planning of the testing effort and managing it through its life cycle. These roles are usually Testing Managers or Project Managers.
Whereas QA is the overall process of ensuring manufacturers make things properly, Quality Engineering (QE) defines (or ‘engineers’) the system that does it. Quality engineers maintain, improve, and monitor the system.
A big part of process improvement is managing the transition. Many books have been written about how to do this, yet there is a paucity of strategies that can be tied to real life variables. In this Appendix to our book (in translation from Spanish) we explore such strategies and suggest a parsimonious approach whenever possible.
MPS and Agile Methods references in englishJorge Boria
The references for the whole Tahini-Tahini story. So far the Prologue, and Chapters 1 and 2 have been uploaded. You can write me for versions in Spanish and Portuguese.
This is the second chapter of the authors' own translation of the award winning book The Story of Tahini-Tahini: Process Improvement and Agile Methods with the MPS Model. Originally published in Portuguese and already in Spanish. This Chapter deals with Process Improvement and how to make it work.
From Lust to Dust: A Product Life CycleJorge Boria
Traditional software engineering deals with two phases of a product lifecycle: Development and Maintenance. In this short paper we propose to take a different approach and look at the product’s lifecycle using an analogy with the human lifecycle. We use this analogy to define roles that we call ‘research’, ‘engineering’, and ‘support’ to accommodate all the required activities that will keep a product useful for the longest period possible, while at the same time giving rapid response to customer needs.
Small organizations have very limited resources. This implies that traditional approaches to SPI will probably sink before they succeed for lack of sustaining funding. This white paper shows a proven approach to institutionalizing a managed behavior and beyond, by effecting small incremental changes that are easy to install individually but that collectively achieve most of the required specific practices at ML2. The presentation addresses a niche audience that usually has great difficulty in finding applicable processes and experiences that match their needs. In particular, small organizations, or process engineers working with small organizations; but also, organizations that cultivate individual dissonance in opposition to synchronicity or democratic decisions can benefit from it.
La última entrega de mi serie sobre el CMMI SVC. Como en la anterior, me enfoco en una de las dos áreas de gestión de trabajo que son exclusivas del modelo SVC, en este caso continuidad de servicios (SCON)
This is the second upload of the book "The Story of Tahini-Tahini: Software Process Improvement with Agile Methods and Maturity Models". We are seeking help to find mistakes and perfect the book.
The Story of Tahini-Tahini: Software Process Improvement with Agile Methods a...Jorge Boria
This is the first part of the book "The Story of Tahini-Tahini: Software Process Improvement with Agile Methods and Maturity Models" that we are crowd reviewing. Please review and send us comments to improve its quality. Thanks.
Versión final del libro "Mejora de Procesos de Software con Métodos Ágiles y Modelo de Madurez MPS: La Historia de Tahini-Tahini" Para una versión Kindle o en papel, recurrir a Amazon.com.
This is a mock up appraisal of an imaginary oilfield services organization, performed against the CMMI SVC practices. It is based on my own experience as a certified high maturity lead appraiser of the CMMI DEV and SVC constellations and a past experience in one of the world's leaders in consulting with a specialty in oilfield services. The article is meant to illuminate how the practices are pertinent in that particular industry. It was developed a few years ago as part of the requisites to become certified for SVC by (then) the SEI.
Although Causal Analysis and Resolution (CAR) is staged at Level 5 of the CMMI, it is a useful compendium of good practices for a company that starts its process improvement road. This mapping is designed to help organizations perform CAR at all levels. Borrowing from the defunct "advanced practices" paradigm, it describes what the practice would be like at different levels of capability within the process area. For example, almost all practices are described for capability level 1, thus providing guidance on how to start preventing defects from recurring.
Effectiveness of Organizational TrainingJorge Boria
The request to measure effectiveness of the training performed at an organization is not met by the "beauty contest" survey taken at the end of an activity. Moreover, since 85% of knowledge acquired by adults is lost in two weeks unless used, as reported by Jane Tippett in Nurses’ acquisition and retention of knowledge after trauma training, it is of fundamental importance that the gauge corresponds to the needs. In this presentation we describe a low tech yet highly effective method for measuring the improvement in productivity gained by training attendees. The method, used since last century in a large telecom organization, is based on some premises: training is only useful if aligned with job outcomes; training should be timely and not carried out solely for consuming the training budget; training objectives should be described as learning objectives, that is to say, what behavioral changes the training is attempting to achieve; managers are responsible for the skills and competencies of their employees.
An introduction to the latest addition to the CMMI constellations of the SEI. This material reflects the model as it was in July 2011. Since the SEI can and will introduce changes to the model, this material could be dated when you access it. Treat it as a simplistic view of the true content and DO find the current status from the right source: The SEI itself.
1. Webinar: QA Three Best Practices March 11, 2009 3:30 PM – 5:00 PM
2. Jorge Luis Boria Sr. VP International Process Improvement Liveware Inc. [email_address] Michael Milutis Director of Marketing Computer Aid, Inc. (CAI) [email_address]
3. About Presenter’s Firm LIVEWARE is a business consultant company in the field of Software Engineering. Since its creation in 1983 it has specialized in the dissemination, application and development of Software Engineering, particularly the concepts of Total Quality and the strategic value of Information Systems. In the past five years it developed a tight relationship with the Software Engineering Institute and is currently the sponsor of five lead appraisers, two certified high maturity lead appraisers, and two CMMI instructors.
9. QA vs Testing Structural Verification Integration and System Functional Verification Validation (User Acceptance) Component Functional Verification Non-functional Verification TESTING VALIDATE VERIFY BUILD Coding Requirements High Level Design Component Design Specification QA
10.
11.
12.
13.
14.
15.
16. Context - 3 UAT Execution (SDS) Test Report Sys Test Execution (SDS) Test Report Acceptance UAT Test Planning and Preparation System Test Planning and Preparation Unit Test Planning and Preparation Acceptance Requirements (SDS) Acceptance Specifications (TSD) Coding (SDS) Unit Test Execution (SDS) Hand Off Developed Components (SDS)`
17.
18. Context - 3 UAT Execution (SDS) Test Report Sys Test Execution (SDS) Test Report Acceptance UAT Test Planning and Preparation System Test Planning and Preparation Unit Test Planning and Preparation Acceptance Requirements (SDS) Acceptance Specifications (TSD) Coding (SDS) Unit Test Execution (SDS) Hand Off Developed Components (SDS)` Phase End Review Phase End Review Post Mortem Project Review Peer Review Peer Review
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29. Texas 3 Step overall project execution selected milestones when to perform QA audits and reviews prep (all involved) repetitive (specialist) audit (all QA)
47. Jorge Luis Boria Sr. VP International Process Improvement Liveware Inc. [email_address] Michael Milutis Director of Marketing Computer Aid, Inc. (CAI) [email_address]
Editor's Notes
The purpose of this webinar is to discuss issues that impact the effectiveness of IT organizations. Our discussion will be limited to IT Service Delivery (problem resolution, consultation requests, enhancements and projects). We will not be addressing Infrastructure or Operations Management issues.
Entry-Level Critical Work Functions Ensure materials, processes and final product meet quality specifications. Support and maintain quality systems. Comply with local, federal and company health, safety and environmental regulations. Identify unsafe conditions and take corrective actions. Entry-Level Technical Content Areas Quality Assurance Meeting Customer Needs Lean Manufacturing Quality Management Systems and Tools Industry Standards Improving Quality Introduction to Statistical Process Control Sampling and Charting Problem Solving Tools Inspecting for Quality Inspecting Raw/Incoming Materials Inspecting In-Process Product Inspecting Final Products Continuous Improvement Business Process Reengineering Systems Analysis Data Analysis Performance improvement strategies Technician-Level Critical Work Functions Monitor production for product and process quality Employ audits and inspections to maintain the quality and continuous improvement process Correct the product and process to meet quality standards Suggest and/or implement continuous improvement actions Technician-Level Technical Content Areas Probability and Statistics Data Analysis and Presentation Presentation Skills Query-Based Intermediate Computer Skills Facilitation Skills Business Case Statistical Process Control Methods Factor Analysis Capability Analysis- Inspection/Test/Validation Reliability Analysis Acceptance Sampling Quality Assurance Audits ISO 9000 Audit Procedures Corrective and Preventive Actions Eliminating Non-Conformities Verification and Documentation Documentation Creation Benchmarking and Best Practice
Fix what hasn’t been working: Academic approach: Literal Interpretation: Infrastructure: Management Visibility: Process Changes: Fragmented Improvements: Build on things that Do work: Project management process: Significant effort in this area over the last 5 years. L2 discipline evident in recent mini-assessments.
Fix what hasn’t been working: Academic approach: Literal Interpretation: Infrastructure: Management Visibility: Process Changes: Fragmented Improvements: Build on things that Do work: Project management process: Significant effort in this area over the last 5 years. L2 discipline evident in recent mini-assessments.