In this series, we pull back the curtain on the art and science of our work. Each part of the Project Blueprint series offers a deep dive into the minds and methods of each team member of a software development project at Zure.

From the initial spark of inspiration to the final keystrokes of code, we want to give you a glimpse into our project landscape, the complexities of software development, and our ways of working.

In this blog post, I will concentrate on describing what our Quality Assurance (QA) professionals do at Zure to help the company in its quest for quality. How we support Zure’s ambition to be the world’s top problem-solver, backed by a commitment to quality.

“By 2040, Zure wants to be the highest quality problem-solver globally” This statement is proudly displayed on Zure.com/About. It is our guiding light, our ultimate destination. For someone experienced in quality assurance, it sounds so lovely; to have the word quality, in our company’s primary goal.

But what does this mean on a day-to-day basis at Zure? The website also explains, “The highest quality comes from the culture, from the people. Quality comes from what we focus on, find meaningful, and want to be proud of.” This is a sentiment I can easily agree with. Quality isn’t just about having the most advanced testing tools, making statistics about the bugs, or recruiting a huge team of testers. It’s about how we conduct our everyday work; how we learn from each other, interact with our clients, and strive to do our best in our tasks.

Kick-starting the Project: Sales and QA

Most of the projects start with some kind of sales phase. To ensure optimal outcomes, it is ideal for QA to be involved in work from the very beginning. Participating in initial customer meetings, reviewing requirement spreadsheets and the like often supply critical insights into potential quality risks for the planned project. It may also turn out so, that QAs, with a fresh point of view, may bring some totally new ideas to the planning table. Their involvement in the early stages also allows them to gain a comprehensive understanding of the project, which can prove beneficial in later stages. They are able to identify and address potential pitfalls before they become major issues, ensuring a smoother project execution.

When things align ideally and we have the opportunity to embark on a brand new development project, it is beneficial to have a QA professional there. From the very beginning, it should be recognized that what matters the most in this project quality-wise? What are the quality attributes and factors to consider? In certain scenarios, usability might be the primary concern, while in others, performance or security could take precedence. Recognizing these factors from the get-go allows the solution to be designed to meet those specific needs right from the onset. This approach not only tends to be more efficient but also more cost-effective.

Also, the testing part can be thought about right from the beginning; before implementing anything make sure you know how you know something was implemented right. In a practical sense, this could mean for example…

• Establishing work processes that promote clarity and eliminate ambiguity among the team and other stakeholders.
• Working with the project stakeholders to define clear acceptance criteria. This will help determine whether the implementation is considered successful.
• Implementing risk-based testing strategies to prioritize testing efforts based on potential impact and likelihood of occurrence.
• Drafting preliminary high-level charters for exploratory testing
• Considering the feasibility of writing test automation cases already in the beginning. These would be on an abstraction level closely aligned with the business case.

This early focus on testing ensures that quality checks are built into every stage of the project, rather than being an afterthought.

The Role of QA in Project Implementation

When a project is in full steam, it’s typically a busy time for QA professionals too. Our work usually involves being part of interdisciplinary teams, working alongside proficient developers and other essential team members. The specific tasks we do can vary widely; largely depending on clients’ business requirements and unique needs. In some instances, the solution might have an extensive user interface, while in other cases, the focus might be solely on APIs or data pipelines, not to forget native mobile apps. The role of a QA professional can be very versatile and usually is adaptable to the specific demands of each unique project.

Testing, naturally, is an essential aspect of quality assurance. Its principal aim is to ensure that the solution functions as planned. To accomplish this, we use a variety of different tools and techniques. Inspection, learning, and documentation form the core of our testing process. The power of human cognition is an invaluable asset here; at times, you begin to notice patterns or spot something out of the ordinary that demands further examination. The most crucial tests should ideally be automated to enable swift and consistent repetitions – this is crucial in safeguarding the most important features. In essence, our approach to testing combines the best of human insight and technological capabilities to ensure the highest level of quality.

But when we are testing, how do we know what was intended? Against what assumptions are we testing? This is a critical question in the Quality Assurance professional’s role. In practical terms, this could mean ensuring that the user stories, which form the foundation of the implementation, are developed to a sufficient degree; to a level where everyone comprehends the objective in the same manner. And another important question is when something should be considered as ready? When it meets our standards, how do we go about gathering feedback from the client or end-users? Who gives the final approval for what we have implemented? Thus, a significant portion of our work extends beyond the technical realm; it involves engaging in deep conversations with the team and the client’s stakeholders; sometimes from business to end-users.

Aside from establishing work methods and conducting traditional testing, our work often includes a range of specialty areas. Many of these are associated with various quality attributes and factors, mentioned already earlier. For instance, in certain cases, performance testing might be necessary. In such scenarios, we create scripts to simulate the load of potentially thousands of users, so we can see how our solution scales, and if issues arise, ensure recovery is executed in a safe and controlled manner. Similar specialty areas can include usability, accessibility, and security. Of course, it’s unrealistic for one person to manage everything independently, which is why we pride ourselves on the diverse expertise we have at Zure, including highly skilled designers and security specialists, among others. Together, we can ensure that the solution functions as intended, even when things get tricky.

Autonomy, purpose, mastery

In his transformative book “Drive,” Daniel H. Pink explores three intrinsic elements that fuel our motivation:

Autonomy, Mastery, and Purpose.

These elements can significantly boost engagement, productivity, and satisfaction in work.

Autonomy, defined as the desire to be self-directed, plays a significant role in boosting engagement. It involves embracing the unique perspectives of each team member and creating an environment where diverse solutions can thrive. In the field of quality assurance, it is important to have different approaches and ways of thinking to address challenges effectively. Each QA specialist may have a slightly different way of doing their thing – and that is just fine. This diversity allows us to learn from one another and benefit from each team member’s unique skill sets and experiences. Some may excel in test automation, while others may have expertise in AI or navigating complex acceptance testing phases. By fostering autonomy and valuing individual contributions, we can continue to excel in delivering high-quality solutions at Zure.

In autonomous teams, decision-making is a collaborative effort that involves working closely with clients to determine the best course of action. We understand that there are no one-size-fits-all solutions, and the best outcomes are achieved through joint efforts with our customers. As QA team members collaborate with the client’s team, they are not isolated from the supportive community at Zure. We have a strong network where knowledge is shared, and mutual support is provided. This collective strength and unity foster a sense of purpose and mastery among our QA specialists, empowering them to overcome challenges and assist the project team in delivering superior quality

Summary

The story that this blog post tells is that at Zure, quality assurance is more than just a department or a checklist; quality is built into our culture. What is special at Zure, especially in terms of quality, are our values. One of these values is ‘Work is better together.’ Whether it is collaborating with clients, the Zure team, or third parties, I do believe that together is also the place where the greatest quality is built.

Next up in the series, we will have a look into the mind of a DevOps Architect / Engineer. Stay tuned! In case you missed the first part of the series, go check out the first part: Project Blueprint: The Team Lead.