Enrique A Decoss

Resolving Quality issues must be all the team's responsibility; perhaps we are talking about accountability; clearly, a QA Manager must understand quality issues and work with the team to prevent those and, in some cases, implement those initiatives to avoid over-correcting. Remember that there are Job descriptions including "Resolve quality issues" as QA manager responsibility; let's avoid this normalization.

Knowing yourself is essential, but knowing the company you will apply to is extremely important. Besides blogs and online info, we can ask employees directly what they value most working with X/Y company; perhaps some challenges. Nowadays, it is critical to research and select the right option to work with.

Testing is easy! I prefer another approach, using the right mindset in our companies; everyone can help us test correctly. Rephrasing that sounds pretentious. Don't get me wrong, every role or activity is essential, saying that, as QAs, we need to facilitate the proper mechanisms to make Testing visible and why it is necessary to all to Test with us. Everyone can help us to test; testing is enjoyable.

We can do many analyses, but let's be honest, if we don't know our current situation, perhaps switching tools is not the best option now; for example, if you are looking for a new test automation tool and your current situation is chaos, you are going to automate chaos. I've seen many companies bringing new tools after a few reports and dashboards, but could you remember who will use the tools? Your team knows more about their current situation, and if you need to update your current process, so be it.

Always consider Agile Testing; sometimes, if we are working in sprints, consider different aspects such as Manual testing, automation testing in the DoD, and developing new features. Creating test automation in sprints is really hard, and we may consider another approach. The main idea here is to test fast; in other words, fail fast, recover, and deliver shorter time-to-market cycles.

I consider one of the most crucial parts of the scrum master rules or mindset is coaching the incremental thinking in the development team and other stakeholders. At this point, you start hearing about scope creep and bad requirements. To avoid getting there, use incremental thinking to add to the software.