Developing software is a costly endeavor. Mistakes are often compounded by miscommunication. Developers and Testers make mistakes because they misunderstand the business requirements. Business analysts make mistakes because they misunderstand the stakeholders. Defects from miscommunication will often go undetected until the software has been implemented, which leads to expensive and time-consuming rework. Establishing a shared quality language is the nexus of understanding for stakeholders, designers, developers, testers, and customers. In this talk, participants will learn how to develop a set of quality test case standards to reduce the cost of quality and meet the customer’s needs. The training will leverage the industry practice of Behavior Driven Development, which promote requirements by example & collaboration, to develop a shared language across not only a team but the whole enterprise. The shared language is written in Gherkin format (Given, When, and Then specifications) to define requirements independent of application type and focused on delivering value that everyone in the organization understands.