<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ivana Rajora on Medium]]></title>
        <description><![CDATA[Stories by Ivana Rajora on Medium]]></description>
        <link>https://medium.com/@ivana.rajora?source=rss-f3927a60724c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7uY65kXLxdnQOpHea8kdsg.jpeg</url>
            <title>Stories by Ivana Rajora on Medium</title>
            <link>https://medium.com/@ivana.rajora?source=rss-f3927a60724c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:53:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ivana.rajora/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Culture of Quality]]></title>
            <link>https://medium.com/undabot/culture-of-quality-342f19794cd1?source=rss-f3927a60724c------2</link>
            <guid isPermaLink="false">https://medium.com/p/342f19794cd1</guid>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[quality]]></category>
            <dc:creator><![CDATA[Ivana Rajora]]></dc:creator>
            <pubDate>Wed, 30 Jun 2021 10:11:16 GMT</pubDate>
            <atom:updated>2021-06-30T10:11:16.710Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>What is it and how to get it?</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*loY_e-QqUpErnjq54U9Akg.png" /></figure><h3>Culture, Quality and Culture of Quality</h3><p>To understand what the Culture of quality represents, let’s break it down into two terms: <em>Quality</em> and <em>Company culture</em> and try to define them first. Then, let’s see how they again fit together and form the <em>Culture of quality</em>.</p><p><strong>Quality</strong> is a term not easily definable and mostly based on perspective, since it applies to everything around us. If we take, for instance, the quality of products and/or services in industries like manufacturing and engineering, we can say that Quality is what makes those products/services ‘fit for purpose’, while at the same time satisfying customer/client/end-user expectations. ISO 9000 also defines Quality as the “degree to which a set of inherent characteristics of an object fulfills requirements”.</p><p><strong>Company culture</strong> can be defined as a “set of shared values, goals, attitudes and practices that characterise an organisation”. We could say it represents the personality of an organisation — all the traits that make your company what it is: ways how employees feel about the work they do, how they interact with others, values they believe in, the decisions they make every day, where they see the company going, and so much more.</p><p>All of those traits collected in an organisation’s culture have a huge influence on the quality produced by the organisation. That is why we strive to instil quality in the company’s culture and create a Culture of Quality.</p><p><strong>Quality Culture</strong> (or Culture of Quality) can be defined as “the opinions, beliefs, traditions and practices concerning quality”. It represents the environment in which the employees follow guidelines, take quality-focused actions, talk about quality, but also see other employees do the same thing. Culture of Quality is also an environment where everyone can feel the quality all around them.</p><h3>The benefits of having a culture of quality</h3><p>So, now that we know how to recognise the culture of quality, let’s look at all the good things that can come out of having the culture of quality in your company.</p><p>Companies that focus on Quality and manage it effectively:</p><ul><li>have lower costs, since quality generates savings (mostly through less reworks needed late in the process), which boosts their profits;</li><li>their brand and reputation enhance;</li><li>their efficiency increases;</li><li>are more successful;</li><li>are more protected against risks;</li><li>survive and thrive (keep on growing).</li></ul><p>Employees that go above and beyond regarding quality and understand its importance:</p><ul><li>are more productive and innovative;</li><li>make fewer mistakes (and, accordingly, their companies spend far less time and money correcting mistakes);</li><li>are more engaged;</li><li>better understand their roles (resulting in fewer issues, less wastage and lower costs);</li><li>are more proactive;</li><li>are happier.</li></ul><p>Companies that make sure their stakeholders’ needs are met and their expectations exceeded:</p><ul><li>receive fewer complaints;</li><li>instil customer with confidence and loyalty;</li><li>make customers happier;</li><li>get higher customer satisfaction;</li><li>achieve customer delight;</li><li>provide better customer experiences;</li><li>get more referrals and higher customer lifetime value.</li></ul><h3>Ways to create a culture of quality</h3><p>After seeing what good comes out of implementing the culture of quality, another question is presenting itself — What should we do to get all these benefits? How and where to start with the culture of quality implementation?</p><p>There is no strict path to follow to create a culture of quality in your organisation. Each organisation is different and will require different tools and techniques. But all of the companies would have the same first step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EeAPzOGmtN0Ws_5kIflXIA.png" /></figure><p><strong>Evaluate your current company culture</strong></p><p>First, through evaluation, define and outline company values. Once you and your company see where you stand with your current culture, you are ready to start the process of improving it by embedding the quality in it.</p><p>Look at your evaluation with Quality in mind and see if those values speak quality. That will give you a rough idea of what parts you should be focusing on the most.</p><p>According to the Quality Magazine: <em>“Companies that have achieved the true culture of quality, demonstrate three common traits: leadership commitment, employee ownership, and organisation-wide continuous improvement”.</em></p><p><em>Some of the most important parts of this process of developing a culture that fosters quality are mentioned below and directly feed in the values mentioned above. Each company, during their journey, should decide the way they would implement any of those steps and where their focus will lie, depending on their current culture, their organisation, employees and the work they do.</em></p><p><strong>Involve Senior Management</strong></p><p>One of the most important aspects of creating a culture of quality is getting everyone involved. That does not just include senior management, but makes them the first ones to get involved. If the top of the company is advocating quality, it is more likely that the employees will follow and take this quality journey seriously.</p><p>The entire company must embrace a quality mindset in everything they do, including cross-department interactions. This is easiest to accomplish if starting from the top because that gives it credibility and a push for everyone to commit to it.</p><p><strong>Involve your customers / end-users</strong></p><p>As we mentioned at the start, Customers play a big role in defining quality. So, don’t ignore their feedback, but rather use it to improve your culture of quality.</p><p>Since everything you are doing should be about the needs and expectations of customers and end-users, ask them what their wants and needs are. The easiest way to do that is by using customer experience surveys and asking direct questions often. But also, pay attention during any kind of feedback — meetings, UAT testing, emails, etc.</p><p><strong>Make your processes well-defined and easy to comprehend</strong></p><p>Well-defined processes in the company show all the employees how to carry out their assignments and it makes the work uniform across different teams. If employees understand the activities that make a process and all of it is very well documented, it is much easier to implement it in everyone’s daily routine. That way the employees perform their work without having to be reminded to follow the process guidelines.</p><p>For a process to become routine, employees have to be educated on the use of the process and trained in the use of the tools that will help them in their work.</p><p>Processes that should follow this are not just development and QA, but rather all the processes in the company. Each process defines the minimum set of activities mandated for each project executed in the organisation, making the QA process focus on QA activities and other processes focus on their tasks at hand.</p><p><strong>Create QA department, if you don’t have one</strong></p><p>No single tool, test or person can guarantee quality. That also means that the culture of quality is not achievable by a QA team alone. Having a dedicated team or a department will take you closer to it, because your QA department should champion quality within the organisation.</p><p>That means they will be:</p><ul><li>providing counsel and guidance on quality matters;</li><li>monitoring quality achievements;</li><li>evaluating and obtaining tools that will improve productivity and quality.</li></ul><p>If you already have an existing QA department that focuses only on uncovering defects, that is a good start, because their knowledge will be improving quality. But you should still work on modifying their responsibilities to include the ones mentioned above, since that will make a big difference in achieving the required level of quality and helping other employees play their part in it.</p><p>Additional change you should do regarding your QA department is making them champions of organizational process initiatives. Since their job is to make organisations better at producing outputs that meet the needs and expectations of the stakeholders, there is no one better to advocate for those initiatives.</p><p><em>Also, remember that your QA department should be of the same importance as any other department.</em></p><p><strong>Train employees in quality culture</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nWKOLD5SxdHp4qML3kaM4A.png" /></figure><p>Employees need to be involved in the culture of quality in a way that they understand what they should do, how, and also most importantly why. The culture of quality is not made by simply following the rules, but by training everyone to think about quality, own it, care about it and act upon it.</p><p>Embedding quality in the company means involving everyone (not just developers and testers) and teaching them what their responsibilities are, what the idea behind the culture change is and what the plan for the future is.</p><p>One other aspect of training employees is asking for feedback. Given the opportunity, employees will adopt a quality mindset if they see their input is valued and their decisions impact the overall work and the company.</p><p>In addition to the QA team training other employees in quality (process, tools, activities) and management influencing cultural values, teamwork should be encouraged, as well as employees learning from one another.</p><p><strong>Create a reward system for achieving excellence in quality</strong></p><p>This will be different in any company, depending on their capabilities and wishes, but it is important because it has a great impact on employee performance and motivation.</p><p>A reward system can include monetary rewards and recognition or praise. The system should define goals and actions so that employees know what is expected from them to receive the rewards/recognition. That way, when the goals are achieved or actions completed, they get the rewards or recognition immediately. Remember, the time aspect of the recognition is very important — “delayed recognition is as good as denied recognition”.</p><p><em>If quality is an important issue for a company, the reward system that they design should not emphasize rewarding the quantity of work accomplished by a business unit.</em></p><h3>Maintenance — once you have it, don’t lose it</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XNJNS0usJqag1HSKH3bsew.png" /></figure><p>Once you and your company go through this long process of developing such a culture, don’t forget about it, but rather work on maintaining it.</p><p>Don’t forget to include everyone in this part of the process as well. Everyone should support the maintenance and contribute to it.</p><p>The best way to do that is to not stand still and continually drive the improvement effort.</p><p>So, how to do that? Well, here are some actions you can take:</p><ul><li>introduce quality metrics and use them to re-evaluate processes and behaviours;</li><li>maintain open and honest communication, ask your employees for feedback and suggestions and use collected information to work towards improvements;</li><li>work on promoting quality and other desired values (through improving accountability, clarifying goals and responsibilities, providing training and support, mentoring, rewarding good performance, engaging employees etc.).</li></ul><p>And at the end, do not forget:</p><blockquote><strong>Quality is everyone’s responsibility.</strong></blockquote><p><em>(W. Edwards Deming, Father of the Quality)</em></p><p><strong>Thank you for reading and a big thanks to </strong><a href="https://hr.linkedin.com/in/anchii"><strong>Ana Šeler</strong></a><strong> for the design!</strong></p><p><strong>Would you like to join Undabot? Check out the open positions on our </strong><a href="https://careers.smartrecruiters.com/undabot"><strong>Careers page.</strong></a><strong><br>Stay up to date with Undabot news by </strong><a href="https://email.undabot.com/x/plugin/?pName=subscribe&amp;MIDRID=S7Y1BAAA38&amp;pLang=en&amp;Z=-691325057"><strong>subscribing to our monthly newsletter</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=342f19794cd1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/undabot/culture-of-quality-342f19794cd1">Culture of Quality</a> was originally published in <a href="https://medium.com/undabot">Undabot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[QA vs. QC vs. Testing — What’s the difference?]]></title>
            <link>https://medium.com/undabot/qa-vs-qc-vs-testing-whats-the-difference-12131b7c427c?source=rss-f3927a60724c------2</link>
            <guid isPermaLink="false">https://medium.com/p/12131b7c427c</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[quality-control]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[customer-satisfaction]]></category>
            <category><![CDATA[quality-software]]></category>
            <dc:creator><![CDATA[Ivana Rajora]]></dc:creator>
            <pubDate>Mon, 07 Dec 2020 14:24:03 GMT</pubDate>
            <atom:updated>2020-12-07T14:37:44.838Z</atom:updated>
            <content:encoded><![CDATA[<h3>QA vs. QC vs. Testing — What’s the difference?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ljUcbpv3nSSB_4py6-50ww.png" /></figure><p>Quality product delivery is the goal for every company, so naturally there is a lot of talk about quality assurance, quality control and software testing. Most people think these terms represent the same thing. More precisely, they think that quality assurance and quality control are equivalent to testing, which we would define as exploring the software in order to find bugs.</p><p>Even though to a small extent this can be correct (in a way that they have the same objective), there is a lot more to it. All the mentioned terms are connected to each other and they actually build on top of each other.</p><p>In simple terms, Software Testing is a part of Quality Control, and Quality Control is a part of Quality Assurance. So, is it correct to say all of it represents the same thing? No, because Quality Control is more than just testing, just as Quality Assurance is much more than just Quality Control.</p><p>Let us explore some definitions and explanations on each of them so that we can see the differences and similarities and decide if only one of them is enough to provide a quality product.</p><p><strong>Testing</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5deNt39T-5CuHkP6kyjyqw.png" /></figure><p>Testing is one of the most important parts of quality assurance and the most known and executed QA activity.</p><p>As per ISTQB, testing is “the process consisting of all life cycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.”</p><p>Basically, testing is a process focused on finding bugs, but also involving the execution of tests.</p><p>There are different testing types that are performed in order to find as many bugs as possible and execute as many different tests as possible in a definite time period defined by the project timeline, in order to cover all aspects of the software under test. Some of those types include:</p><ul><li>Functional testing,</li><li>Performance testing,</li><li>Security testing,</li><li>Database testing,</li><li>API testing,</li><li>Usability testing,</li><li>Accessibility testing</li></ul><p>Tester performs testing manually or automatically (using different automation tools), depending on many factors, including, but not limited to size of the project, complexity of the project, available resources, etc.</p><p>Testing helps to measure the quality of software and is interested in the improvement of the quality. We can say that finding and fixing bugs increases quality and if fewer bugs are found, it gives more confidence in said quality.</p><p><strong>Quality Control</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RccreKw0SJH9PGX0RP9ZJg.png" /></figure><p>Quality control (QC) is defined as “a set of activities whose purpose is to ensure that all requirements are met in the final product”.</p><p>In order to control quality, we have to measure it and compare it with standards. We do that by using software quality metrics.</p><p>Also, in order to determine the level of the quality delivered by the final product, we use different quality control activities. Those are deliverable peer reviews (where deliverables are Requirements, Design, Code, Deployment, Test Plan, Test Cases) and testing.</p><p>Quality control focuses on the quality of the software by:</p><ul><li>Adopting and implementing activities mentioned above (which include testing);</li><li>Ensuring that all the processes, procedures, etc. designed by Quality assurance are followed correctly;</li><li>Making sure that the deliverables are defect free, acceptable and based on the quality requirements.</li></ul><p><strong>Quality Assurance</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lM5SHj1F-DcNfc1G7lDA9A.png" /></figure><p>Quality Assurance (QA) is “a set of activities for ensuring quality in software engineering processes that ultimately results, or at least gives confidence, in the quality of software products.”</p><p>Those Quality Assurance activities are: Process definition, Process training, Process implementation and Process audit.</p><p>Quality assurance focuses on designing processes, procedures, standards, methodologies and making sure they are implemented correctly and continuously improved. Resources, processes and procedures keep the organization focused on goals.</p><p>In practice, Quality Assurance is usually in charge of:</p><ul><li>Creating Test Strategy;</li><li>Creating Templates for test documentation (test plans, test cases and bug reports);</li><li>Defining Quality metrics;</li><li>Identifying testing risks and controls;</li><li>Choosing and implementing tools to be used as a support for testing;</li><li>Creating guidelines to be followed for different testing types.</li></ul><p>Quality Assurance is done throughout the software development process using set resources and processes to help guide the development process in the right direction. In different phases of the process, quality control activities are also performed as a part of Quality Assurance.</p><p>The goal of quality assurance is to prevent defects, help ensure consistency across different projects in the organisation and to satisfy the customers. Except reaching the goal, QA includes additional advantages like cost reduction (less reworking since guidelines are followed), improvement of employee motivation (more ownership regarding processes is given to the employees), better communication (peer reviews remove some of the hierarchy). Quality Assurance also empowers employees to give feedback and care about quality.</p><p><strong>Conclusion</strong></p><p>Customer satisfaction is the goal of every company and a way to reach it is through the delivery of a quality product. Quality can be reached only through a combination of proactive and reactive process and introducing QA team into the company ensures exactly that. Quality Assurance team uses procedures and methodologies to prevent defects (QA) and implements procedures during testing in order to discover defects (QC).</p><p>QA includes QC, but it is also dependent on it because good QA uses QC inputs to correct implemented procedures.</p><p>Without one of them, we are missing a key ingredient to build Quality as a company’s core value. Use your Quality Assurance team as a stepping stone to promote an approach where “Quality is everyone’s responsibility”.</p><p><strong>Thank you for reading and big thanks to </strong><a href="https://www.linkedin.com/in/antonijabutkovic"><strong>Antonija Butković</strong></a><strong> for the illustrations!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12131b7c427c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/undabot/qa-vs-qc-vs-testing-whats-the-difference-12131b7c427c">QA vs. QC vs. Testing — What’s the difference?</a> was originally published in <a href="https://medium.com/undabot">Undabot</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>