Have you ever heard this conversation before: “We are totally Agile, we have stand-ups everyday! That isn’t agile. That is trying to be “hip” to all the “new jazz.” #FellowKids
Before writing this, someone asked me “What is the one thing the Quality Engineering team at Appian does that is unique?” I couldn’t answer them, because I don’t feel I am part of the QE team. I feel like I am part of the development team. This is what it means to be agile at Appian. This is why we are Quality Engineering (QE) and not Quality Assurance.
So how does QE fit into Agile development? I often hear QEs at other companies say, “We do all the testing at the end of the sprint” or “We test the previous sprint’s work in the next sprint” — NO! NO! NO!
Agile testing is about continuously testing the product from the beginning (spec document review) to the end (regression and release testing). The earlier you find a bug, the cheaper it is to fix.
Here are my rules for being a good QE in an Agile world:
What does “Quality Assurance” mean in an Agile World was originally published in Appian Engineering on Medium, where people are continuing the conversation by highlighting and responding to this story.