Outcome is one of the new buzz words and is central to aligning organizational or project visions and goals to measurable expectations. Testing organizations, as service entities, need to provide information about both product readiness as well as service quality. Many testing organizations struggle with how best to define both their service and their outcomes within a testing relationship. Testing as a Service (TaaS) organizations in particular are interested in better alignment of their work to outputs.
Join us as we address key questions of interest. What are good outcomes for a testing organization? Are outcomes in agile development projects differ from outcomes in more traditional projects? How can outcomes be used for optimum benefit? What, how, and why should you define outcomes? Are outcomes related to service level agreements? Whether you are an agile team member, an outsourced testing team, or manager of a testing organization, this tutorial can provide practical and valuable information and examples for viable testing service outcomes and their use in today’s world.