--- source_url: "https://www.scnsoft.com/software-development/about/how-we-work/quality-management" title: Quality Management at ScienceSoft mirrored_at: 2026-08-15T01:03:25.126Z host: www.scnsoft.com cited_in_42a: true mirror_canonical: "https://index.42a.ai/www.scnsoft.com/software-development/about/how-we-work/quality-management" --- > **Original source:** https://www.scnsoft.com/software-development/about/how-we-work/quality-management ## Quality is Only Real When Measured: KPIs We Use For each client, we devise a **tailored** set of quantitative KPIs, ranked according to their weight for project health and impact on customer goals. We use the KPIs to assess and **continuously improve** the success of cooperation and the quality of the software we deliver. ### Development process quality KPIs Here are some of the metrics we employ in our projects. The actual set depends on the specifics of the development approach and is defined individually for each client. [image] Time - _Actual time spent vs. planned time_ (total and across particular tasks). - _Lead time and cycle time, team velocity, deployment frequency, throughput_ — show trends behind the speed and amount of work an Agile development team completes per iteration. [image] Cost - _Budget vs. actual costs_ — a general KPI for project health measurement. - _Discovery cost estimates vs. refined budget._ - _Cost variance dynamics._ [image] Scope - _Components and features implemented vs. specified requirements._ - _Release burndown_ — reflects the tasks completed during an Agile iteration (measured in user stories, epics, or the entire project scope). - _Features waiting in the backlog longer than the deadline_ — a control point that, ideally, should always equal zero. [image] QA efficiency - _Test coverage and actuality._ - _Deliverables accepted in the first UAT phase._ - _Defects count_ per project/iteration/functional module (grouped by severity). - _Testing effectiveness_ per project/iteration. - _Rejected defects ratio_ — reflects the quality of defect localization and reporting procedures. - _Reopened defects rate_ — shows the efficiency of the quality stabilization procedures. ### Software quality KPIs ### Usability Indicates how easy it is for the software user to accomplish a desired task and the kind of user support the system provides. 1. User adoption rate. 2. Training duration. 3. Task performing duration. 1. The number of completed tasks per time period. 2. Completion rate (successfully completed to total tasks). 3. The number of errors. ### Availability Measures the probability that a system performs correctly at a specific time. 1. Mean Time Between Failures. 2. Mean Time To Detection​. 3. Mean Time To Recovery. 4. Mean Time To Failure​. 1. POFOD​ (Probability of Failure on Demand) - the number of failures/requests over the observed period. 2. ROCOF​ (Rate of Occurrence of Fault) - total number of failures. ### Performance Showcases the solution’s ability to meet action timing requirements. 1. Latency. 2. Throughput. 3. Capacity and spare capacity. 1. Schedulable utilization. 2. Screen refresh time. 3. Adaptability to accommodate additional resources. ### Security Measures the system’s ability to protect data and information from internal and external cyber threats. 1. Data encryption efficiency. 2. Security incidents. 3. Known vulnerabilities left open by the end of the month. 1. Vulnerabilities found by regular penetration testing. 2. Vulnerabilities found by independent penetration testing. ### Code quality Shows the overall level of excellence and reliability of a software program's source code. 1. Maintainability index (MI). 2. Cyclomatic Complexity (CC). 3. Depth of Inheritance. 1. Class Coupling. 2. Lines of code. 3. Halstead Volume. ## How We Take Care of Quality at Every Stage of Software Development Here is how we manage quality throughout all stages of our typical [Agile software development](https://www.scnsoft.com/software-development/agile) project. ### 1\. A steady start To substantially reduce quality-related risks, we introduce quality measures as early as the project's inception stage – when we explore the client's needs. - Describing the project **[scope](https://www.scnsoft.com/software-development/about/how-we-work/scoping)** and preparing high-level **[estimates](https://www.scnsoft.com/software-development/about/how-we-work/estimate),** ensuring they correspond to the client's needs and expectations regarding the deliverables, time frames, and budget. - Devising a **quality strategy** for our services and software. - _(optional)_ Signing a **quality agreement** as an appendix to the contract or work order. - Conducting initial **risk assessments** (including ones related to regulatory compliance, cybersecurity, and unplanned efforts) and openly discussing them with a client. Drawing up a **high-level risk mitigation strategy**. - Introducing a tailored [**collaboration strategy and plan**](https://www.scnsoft.com/software-development/about/how-we-work/collaboration) aimed to meet project goals with maximum efficiency. Check our RACI-based collaboration model for Agile software development ![Collaboration model for an Agile software development project - ScienceSoft](https://www.scnsoft.com/about/how-we-work-collaboration/raci-based-collaboration-model.svg) Hide - Assembling a **project team** of pre-vetted specialists best corresponding to a client's needs and approved by a client. ### 2. Shrewd planning At this stage, we elaborate on the project plan and determine tangible [success measures](https://www.scnsoft.com/software-development/about/how-we-work/success-measurement). - Creating a **detailed project plan**, defining **milestones**, and describing the **tasks** to complete. - Defining **KPIs** that will allow stakeholders to track the project's progress and us – to optimize and improve our efforts continuously. - Creating detailed **technical requirements specifications** (can be presented as user stories, mockup-based behavior descriptions, etc.). - Composing a **requirements traceability matrix**. - Eliciting all possible risks related to the software development project and preparing a **risk mitigation plan**. - Creating a **high-level test plan** that specifies the testing scope, manual and automated testing ratio, testing team composition, test schedule, general test entry and test exit criteria, QA toolkit, and test KPIs. ### 3. Solution building #### Architecture, [UX](https://www.scnsoft.com/software-development/about/how-we-work/ux-design) and [UI](https://www.scnsoft.com/software-development/about/how-we-work/ui-design) Design At this stage, we ensure top-notch software and service quality via: - **Cross-reviewing** functional and non-functional software requirements to improve their consistency and completeness for the development process and testing. - Designing a **high-performing, secure, and flexible architecture**. See an example of software architectures we create ![Smart contracts utilizing a third-party blockchain network - ScienceSoft ](https://www.scnsoft.com/insurance/smart-contracts/system-architecture.png) Hide - Studying the target users' needs and behavior and creating **convenient user experiences**. - Designing a **stylish app look** for high user engagement, retention, and ease of use. - Creating a **feature DoR** and handing over the feature to developers. - **Transparent communication** between the technical design, development, and QA teams. #### Coding We deliver software front and back end, APIs, and integrations in 2–4 week Scrum iterations. - Following **unified** code rules and **specific** rules for particular programming technologies. - Performing regular **unit testing** and [**code reviews**](https://www.scnsoft.com/software-development/code-review) (ad hoc reviews, pair programming, walkthrough, etc.). - Controlling quality metrics specific to the software type (involves **security** and **compliance** assessments for in-progress software with high requirements for data protection). - Introducing **Infrastructure as Code** and running relevant unit tests. - Implementing **[IT automation](https://www.scnsoft.com/devops):** establishing CI/CD pipelines, automating application monitoring, configuring automated development, testing, and production environments. #### Rigorous testing We hand over user stories to both developers and testers simultaneously to create and execute test cases in parallel with development. Our major quality management processes and activities at this stage: - Taking a **[shift-left approach](https://www.scnsoft.com/software-testing/shift-left-testing)** to testing and moving testing activities closer to the beginning of the software development process. - Designing **test scenarios** and **test cases**, writing **test scripts** for automated testing. - Setting up **test environment** and preparing **test data** (real or synthetic datasets) that reflect real operational conditions and edge cases. - Incorporating automated tests into CI/CD pipeline to speed up the testing process. - Executing manual and automated tests. - Analyzing test results, evaluating testing success, and performing **additional testing** if necessary. - Documenting all necessary testing aspects in compliance with **ISO/IEC/IEEE 29119-3:2021**. ### 4\. Delivery At this stage, ScienceSoft delivers a build or ready software to the customer. - Providing a **test result report** describing the testing progress, defects validation results, and invested efforts. - Introducing comprehensive **[software documentation](https://www.scnsoft.com/software-development/about/how-we-work/documentation)**, including maintenance guides and end user tutorials. ### 5\. Maintenance After the ready-to-use software is set live, we support and evolve the solution according to our client's needs. With ScienceSoft, one can be sure that the developed software always remains of excellent quality and brings high user satisfaction. - Recommending and implementing **improvements** and **new functionality** via CI/CD pipelines. - **Quality assurance** of new and changed features (covers full-scale [regression testing](https://www.scnsoft.com/software-testing/services/regression)). - **Optimizing cloud resources** for cloud-hosted applications. - Following the **ITSM**\-based approach and applying the **ITIL** best practices. - Monitoring and [reporting](https://www.scnsoft.com/software-development/about/how-we-work/reporting) **service KPIs**, continuously improving the performance of support teams. ## Check What Clients Appreciate in Cooperating with ScienceSoft [image] > ScienceSoft proved to be a professional service provider from the outset. The solution developed by ScienceSoft fully met the client's requirements and expectations. The project marked the start of successful and mutually beneficial cooperation between Leo Burnett and ScienceSoft. We appreciate their **proactive approach** and ability to suggest improvements to a prospective solution on both architectural and business levels. **We know we can always rely on ScienceSoft's various competencies when our clients require quality software which would facilitate their business success.** [image] [image] Rob Ellis CEO > Throughout security testing activities, ScienceSoft’s cybersecurity team proved to be result-oriented and attentive to detail. Thanks to ScienceSoft’s quality testing efforts, we were able to ensure a higher level of protection of our cloud application and the sensitive customer data stored in it. ScienceSoft has proved to **be a competent cybersecurity partner** who can **deliver high-quality testing services within the deadlines provided.** We consider ScienceSoft a trusted business partner and plan to continue our working relationship with them. [image] > … we can say that we are no doubt happy with our choice of development partners. **The quality they deliver is consistently high.** Given that the whole project team is international, we have no communication problems, and the reports are on time. **What we appreciate is their ability to work independently, with no need for our careful guidance**. > > With ScienceSoft, we managed to acquire the development resources that we needed and got them fit into our teamwork smoothly. **We believe they've contributed a lot to speed up our product's release**. Looking for a Quality-Dedicated IT Service Provider? Focus on what is important. Leave the rest to the vendor who cares about quality as much as you do.