Feature Quality: QC/Dev Alignment

4 years ago dzone.com

Summary: This is a summary of an article originally published by the source. Read the full original article here →

During Agile work, as a team, we care about customer satisfaction by getting earlier feedback during Agile sprints, but at the same time, we need to represent sprint work with high quality and we need to make customers happy.

After the user story is refined, team members should develop acceptance criteria, preferably one that also includes indirect scenarios.

They can then assign test cases that cover happy scenarios to development team members to make sure that the feature/user story is released to the quality team with at least the happy scenarios functioning as expected.

Sometimes a development team member says that this feature/user story is ready to be tested on the testing environment by the quality control members, while it is not deployed/merged yet to the testing environment.

DevOps Articles