Agile teams incrementally deliver functionality based on user stories. In the sprint to deliver features, frequently software qualities (non-functional requirements) such as security, scalability, performance, and reliability are overlooked. Often these characteristics cut across many user stories. Trying to deal with certain system qualities late in the game can be difficult, causing major refactoring and upheaval of the system’s architecture. This churn isn’t inevitable. Especially if you adopt a practice of identifying those characteristics key to your system’s success, writing quality scenarios and tests, and delivering on these capabilities at the opportune time.
We will show how to write Quality Scenarios in an Agile manner that emphasize architecture capabilities such as usability, security, performance, scalability, internationalization, availability, accessibility and the like. We will also address the when, where, and how on Quality Scenarios. This will include how to identify, profile, and outline the relevant quality characteristics. This workshop will be hands-on; we present some examples and follow with an exercise that illustrates how you can look at a system, identify, and then write and test quality scenarios.
You must be a Member to view this post and you are currently not logged in.
You can either log in below or sign up here.