013: PM, BA, QA, UX – key IT roles beyond developers

Hello and welcome to yet another episode of Speedtalks, the podcast about everything tech in the financial services industry and beyond. The topic of today’s episode is PM, QA, BA, who are they and what do they bring to IT projects?

Okay, the idea about this episode is to talk about something that is often overlooked in discussions about software development. Who is needed in a project besides developers, besides the engineers that are actually doing the coding.

In this episode, I will explore the key non-development roles such as project manager, business analyst, quality assurance (tester) and UX designer. What do they do? What value do they bring to the project? How much do they cost? And is it really worth paying for them?

Why isn’t a development team alone enough?

Development teams excel at writing code, but a project’s success depends on more than just development. Someone must manage priorities, business requirements, and quality assurance. That’s where PMs, BAs, QAs, and UX designers come in. Developers alone cannot gather requirements, design the project, test it, and maintain constant communication with clients. IT projects are often more complex than expected, requiring analysis, risk management, and communication to avoid failure.

The key roles in IT projects

Project Manager (PM)

A Project Manager ensures that the project is delivered on time, within budget, and according to client expectations. Without a PM, projects can quickly become chaotic, with tasks improperly assigned, risks going unnoticed, and communication breaking down. The PM serves as the primary point of contact between the client and the team, overseeing developers’ time and coordinating the project to ensure smooth execution.

Why invest in a PM?

• Prevents delays and communication issues.
• Helps mitigate organisational chaos.
• Ensures proper task management and risk assessment.

Business Analyst (BA)

A Business Analyst translates business needs into technical requirements. Often, clients come with an idea of what they need, but a BA refines these concepts to align with business goals. By gathering and analysing requirements, they minimise the risk of developing a product that fails to meet expectations. BAs bridge the gap between business needs, user expectations, and technical feasibility.

Why invest in a BA?

• Reduces the risk of costly errors (which can otherwise cost tens of thousands) by clarifying requirements from the start.
• Ensures alignment between business goals and the final product.
• Saves time by streamlining development workflows.

Quality Assurance (QA) – Tester

QA testers ensure software quality, identifying bugs before they reach users. Quality means different things for different projects, but at its core, QA is about making sure a product functions correctly and reliably. A QA tester’s role goes beyond clicking through an application—they systematically test, both manually and through automation, to detect potential issues before release.

Why invest in a QA?

• Fixing bugs post-release is significantly more expensive than catching them early.
• High software quality ensures business stability and lower maintenance costs.
• Enhances user satisfaction by preventing functionality issues.

UX Designer

A UX Designer ensures that a product is intuitive, user-friendly, and visually appealing. Even the best technical solutions can fail if they are hard to use. UX designers focus on user interactions, ensuring that the product serves its intended purpose efficiently.

Why invest in a UX Designer?

• A well-designed interface increases user satisfaction and conversion rates.
• Helps avoid usability issues that could make the product unappealing.
• Improves overall customer experience, leading to better retention.

What does an ideal team look like?

In an ideal scenario, a development team is complemented by other specialists. A typical setup might include:

• Developers: 2-4 engineers (or more, depending on project size)
• QA Testers: 1 tester per 2-3 developers
• Business Analyst: Helps with requirement gathering and refinement
• UX Designer: Works on the design phase before development
• Project Manager: Oversees and coordinates the project

For smaller teams, some of these roles may be part-time. A full Scrum team of about eight people might include four developers, two testers, a BA, and a PM, ensuring smooth workflow and efficient delivery.

Are these roles included in project costs?

Whether these roles are included in project costs depends on the cooperation model:

• Time and Materials Model: Roles are billed separately.
• Fixed Price Model: Costs for these roles are included in the estimate.

In most professional IT companies, these roles are standard in project teams. While some smaller projects may function without them, removing these roles often leads to higher costs due to misalignment, usability issues, and post-release bug fixes.

How much do these roles cost?

Compared to developers, these roles are generally more cost-effective:

• QA testers typically cost 20-30% less than a frontend developer.
• PMs, BAs, and UX Designers usually cost 20-30% less than a senior backend developer.
• Some companies price QAs the same as developers, but many (including Speednet) offer lower rates for non-development roles.

Conclusion

PMs, BAs, QAs, and UX Designers are not unnecessary expenses — they are essential team members ensuring project success. Their presence reduces risks, increases efficiency, and leads to a better final product. If you’re planning an IT project, investing in these roles will ultimately save time, reduce costs, and improve overall project outcomes.

Thanks, and stay tuned for the next episode!