capacitacion 1100

capacitacion 700

Workshop "Being Agile at Quality: Values, Practices and Patterns"

Workshop "Being Agile at Quality: Values, Practices and Patterns"

dis y admin base de datos big

Being Agile, with its attention to extensive testing, frequent integration, and focusing on important product features, has proven invaluable to many software teams. When building complex systems, it can be all too easy to primarily focus on features and overlook software qualities, specifically those related to the architecture. Some believe that by simply following Agile practices—starting as fast as possible, keeping code clean, and having lots of tests—a good architecture will magically emerge. While an architecture will emerge, if there is not enough attention paid to it and the code, technical debt and design problems will creep in until it becomes muddy, making it hard to deliver new features quickly and reliably.

It is essential to have a sustainable architecture that can evolve through the project life-cycle. Sustainable architecture requires ongoing attention, especially when there are evolving priorities, lots of technical risk, and many dependencies. This workshop presents a set of patterns that focus on practices for creating and evolving a software architecture while remaining Agile. These practices include a set of tools that allow teams to define “enough” architecture in the beginning of the project and to manage the state and the evolution of the architecture as the project evolves.

Topics: ● Quality and Agile ● Tradeoffs with Quality ● Breaking Down Barriers ● Whole Team Agile Quality ● Integrating Quality into Agile ● Finding and Describing Qualities ● Keeping the Focus on your Quality Values ● Measuring and Testing System Qualities ● Sustaining Quality

Course Objectives / Learning Outcomes

This session introduces techniques and practices for interjecting system quality specification and related architecture, design and testing efforts into your project while being more agile about it. We will present several agile techniques and practices that support the definition and delivery of system qualities. We will explore how QA, including testers, and architects can collaborate to ensure that system qualities are addressed in an agile manner emphasizing architecture capabilities such as usability, security, performance, scalability, and availability. You will get hands-on experience briefly practicing some of these techniques. You will learn options for coordinating work among teams and be exposed to techniques and practices that support the incremental definition and delivery of system qualities along with system functionality and weaving quality-related work into your projects and programs.

I have been innovating, collecting and writing on the best practices and patterns on this topic over the last several years. During this time I have given presentations, workshops, and keynotes at various conferences and in an industrial setting and published (and continuing writing and collecting) over two dozen patterns on this topic. I have recently worked with organizations on the best practices for Agile Quality Assurance and also shepherded Agile Experience reports on the subject. I received the New Directions award with a colleague at Saturn, given to the presentation that best describes innovative new approaches and thought leadership in the application of architecture-centric practices for the topic "QA to AQ: Shifting from Quality Assurance to Agile Quality".


● How to overcome barriers between QA and agile teams?

● How to structure Agile Teams keeping the focus on quality?

● When to focus on important qualities for your organization?

● How to integration Quality into your agile process?

● Ways to find and describe system qualities for agile teams.

● Ways to measure System Qualities and to make them visible to the agile team.

● Overview of different Testing Strategies for System Qualities.

● Ways to improve and sustain your agile practices with quality.


● Agile values and practices and their impact on system qualities.

● How system quality specifications, design, testing fit into agile processes.

● The integral role of architects and QA in supporting system quality objectives

● Patterns and techniques for addressing architecture risks and system quality concerns

○ Breaking down barrier

○ Adding quality concerns to a product roadmap

○ Alternatives for managing architecture and quality-related tasks

● Specifying system quality requirements

○ Simple quality scenario templates

○ Specifying measurable results

○ Agreeing on quality target values

○ Adding quality-related acceptance criteria to user stories

● Making Quality Visible

○ Quality radiators and dashboards

○ Quality-related work made explicit

○ Qualify the Backlog

○ Checklist Fitting Quality Assurance into your Agile process Questions and Wrap-up


Requirements: General understanding and background of agile principles (possibly enterprise-scale agile) along with knowledge of Quality Assurance practices.



Joseph Yoder
Joseph (Joe) Yoder (agilist, computer scientist, speaker, and pattern author) is the founder and principal of The Refactory, a company focused on software architecture, design, implementation, consulting, and mentoring on all facets of software development. Joe is also the president of The Hillside Group, a non-profit dedicated to improving the quality of life of everyone who uses, builds, and encounters software systems. Joe has presented many tutorials and talks, arranged workshops, given keynotes, and help organized leading international agile and technical conferences. He is widely 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, how to architect and build highly flexible systems, how to keep your design clean, using patterns, refactoring, and the best testing practices. Recently Joe has been working with organizations and thought leaders on best practices for including quality aspects throughout the complete software life-cycle. Joe thinks software is still too hard to change and wants to do something about this. He believes that using good practices (patterns), putting the ability to change software into the hands of the people with the knowledge to change it, and bringing the business side closer to the development process helps solve this problem.


General Information

Duratión: 4 hours; 2 hours presentation y 2 hours of hands-on.

Date and time: November 19th, 15:30 - 19:45 hours


Campus Santiago San Joaquín USM, Avda. Vicuña Mackenna 3939, Metro estación Camino Agrícola.


 $ 82.000 CHP or 120 USD or 3 UF


Contact and registration

Esta dirección de correo electrónico está siendo protegida contra los robots de spam. Necesita tener JavaScript habilitado para poder verlo.

fono 32-2654445

Note: The program is dictated as long as there is a minimum number of 15 participants.



Formulario de Postulación

(*) Son datos necesarios para enviar.

Formulario de Postulación
Nombre Completo (*)

Entrada no válida
Teléfono (*)

Entrada no válida
Correo (*)

Entrada no válida
Región / Ciudad (*)

Entrada no válida
Diploma (*)

Entrada no válida
Asunto (*)

Entrada no válida
Mensaje (*)

Entrada no válida

Ingrese Captcha

Captcha (*)

Entrada no válida Captcha