📋
QASpace-CaseStudies
  • Home
  • Test Strategy
    • Vision of Quality
      • Good Test Coverage
      • ISO 29119 Certification
      • Date Internationalization Format
      • Localization Testing
      • Test Management
      • Creating TestCase
  • How to Test
    • How to write good TestCase?
      • Tips on Testing
      • Pair Testing
      • UserStory to TestCases
      • Optimising the development flow in a Scrum team
      • Rate/Prioritise bug tickets
  • Exploratory Testing
    • Exploratory Testing
      • Creating Test Charters
      • Test Charters
      • Velocity was too high
  • Agile
    • Implementing Scrumban
      • Breakdown Task
      • Common work across teams
      • Sustainable QA process in the organization
  • Philosophy of Testing
    • Brainstorming
  • Metrics
    • Risk Analysis
      • Testing Outsource
      • How to measure Quality?
  • Automation
    • AI-Automation
      • Software through the lens of AI
      • SAP/Salesforce Automation
      • Mobile Automation
      • Solve by automating the GUI?
      • Improve Skill-sets
      • Coding Skills
      • Working in BDD
      • Value of Test Automation
      • UI/API automation asset
      • TDD VS BDD
      • Selenium vs Cypress
      • An important consideration of Test Automation journey
      • Balance Test Automation Development
      • Automation is no longer providing value
      • Define AI in test automation
      • Unique Locators
      • Best Practices as QA, QA Lead, and Automation Engineer
      • Making friends with Imposters
  • Survey/Polls
    • Is QA really a Gatekeeper?
  • Performance
    • Performance Testing
      • Client-Side Performace
Powered by GitBook
On this page

Was this helpful?

  1. Agile
  2. Implementing Scrumban

Sustainable QA process in the organization

TechWell Hub Community

PreviousCommon work across teamsNextBrainstorming

Last updated 4 years ago

Was this helpful?

Case Study:

Hello Everyone, In my current org, we have 8 automation test engineers but those all are scattered in different project. I am in process to setup a sustainable QA process in the organisation. We have taken some steps to make the things streamline. Nowadays we have started meeting daily for 10 minutes as a QA team to understand each other problems. Define some team OKRs to drive the things but those are not adding such value as a team. Team stuck in their respective assignments. Any suggestion how can we streamline these things to setup a better QA process.

Suggestion 1:

My suggestions would be to first of all stop thinking about it like the QA is a separate thing / group. Instead, think of the QA folks as team members of their perspective teams instead of a centralized team. Next, I would suggest having the teams define the overall quality process. IME whole teams that own quality consistently deliver much higher quality and are able to release more frequently.

As far as measures - I tend to look at the outcomes I wish to achieve. For example, I think escaped defects, deployment frequency, etc. are far more useful than number of tests or test coverage. The former show how the team is doing overall while the later really do not have a correlation to quality and the goal of delivering software.

-- Cheezy

Reference:

Assess Quality, Don't Measure ItSatisfice, Inc.
Logo