<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">
  <url>
    <loc>https://www.qualitysage.com/home</loc>
    <changefreq>daily</changefreq>
    <priority>1.0</priority>
    <lastmod>2021-06-15</lastmod>
    <image:image>
      <image:loc>https://static1.squarespace.com/static/5f31fc4d711de26f352b79c6/t/5ff380d9461d8d43a33c97ea/1609794906268/IMG_0848.jpg</image:loc>
      <image:title>Home - For those seeking Software and Design Quality -</image:title>
      <image:caption>QSAGE Understanding the nature of quality</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://static1.squarespace.com/static/5f31fc4d711de26f352b79c6/t/5ff38b3a289de731b31f8182/1609796437474/EdieHovermale.jpg</image:loc>
      <image:title>Home</image:title>
    </image:image>
    <image:image>
      <image:loc>https://static1.squarespace.com/static/5f31fc4d711de26f352b79c6/t/5ff4b054dd74b20cfa5c6f8a/1618279603135/Screen+Shot+2021-01-05+at+9.52.44+AM.png</image:loc>
      <image:title>Home - Implement Controls and Best Practices for Quality Software</image:title>
      <image:caption>Quality comes from all supporting systems not just testing. Your quality strategy is a team effort and should be part of the development, testing, deployed environments, and customer engagements. Quality efforts can be compared to a smooth running car, if one mechanism is not running well it will effect the whole ride. Working together to identify, implement and refine best practices and controlled systems can create a well run, repeatable, quality release.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://static1.squarespace.com/static/5f31fc4d711de26f352b79c6/t/605a3b3b231d5550115503ab/1618279603142/TestMandala.jpg</image:loc>
      <image:title>Home - Goal of Testing - FIND AND FIX DEFECTS EARLY</image:title>
      <image:caption>The goal of testing is to find defects and to fix them early. Working towards implementing ‘defect finding structures and activities’ supports the quality efforts. These structures and activites include: Understanding product domain and goals Identifying tests Identifying weak areas and prioritizing areas of risk Ensuring test types are considered Assessing usability &amp; user experience and being a customer advocate Identifying and understanding code dependencies Implementing a test repository Creating and maintaining test data Automating regression tests Execute tests early and often Reviewing code Understanding code changes Controling test environments Cleary reporting defects</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://static1.squarespace.com/static/5f31fc4d711de26f352b79c6/t/60c832a4bb2ff30fb882265a/1623732927082/FMEA.jpg</image:loc>
      <image:title>Home - Failure Mode and Effects Analysis - FMEA</image:title>
      <image:caption>FMEAs help us identify, understand and focus on the impact of potential risks for: Systems Designs Processes Services Software Manufacturing An FMEA results in a prioritized list of risks, effects and controls. If a risk calculation is too high a mitigation action should be taken and the risk reassessed. The FMEA is a living document that should be updated and re-evaluated with each design / process change. An FMEA is used as the basis for Control Plans which is a summary of proactive defect prevention, reactive detection techniques, and a well-thought out Reaction Plan if a failure does occur. The FMEA, Control Plans, and Reaction Plan should be well understood by the cross functional team for a fast reaction if a failure occurs.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://static1.squarespace.com/static/5f31fc4d711de26f352b79c6/t/6075237bc3fb50429d4ed031/1618289540660/iso13485.jpg</image:loc>
      <image:title>Home - ISO 13485:2016</image:title>
      <image:caption>ISO 13485:2016 is an international standard used by organizations of all sizes involved in one or more stages of the life-cycle of a medical device, related services and associated activities. ISO 13485:2016 specifies requirements for a quality management system where an organization demonstrates its ability to meet customer and applicable regulatory requirements. The processes required by the standard are the responsibility of the organization whether or not the organization performs the processes and are accounted for in the organization's quality management system by monitoring, maintaining, and controlling the processes. Regulatory requirements allow for exclusions of design and development controls, if these exclusions can be justification from the quality management system through alternative approaches and/or documentation. The quality management system guides the organization in achieving quality objectives, continuous improvement, and customer satisfaction by including elements such as objectives, document management processes, and data management policies.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://www.qualitysage.com/about</loc>
    <changefreq>daily</changefreq>
    <priority>0.75</priority>
    <lastmod>2021-01-05</lastmod>
    <image:image>
      <image:loc>https://static1.squarespace.com/static/5f31fc4d711de26f352b79c6/t/5ff4c127af41aa3cf58a97ed/1609875773001/IMG_0873.jpg</image:loc>
      <image:title>About - QSAGE is an idea, a way of working, a philosopy.</image:title>
      <image:caption>I want to share my experiences with others to help them grow into top software quality engineers and to help companies gain a quality mindset to create the best quality software. Coming back to the basics even in times of fast paced product releases, grounds the team to be able to feel confident in their software. Edie</image:caption>
    </image:image>
  </url>
</urlset>

