Testing against implicit requirements

"When I started my testing career, one of my first bosses told me that ASSUME makes an ass out of u and me. Fast forward almost ten years and those words still ring true."
Even if we have written requirements, we will still be expected to test against hidden aka. implicit requirements. And these are a LOT trickier. After all, how can I test against something that I can't see? How can I test against something that nobody has written down or explicitly told me?
When it comes to implicit requirements, there's a lot of room for mistakes, misunderstandings, and frustrations - but it doesn't have to be that way.
I'll share my experience in testing against implicit requirements and provide tips on how to spot implicit requirements, what shape implicit requirements, and of course how to test against implicit requirements.

What You'll Learn:

• How to spot implicit requirements
• What shapes implicit requirements
• Heuristics on how to test against implicit requirements

About the Speaker:
Nicola Lindgren is a Senior QA Engineer/ QA Manager, based in Malmö, Sweden. She is an international conference speaker, frequent blogger and avid learner of all things testing, agile and leadership.
She has worked on projects in a wide range of industries including Trade, Education, Payments, e-Commerce, Transport and Gaming. She has worked in Agile (Scrum, Kanban), Continuous Delivery and Waterfall environments, in both co-located and distributed teams.
Nicola started two testing meetups (one in Auckland, New Zealand and one in Stockholm, Sweden), has taught software testing courses and run workshops, coached and mentored multiple testers and written for various testing publications. She has also been a co-instructor for the BBST Foundations course multiple times.
She blogs about testing, automation, (personal) development and agile at nicolalindgren.com