Agile2015 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 3


The Product Owner's Guide to Writing Acceptance Tests (Paul Carvalho)
Limited Capacity seats available

Aristotle once said "Well begun is half done." User Stories need 3 C's to get the team going, not two. Don't skip the Confirmation/Acceptance Criteria!
There is help for Product Owners (or BA's) who want to write good acceptance criteria. ATDD and BDD suggest writing these acceptance tests in Gherkin notation. Given-When-Then may seem odd or intimidating at first glance, but it gets easier with understanding and practice. Writing good acceptance criteria for User Stories requires looking at Requirements in a slightly different way.. and maybe picking a tester's brain too.
Join Agile Coach and Testing consultant, Paul Carvalho, as he shares insights, models and tips to help you embrace the art of writing good tests to help get your teams started on the right track. Learn new ideas and techniques to help you get the most from your Product Backlog Refinement activities to benefit your teams and customers.
Learning Outcomes:
  • Help Product Owners write clear acceptance criteria for user stories
  • Overcome the fear of Given-When-Then format for acceptance criteria
  • What Testers should know that they don't know about how they can help their teams learn to test better

avatar for Paul Carvalho

Paul Carvalho

Agile Coach, Trainer, Quality Driven Inc.
Paul is a Testing expert, Agile coach, interactive teacher, Rubyist, comic relief, and efficiency enthusiast with over 20 years of experience in various domains. A Quality consultant by trade, Paul helps companies deliver world-class value. Beware: his eyes sparkle when he talks about... Read More →

Monday August 3, 2015 14:00 - 15:15
Chesapeake 7/8/9


Do the tester role survive in a test infected team? (Juan Gabardini)
Limited Capacity seats available

In a test-infected team everybody takes part on testing and quality. So, the question is: which testing perspectives and skills the team should develop? Should some members remains as 'testers'? Are those perspectives and skills the same as in the traditional tester role?
Testers were often second-class citizens in traditional teams. When evolving to agility, some feel they should become programmers or become obsolete because, as everybody test, then the tester role is not needed anymore. In other teams, someone in the team keep the ‘tester’ tag, but it is unclear what they should do.
In this session I will present some ideas on the tester role on both traditional and test infected teams and open a discussion to answer the above questions, not as a black or white choice but as context-aware response.
We will also discuss how to bring the test mindset and skills to the whole team.
Learning Outcomes:
  • Skills and mindset in a traditional tester role
  • Skills and mindset in the tester role in a test infected team
  • Heuristics, books, and exercises to develop testing skills and mindset in the whole team.


Juan Gabardini

Agile Coach, Kleer

Monday August 3, 2015 15:45 - 17:00
Potomac 5/6
Tuesday, August 4


Example Mapping (Matt Wynne)
Limited Capacity seats available

In this session I'll teach you a simple, practical technique that you can use to break down any user story.
BDD and ATDD enthusiasts already know how useful it is to have the three amigos - tester, product owner and developer - meet to discuss a new user story before they start development. What many teams don't have is a clear structure for these conversations. Sometimes they can take a long time, or drain the group's energy by going round in circles.
Over many years of teaching hundreds of people about BDD, I've developed a simple practical technique that will allow you to break down a story in about 25 minutes. All you need is a pack of coloured index cards, some pens, and a curious attitude.

Learning Outcomes:
  • the purpose of a three amigos session
  • a practical technique for visualising what you know, and don't know about a user story
  • the difference between rules and examples

avatar for Matt Wynne

Matt Wynne

Co-founder, director, Chief Mountaineering Officer, Cucumber Limited
Matt is one of the world's leading BDD practitioners. A programmer, coach, trainer and popular international speaker, he was as invited to join the Cucumber core team in 2009. Together with Aslak Hellesøy, the creator of Cucumber, he's co-author ofThe Cucumber Book, Behaviour-Driven... Read More →

Tuesday August 4, 2015 15:45 - 17:00
National Harbor 3
Thursday, August 6


Hands-on manual UI testing workshop (Emma Armstrong, Lisa Crispin)
Limited Capacity seats available

Most of us are faced with User Interfaces to test but how many of us are taught to actually test them? Have you ever forgotten to test something about a UI or have you had to cover environments where you are less familiar with system variations that may affect the application.

This workshop will look at both the theory and practice of testing User Interfaces. Using physical examples we will look at how the environment changes the tests you need to consider.
Working together through these exercises, you will strengthen your own testing skills library that you can draw from in the future.
Learning Outcomes:
  • How to test a User Interface while it’s still in design
  • User Interface considerations to be aware of
  • Oracles and Heuristics to consider for testing User Interfaces
  • Environmental Variations that affect User Interfaces

avatar for Emma Armstrong

Emma Armstrong

Mrs, Towers Watson
Emma Armstrong is a test engineer and has been baking quality into software since 2000. In that time she has gotten her hands dirty with both manual and automated testing and had the opportunity to dig into everything from compilers to web applications.She has worked with most methodologies... Read More →
avatar for Lisa Crispin

Lisa Crispin

Co-founder, Agile Testing Fellowship
Lisa Crispin is the co-author, with Janet Gregory, of More Agile Testing: Learning Journeys for the Whole Team (2014), Agile Testing: A Practical Guide for Testers and Agile Teams (2009), the LiveLessons "Agile Testing Essentials" video course, and “The Whole Team Approach to... Read More →

Thursday August 6, 2015 09:00 - 10:15
Potomac D


Visual Testing: It’s Not What You Look At, It’s What You See (MIke Lyles)
Limited Capacity seats available

How many times have you driven all the way home, only to realize you didn’t remember anything from the drive. Your mind was in a different place, and you were driving on autopilot. Or maybe you walk out to your garage and get in your car every day and are so used to the surroundings that you don’t notice that something has been taken or moved to a new location. When our eyes are so familiar with the things we see every day, our brains are tricked into believing that there is nothing that has changed.
In the popular TV show, “Brain Games”, we find many exercises where you, the audience, are asked to pay attention and focus on what is happening. That simple focused attention gets the majority of people in trouble, because the art of focusing on a specific area or activity prohibits the audience from seeing things that are going on around them. This “inattentional blindness” causes key details to be missed. Your brain is the most complex tool that you will ever have in your possession. However, with a highly complex tool comes the need to ensure that it is used appropriately and to its full potential.
In the testing profession, such focused concentration, leading to “inattentional blindness” can be detrimental to the success of the product being delivered. As testers, we must find a way to constantly challenge our visual images and prohibit our brain from accepting that there are no changes which could impact the quality of the product. It is critical to be aware of the entire surroundings of the testing activity and to be able to recognize and call out changes that may be easily overlooked without an attention to detail.
In this session, Mike Lyles will challenge the audience to literally “think outside the box”. The audience will be given specific exercises to show how that the human mind sometimes overlooks details when they seem visually insignificant or unrelated. We will examine how testers can become better prepared for such oversights and discuss strategies that can be used immediately in your organizations. The key to eliminating the risk of oversight and missed problems is learning how to identify the areas where you may have originally ignored a focused effort.

Learning Outcomes:
  • Key Takeaways:
  • • An understanding that no matter how good we believe we are as testers, we have to realize that there is the possibility of being so familiar with a product that our eyes do not notice changes that sneak in.
  • • Tips to recognizing patterns and potential gaps that many visual testing activities may miss.
  • • Techniques that can be used in becoming a better visual tester.

avatar for Mike Lyles

Mike Lyles

DIrector of QA & PM, Bridgetree
Mike Lyles is a Director of IT, international speaker, and author. He has over 25 years of IT experience in software development and testing. His motivational book, “The Drive-Thru is Not Always Faster” was released in Nov 2019. Find out more on the book at www.TheDriveThruBo... Read More →

Thursday August 6, 2015 10:45 - 12:00
National Harbor 13
Friday, August 7


“Follow-your-nose” testing – questioning rules and overturning convention (Christin Wiedemann)
Limited Capacity seats available

Is testing really keeping up with the advances of software development? Are our testing approaches evolving as quickly as the new technologies, or are we being left behind, using the same methods and techniques as we did a decade ago?
Testing needs to get more innovative, find new ways to test more efficiently and effectively, and to better adapt to each unique context. The first step is to realize that testing is not about finding answers, but about asking questions. Nobel laureate Dr. Michael Smith advocated “follow-your-nose research” in his field, biotechnology; he was willing to pursue new ideas even if it meant that he had to learn new methods or technologies. Similarly testers should do “follow-your nose testing”, exploring new approaches and questioning old habits.
This workshop suggests an approach for test planning that encourages innovation and overcomes barriers to quality. Through a cogent discussion of ideas around brainstorming, collaboration and creativity, you are provided with new insights that can help you revolutionize the test industry! Working in smaller groups we explore different examples of test challenges we have experienced ourselves, covering topics ranging from tools and environments to methodologies and teams. Using our new tools for encouraging innovation through collaboration, we try to come up with revolutionary suggestions for how to address these challenges. Focusing on asking the right questions, we might also come up with a few answers.
Learning Outcomes:
  • Testing needs to continuously re-invent itself to keep up with the advances of software development, which means we need to creative a collaborative environment that encourages creativity and innovation.
  • Takeaways:
  • + A presentation of ideas about why testing needs to get more innovative
  • + Why classic brainstorming doesn’t work, and how to build creative, innovative teams
  • + Tools to re-invent testing practices
  • + An understanding of what “follow-your-nose testing” is, and how to apply it on any software development project

avatar for Christin Wiedemann

Christin Wiedemann

Exec. VP, PQA Testing
After finishing her Ph.D. in Physics at Stockholm University in 2007, Christin Wiedemann started working in IT as a software developer, but soon discovered that she found software testing to be more interesting and challenging. Changing careers, she started working as a tester, and... Read More →

Friday August 7, 2015 09:00 - 10:15
Chesapeake 7/8/9