2.6. Summary

● QA is not just a phase — it’s a continuous practice across SDLC

Quality Assurance (QA) is integrated throughout the entire Software Development Life Cycle (SDLC), rather than being limited to a single phase, such as testing after development. This integration ensures that quality standards are maintained at every stage, from requirements gathering to maintenance.

Think of a bakery where quality control is applied at every step of making a cake. Instead of just tasting the cake at the end to check if it's good, the baker checks the batter for proper mixing, ensures the oven is at the right temperature, and inspects the cake after baking. This continuous checking guarantees a high-quality cake, just as continuous QA guarantees a high-quality software product.

● In Waterfall, QA validates after development ● In Agile, QA is embedded from day one in every sprint

In the Waterfall model, Quality Assurance typically reviews and validates the software only after the development phase is complete. This means any defects found at this stage can be costly to fix. In contrast, the Agile methodology involves QA from the very start, allowing QA professionals to create test cases alongside the development team and catch issues early, resulting in more efficient development cycles.

Imagine preparing for a theatre performance. In a traditional rehearsal method (akin to Waterfall), the cast only practices their lines without feedback until the final performance. If something goes wrong, it’s harder to fix. In a more collaborative method (like Agile), the director gives feedback throughout the rehearsals, which helps the actors improve continuously, leading to a better final performance.

● Effective QA ensures that every phase contributes to a quality product

When QA practices are effectively implemented throughout the SDLC, every phase — from planning to deployment — focuses on quality outcomes. This assurance means that the software not only meets user requirements but is also free of significant defects, enhancing user satisfaction and reducing long-term costs associated with software maintenance.

Consider building a house. If every step, from laying the foundation to painting the walls, is carefully checked for quality, the final house will be sturdy and beautiful. If checks are missed in early stages, the house might face serious problems later on, similar to how missed QA steps in software development can lead to bigger issues after launch.

“In modern SDLCs like Agile, QA is no longer a gatekeeper — it is a collaborative partner in delivering value.”

In contemporary software development practices, particularly in Agile frameworks, the role of QA has evolved from merely checking work at the end to actively collaborating with development teams. This shift means that QA contributes not just to testing but also to building the product, ensuring that quality is part of the design and development process from the very beginning.

Think of a sports team, where the coach (QA) works alongside the players (developers) during training. Instead of just grading their performance after each game, the coach provides feedback during practice, helping the team improve their strategies and execution. This teamwork leads to better overall performance in matches, just like collaborative QA leads to high-quality software.

--