Abstract/Description

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.

Additional Resources

About the Speaker(s)

Joseph (Joe) Yoder (agilist, computer scientist, speaker and pattern author) is the founder and principle of The Refactory (www.refactory.com), a company focused on software architecture, design, implementation, consulting and mentoring on all facets of software development. Joe serves as president of the board of The Hillside Group, a group dedicated to improving the quality of life of everyone who uses, builds, and encounters software systems. He is best known as an author of the Big Ball of Mud pattern, which illuminates many fallacies in software architecture. Joe teaches and mentors developers on agile and lean practices, architecture, building flexible systems, clean design, patterns, refactoring, and testing. Joe has recently been working with organizations and thought leaders on the best practices for including quality aspects throughout the complete software life-cycle. In 2015 he won the New Directions award with a colleague at Saturn 2015, given to the presentation that best describes innovative new approaches and thought leadership in the application of architecture-centric practices for the presentation “QA to AQ: Shifting from Quality Assurance to Agile Quality”. Joe thinks software is still too hard to change. He wants to do something about this and believes that you can start solving this problem through the use of proven practices (patterns) and by putting the ability to change software into the hands of the people with the knowledge to change it.

Rebecca is President of Wirfs-Brock Associates. She helps organizations and individuals hone their design and architecture skills, improve system quality and manage technical debt. In addition to coaching and mentoring she conducts workshops on agile architecture, design and pragmatic TDD. She invented the set of design practices known as Responsibility-Driven Design (RDD) and by accident started the x-DD meme. Rebecca is Director of the Experience Reports Program and Experience Report Track Chair. She is on the Board of the Hillside Group and writes patterns about sustainable architecture, agile QA, and adaptive systems. If you want to share experiences or wisdom in pattern form, Rebecca can help you turn your itch for writing into the written word. Read her blog at www.wirfs-brock.com/blog and find articles and patterns on her resources page, www.wirfs-brock.com/Resources.html