Quality assurance as a project manager: 5 tips & thoughts

In the dynamic world of agile projects, project managers are often faced with the challenge of how we can implement quality assurance efficiently. As a Scrum Master, I’m sharing five tips and thoughts on the subject today to help you get started.

Before we go into more depth, let’s briefly clarify what quality assurance means in project management. In agile teams, quality assurance refers not only to the code, but to the entire process and, above all, the results of the project. It’s about ensuring that the team delivers high-quality results that meet customer requirements.

Responsibility for quality assurance in the team

Who is actually responsible for quality assurance in projects? The answer here is a theoretical, optimal one: Everyone in the team. Quality assurance is not an isolated task of a single project manager. Every team member should feel equally responsible for achieving the best possible results. This not only promotes cooperation, but also contributes to a holistic understanding of quality.

At the same time, this answer may miss the mark, as the search is often on for a responsible person. In this case, the project management or the project manager or another role is usually responsible.

There are three typical methods used by project managers when it comes to quality assurance.

Statistical Process Control (SPC):

Statistical Process Control is a method for monitoring and controlling processes. By analyzing statistical data, deviations from the normal process flow can be identified early on. This enables proactive intervention to ensure the quality of the results. SPC is an effective technique for identifying variations in processes and driving continuous improvements.

Failure Testing:

Failure Testing is a method in which a system or product is deliberately exposed to extreme conditions in order to identify possible weaknesses or failures. The goal is to test the resilience and reliability under extreme conditions and to ensure that the product meets the requirements. Failure Testing is a proactive measure to identify and fix potential weaknesses early on before the product is released to the market.

Total Quality Management (TQM):

Total Quality Management is a comprehensive approach to improving quality in all areas of a company. The focus is on the continuous improvement of processes, products and the organizational structure. TQM emphasizes the involvement of all employees in the quality process and strives to define and continuously exceed quality standards. This holistic approach creates a culture of quality orientation throughout the company.

I would like to add a few concrete tips for your agile project to these rather abstract approaches to the topic of quality assurance. The tips are intended to contribute to a better delivery of results at the end of the project.

Tip 1: Implement automated tests:

Scrum Guide recommends continuous improvement, which is obviously closely related to quality assurance for project managers. Automated testing is an effective way to ensure quality. Unit tests can be performed automatically during the development process. Saving time and minimizing potential sources of error are the benefits.

Tip 2: Continuously train team members:

Agile’s project management requires constant adaptation. Continuous training is therefore crucial. Example: Establish regular training sessions or lunch-and-learn sessions to share and discuss new knowledge within the team.

Tip 3: Implementation of code reviews:

Scrum Guide encourages transparent collaboration. Implement regular code reviews in the team (if it is an IT project) to ensure that the code not only works, but also meets the agreed standards. Joint feedback promotes quality development.

Tip 4: Emphasize the Definition of Done (DoD):

A clear Definition of Done (DoD) is crucial for quality. Define clear criteria for when a task is considered complete. This creates transparency and prevents misunderstandings about when work is considered to be of high quality.

Tip 5: Use reviews and retrospectives for continuous improvement:

Scrum Guide emphasizes regular inspection and adaptation. Use retrospective meetings to reflect together on the process and identify potential for improvement. Instead of looking for blame, focus on more efficient ways of working.

By the way, I would like to add as a note that this information depends on what kind of company you are in - is it, for example, a small startup, a large corporation or somewhere in between? Then some of the points here may be less relevant, because management and leadership styles should of course be adapted to their context (more on: What is small business leadership).

Of course, tools can also help with quality assurance in your project. Echometer, which was developed for agile teams, leads and project managers, is particularly worth mentioning here.

Echometer is a digital tool that helps agile team leads with agile retrospectives and team Health Checks. Whether remote, hybrid or on-site: it makes team coaching measurable and professionalizes your work while saving you a lot of work. Just take a look at our website to find out more: www.echometerapp.com.

Many quality assurance measures could be saved if the basics of the agile manifesto were really lived.

Christian Heidemeyer, Psychologist & Scrum Master

In the agile world, quality assurance for project managers is a collaborative process at best. By everyone in the team taking responsibility, encouraging continuous feedback, constantly educating themselves and using retros for improvement, we not only create high-quality products, but also a motivated and efficient team.

Finally, one more note: If you would like to try out how it feels to develop your team further with our tool: You can start an agile retrospective without logging in below, in this case the “Keep, Stop, Start” workshop. 

Alternatively, simply forward our website to the responsible colleagues: www.echometerapp.com.