Agile2019 has ended

Sign up or log in to bookmark your favorites and sync them to your phone or calendar.

Testing & Quality [clear filter]
Monday, August 5

10:45 EDT

Testing Microservices - See It, Feel It, Touch It, Heal It, Explore It (Ken Pugh)
Limited Capacity full
Adding this to your schedule will put you on the waitlist.

Microservices are becoming more prevalent. External behavior of an application depends on multiple services working together. Each service needs to be checked that it both provides the desired behavior as well as handles exceptions and error conditions, such as the inability to communicate with a dependency. Interactions between these services needs to be checked and monitored. Checking behavior does not stop at deployment but needs to continue after release.
From a testing perspective, microservices can be viewed both as mini-applications with external behavior and as internal components. For applications, the externally facing triad (tester, developer, and customer) collaborates to create tests for behavior; for internal components, a different triad (tester, consumer, producer) generates these tests. To properly test microservices, we need to see, feel, touch, heal, and explore them.
See it: Tests need to be visible so that all members of the triad share the understanding of the behavior.

Feel It: Behavior for cross-functional (non-functional) aspects of microservices can be documented in tests.

Touch It: Testing for interactions of microservices can include injection or simulation of faults.

Heal It: Check that telemetry which records microservice interactions can be used to determine failure causes.

Explore It: Testing ought to go beyond just the behaviors described.
With so many aspects, testers need to work as collaborators in specification and tests, not just the test executors. The primary audience for this interactive workshop is for testers involved in microservices. However, it is also appropriate for any role which collaborates on the construction or delivery of these microservices. The session includes both lecture and a set of exercises on specifying and testing microservices.

Learning Outcomes:
  • Collaborate on creating microservice specifications with tests
  • Create appropriate cross-functional behavior tests for microservices
  • Determine a strategy to test microservice interactions
  • Explore ways to test telemetry


avatar for Ken Pugh

Ken Pugh

Chief Consultant, Ken Pugh, Inc.
Ken Pugh helps companies evolve into lean-agile organizations through training and coaching. His special interests are in collaborating on requirements, delivering business value, and using lean principles to deliver high quality quickly. He has written several programming books... Read More →

Monday August 5, 2019 10:45 - 12:00 EDT
National Harbor 8

15:45 EDT

How agile is your testing mindset? (Karen Greaves, Kelley Cooper)
Limited Capacity full
Adding this to your schedule will put you on the waitlist.

Agile testing is about more than how to squeeze enough testing into the last few days of the sprint. However, many teams have adopted agile and not yet changed the way they think about testing.
Do any of these sound familiar:
Testers are usually extremely busy at the end of a sprint.
Teams have a hardening sprint before they ship where they do manual regression testing.
There is a growing backlog of bugs found internally that never get fixed.
You really want to do test automation but you struggle to fit it into the story.
Developers are usually working on different stories to the testers because they work ahead.
Task boards have a test column after the dev or in progress column.
If so, it's time to adopt an agile testing mindset. In this session, we will introduce you to 5 simple statements to help you practice this new mindset every day. We will also cover techniques you can start using immediately to help reinforce this mindset. These will be simple things anyone can do: from a minor tweak to your taskboard, to different questions to ask in planning.

Learning Outcomes:
  • Experience how testing early and often can actually save you time.
  • List five ways agile testing is different to traditional testing.
  • Learn which questions to ask to prevent bugs before any code is written.
  • Learn some simple techniques for your task board to help focus on doing testing activities before development (even if you don’t do TDD).


avatar for Karen Greaves

Karen Greaves

Agile Coach, Growing Agile
I love meeting new people so come introduce yourself. Check out www.growingagile.co.nz to see what I look like, or just listen for the loudest person in the room :)
avatar for Kelley Cooper

Kelley Cooper

Agile Coach
Professional herder of cats on PCP...Agile Coach and mother of 4!

Monday August 5, 2019 15:45 - 17:00 EDT
National Harbor 8

15:45 EDT

Pop culture as inspiration for test ideas (Nicola Sedgwick)

Do you see colleagues getting tunnel vision and fixating on resolving problems or releasing features?
Do you understand the value add to the user (or business) for every item in every release?
Do you have a great quality product but unhappy users?
"If the answer is "yes", then don't wait another minute. Pick up the phone and call..."
You're not alone
Sometimes we need a stimulus or trigger to break us out of the day-to-day and get us looking at a feature or task in a new light. This workshop will share some tools for doing exactly that. These tools are not complex or technical, but fun exercises and games to demonstrate how we can take inspiration from popular culture to breath new life into our work and our teams. For Agile 2019 the inspiration will be:
  • Ghost Busters
  • Dungeons & Dragons
  • David Bowie

Learning Outcomes:
  • Techniques for forcing yourself to look at a scenario through a different lens (David Bowie)
  • Understanding that 'tunnel vision' is a human condition and not a failing (Ghost Busters)
  • Bringing feature requirements to life by having fun with them (Dungeons & Dragons)
  • Takeaway instructions for attendees to run these games with their own teams

avatar for Nicola Sedgwick

Nicola Sedgwick

Mindful Leader, Coach & Team Glue, Culturli
An avid enthusiast of agile ways of working, Nicola loves the way technology can enhance and transform the world around us. Nicola is often found working with a product and coaching focus to ensure agile teams collaborate between themselves, and with stakeholders, in order to eliminate... Read More →

Monday August 5, 2019 15:45 - 17:00 EDT
Chesapeake G/H/I
Tuesday, August 6

09:00 EDT

Test Everything - Quality ... It's not just for code anymore (Bob Payne)
Limited Capacity filling up

In this dynamic workshop we will explore the world of value delivery and quality. If done means potentially shippable, valuable, operable, usable and secure we need to do more than just test the code.
All too often I have seen systems developed with great automated testing on the widgets that make up our "Product". I use the quotes around product because I believe we need to look more holistically about how we deliver value in organizations. This is not a new idea, testers have striven to take this approach and when a holistic approach is taken to all aspects of quality our business outcomes are better.
We deliver what we thought was needed in the "Product" but...
  • It does not deliver the value we thought because we did not test the value proposition before building.
  • It is not optimally usable because we did not test the user experience.
  • It has operational issues because we did not test infrastructure, load, performance or other critical operational issues.
  • It has documentation but that documentation is not used because we did not test the, need, value, format or accuracy of it.
  • It gets delayed or is stopped from production because we did not test our assumptions about, security, governance and risk.
"Your system is perfectly designed to get the results you are getting."
-W Edwards Deming"
We must change the system of product delivery to get the results we want.
This world cafe style will start with an introduction to the topic of value, appropriate quality and testing both value and quality. I will discuss example methods for:
  • Testing Value
  • Testing Usability and User Experience
  • Testing Operations
  • Testing the Documentation
  • Testing Security, Risk, Audit and Governance
We will then break out into groups around the 5 topics and brainstorm how to ensure quality as early as possible and how we might test even before we build. Participants will rotate through the topics and add greater and greater detail to them as they drill down on the topics.
A readout will follow
For more information on the World Cafe workshop format you can check it out here (http://www.theworldcafe.com/key-concepts-resources/world-cafe-method/).

Learning Outcomes:
  • - Testing everything
  • - Testing early
  • - Testing more than just the code


avatar for Bob Payne

Bob Payne

SVP of Agile Transformation, LitheSpeed
An early adopter of Extreme Programming, Scrum, and SAFe, Bob Payne has worked exclusively as a Lean+Agile Transformation leader since 1999.Bob hosts the Agile Toolkit podcast and has produced over 170 podcasts, recording a variety of industry leaders and Agile practitioners. His... Read More →

Tuesday August 6, 2019 09:00 - 10:15 EDT
Chesapeake G/H/I

10:45 EDT

Leveraging software development principles into automation framework (Aditi Mulay, Ricardo Mediavilla-Maldonado)

Automation framework development can be considered similar to application development. The framework would greatly improve if the the same design principles used to write application code are leveraged to build it. By leveraging the 4 pillars of Object Oriented Programming in writing your automation framework, we can achieve the same level of efficiency as your application. Here are some examples we will discuss during the presentation:
  • Abstraction
  • Encapsulation
  • Inheritance
  • Polymorphism
Software development is built on the foundation of reusability and reliability. By making the steps in scenarios reusable and scenarios or test cases independent, we can lower the test maintenance costs and improve stability.

Learning Outcomes:
  • We expect that attendees will have a better understanding of software development principles such as abstraction, encapsulation, inheritance and polymorphism and how to use these concepts in the development of automation frameworks


avatar for Aditi Mulay

Aditi Mulay

Automation Test Lead, Karsun Solutions LLC
Aditi Mulay is currently working as Automation Lead at Karsun Solutions LLC ensuring code quality, increasing test coverage for their web based application. Aditi has worked in diverse domains like education, advertisement and the government sector. Aditi has managed and lead automation... Read More →

Tuesday August 6, 2019 10:45 - 12:00 EDT
Chesapeake J/K/L
Wednesday, August 7

10:45 EDT

Testers in the deployment pipeline - Blockers or assets? (Alan Parkinson)
Limited Capacity seats available

Companies that release multiple times a day typically financially outperform companies that don’t. Moving from monthly or weekly deployments to deploying multiple times a day requires an introduction of new technical practices and the concept of the deployment pipeline. Without any changes to the testing techniques used and the stages they are applied within the pipeline, testing quickly becomes a bottleneck and a major frustration. The knee jerk reaction to this situation to remove skilled testers and just use "Automated tests".
Testers still have a place in deployment pipelines and in this interactive workshop, we will be using games to introduce the concepts of small frequent deployments, learn why tester practices may create a bottleneck in the deployment pipeline, and what changes you can make to avoid these blockages. The exercises run within the sessions are designed to be taken back to the office to help with coaching your co-workers.

Learning Outcomes:
  • How automation can give a false sense of security to teams and why you still need skilled testers
  • Exercises to help coach, teach, or influence colleagues to adopt changes to testing within the deployment pipeline
  • The impact on testing when developers adopt a trunk-based branching strategy and feature toggles
  • Where different testing practices need to be moved within the deployment pipeline


avatar for Alan Parkinson

Alan Parkinson

CEO and Product Owner, Hindsight Software

Wednesday August 7, 2019 10:45 - 12:00 EDT
Chesapeake 10/11/12

10:45 EDT

Title: Finding Efficiencies in Agile Testing (Melissa Tondi)
Limited Capacity seats available

Imagine if you could add a more time to your testing, where would you spend it? Although we can't add more hours to our day, we can find time by discovering inefficiencies in our current approach.
Many of us feel like we never have enough time to fully test in a given sprint, cycle or other timeframe. We plan for the best case scenario, but, undoubtedly, something happens with our best-laid plans that cause us to feel like we "just didn't test enough." In this session, we will talk about the five areas that may be causing inefficiencies in your overall approach - to include test planning and duplication of testing to the left of QE. Melissa will discuss these five areas and you'll have a chance to share yours with the outcome to be practical solutions that can be implemented quickly. Once we have the plan to reduce or eliminate the inefficiencies, we'll talk about areas you may be able to spend more time in or add to your overall testing strategy – effectively adding more time to do what you do best!

Learning Outcomes:
  • Why is there Never Enough Time?
  • What Testing Activities do we Emphasize?
  • Where do we Find Inefficiencies?
  • How do we Fix them?
  • What would you do with that Time Saved?


avatar for Melissa Tondi

Melissa Tondi

Quality Engineering Leadership, E*TRADE
Melissa Tondi has spent most of her career working within software testing teams. She is the founder of Denver Mobile and Quality (DMAQ), past president and board member of Software Quality Association of Denver (SQuAD), and Sr. Manager of Quality Engineering at E*TRADE, where she... Read More →

Wednesday August 7, 2019 10:45 - 12:00 EDT
Chesapeake 1/2/3

15:45 EDT

Hey, You Got Your TDD in my SQL DB! (Jeff McKenzie)
Limited Capacity seats available

When should we test our data? From an application development perspective, a unit test against a database isn't a unit test at all. Which makes sense -- connected systems introduce overhead and dependency, both of which reduce stability and decrease productivity during test-driven development (TDD). But if we wait for integration testing, critical functionality can get missed. In this session, we will discuss strategies for filling the data testing gap, directly within a Microsoft SQL Server environment. If you do a lot of work in T-SQL but aren't familiar with TDD, you'll learn the why and how of test-first development. If you're accomplished with unit tests, but never tried them in your database, you'll learn how to apply familiar concepts like setup, mocking, and assertion. We'll spend most of our time walking through a solution based on a real-world project, specifically using the open source tSQLt database unit testing framework.

Learning Outcomes:
  • what TDD is
  • benefits of TDD
  • the practice of TDD
  • how to obtain and install the tSQLt unit testing framework in SQL Server
  • how to write unit tests in SQL using the tSQLt framework
  • experience walking through an example scenario


avatar for Jeff McKenzie

Jeff McKenzie

Practice Manager, Insight Digital Innovation
Jeff McKenzie has worked in software development for nearly twenty years, in both freelance and full-time capacities, as a developer and team leader. He enjoys helping others solve problems through technology, whether it's the small business getting on the web for the first time... Read More →

Wednesday August 7, 2019 15:45 - 17:00 EDT
National Harbor 3
Thursday, August 8

09:00 EDT

Forget the QA! We’re a Cross-Functional Team!* *(But who has time to test anything?) (Marianne Erickson, Julie Clooney)
Limited Capacity filling up

In a perfect world, every Agile team has its own QA lead and a tester or two, with time to execute continuous testing and access to end users for extensive interviews. In this perfect world, teams practice cross-training so that during peak test times, additional team members can take on testing roles, thus adding new eyes to the process and augmenting test results.
In the real world, good testing practices often fall prey to decreasing budgets and to testing bottlenecks when multiple user stories enter the testing queue at the end of the sprint. In the budget-centric organization, often the testers are the first to go when finances demand a reduction in teams. Once the “just get anyone to do the testing” mentality creeps into an organization, quality becomes relegated to that proverbial back burner. Eventually, someone gets burned. When a team is fortunate enough to retain its testers, they find themselves overwhelmed with work at peak test times (usually near the ends of sprints or just before deployment) and attention to detail declines.
With nearly 30 years of combined experience between us, we (and we are Julie Clooney and Marianne Erickson) have compiled tools to help mitigate the effects of budgets and bottlenecks in the testing process. Our tools help build team enthusiasm for quality and a Whole-Team, Agile approach to testing. Learning outcomes in five areas will provide our session participants with a toolkit they can use to facilitate improved, continuous, and collaborative test strategies for their teams.

Learning Outcomes:
  • Participants in our session will learn how to implement a “Whole Team Approach” toward testing, and take away a toolkit of ideas to practice with their own Agile teams.
  • We will concentrate on five focal points of Agile Testing:
  • 1. Culture and Mindset: Creating a Whole Team Approach
  • 2. Categories of Testing: Who can, who can’t, and cross-training
  • 3. Roles and Responsibilities
  • 4. Test Strategy and Planning
  • 5. UX and UI: The user-centric tester


avatar for Marianne Erickson

Marianne Erickson

Sr, Consultant at Express Scripts, Daugherty Business Solutions

Thursday August 8, 2019 09:00 - 10:15 EDT
National Harbor 3

14:00 EDT

Help! I am Drowning in 2 Weeks Sprints...How do I determine what NOT to Test! (Mary Thorn)

Sometimes we allow ourselves to drown in work… We hear it all the time: we as testers complaining at retrospectives to our teams that we do not have enough time to test everything. We, as testers, often work overtime the last week of a sprint to ensure the definition of done is accomplished. Why do they do this? Why do we, as testers, enable the bad behaviors of “Scrummerfall” or a lack of whole-team ownership of quality? In this talk you will learn techniques that allow you to test smarter, not harder, and enable the team to have better conversations that make it clear what they are testing in the sprint. Most importantly, we want you to come out of this session being able to answer the question, “What are you not going to test this sprint?” As well as, how do you receive buy in from stakeholders on such "risk based" approaches. You will be able to take home 5 practical risk based approaches that allow you to swim, not sink, by focusing your own and your team’s efforts on testing the right thing.

Learning Outcomes:
  • The attendees will come away with five risk based testing techniques to take back to their scrum teams teach them in ways limit scrummerfall
  • - 3 amigos
  • - Test Ideas
  • - Test Case Gaps
  • - Pareto
  • - All Pairs
  • Team based conversation techniques
  • Stakeholder buy in on the risk based decisions


avatar for Mary Thorn

Mary Thorn

Agile Practices Lead, Vaco
During her more than 20 years of experience with financial, healthcare, and SaaS-based products, Mary Thorn has held VP, Director, and Manager level positions in various software development organizations.A seasoned Leader and Coach in Agile and Testing Methodologies, Mary has direct... Read More →

Thursday August 8, 2019 14:00 - 15:15 EDT
National Harbor 4/5

15:45 EDT

Rethinking quality and the engineers who protect it (Andrew Smelser)
Limited Capacity seats available

Testing software is a critical responsibility, but testing is not a synonym for quality. Shifting your approach to software quality from black box testers, to quality coaching could lead to delivering higher quality products. In this talk, learn about QA coaching and what value these coaches can add to development teams.

Learning Outcomes:
  • An introduction to a new model for QA + tips for collaborating with developers and coaching quality.


avatar for Andrew Smelser

Andrew Smelser

Quality Coach, Eventbrite

Thursday August 8, 2019 15:45 - 17:00 EDT
Chesapeake A/B/C

Filter sessions
Apply filters to sessions.