Key learnings from Leading Quality Book by @ronaldcj and @owaispeer

#softwaretesting #quality #QualityManagement #testing #testingstrategy

A thread ๐Ÿงต ๐Ÿ‘‡
It is necessary to communicate to the entire team how the efforts invested in quality add value to the business. ๐Ÿ’ฐ
The mindset of upper management ๐Ÿ‘‘ plays an important role in developing quality practices in the company
There should be balance with respect to the speed with which you are deploying the changes and quality that is provided along with that speed ๐Ÿšค
Poor quality can damage the company in many ways including losing the customers ,the team members as well as a huge cost to your career ๐Ÿ˜ญ
Instead of just focusing on the technical aspect of your role, it is necessary to focus on how your role as well as the team can impact the growth of the business by identifying the company's growth metric and all the decisions should be based upon that ๐Ÿ˜Ž๐Ÿ˜Ž
There should be clarity within the organisation about the following narratives:

- Who will be responsible for the quality. Ideally everybody and culture should be created so that everyone becomes responsible for the quality of their work.
Narratives continued:

- Right ways to test and tool to be used. Ideally different types of testing based on where the product is currently in the market. It all depends on the context.
- Discussions around what return on investment is by investing in quality
Automation should be done based on the value that it would provide. For example a scenario is too complex to automate and the probability of your customer using it or getting impacted is very low then it's better not to automate it.
#testautomation
Each product navigates broadly through following stages:

- Validation: product-market fit
- Predictability: creating a stable infrastructure for scale
- Scaling: minimising negative impact to unlock growth
Your testing strategy and the tools should be changed as the product evolves through the above stage.
It is more important to prevent the bugs rather than finding them.
Testing in production can provide you with different information than testing in sanitized environment. It is also necessary to have a robust infrastructure in place to do so. It does not mean you should only test in production though ๐Ÿ˜
Monitoring and alert systems ๐Ÿšจ๐Ÿšจ should be based on how a change or an issue can impact the user. This insures that everyone in team is focuses on users.
It is necessary to have the clear vision first to build the right strategy.
Napoleon Hill's quote from the book:
When defeat comes, accept it as a signal that your plans are not sound, rebuild those plans, and set sail once more toward your coveted goal.
If you have read the book then add your learnings too

โ€ข โ€ข โ€ข

Missing some Tweet in this thread? You can try to force a refresh
ใ€€

Keep Current with Ashwin Karangutkar

Ashwin Karangutkar Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(