9:30 – 13:00 Finding Bugs Before Implementation

What if you could spot bug before implementation? Would you be interested in preventing it before it has materialised in code, when it exists as invalid assumption or unknown? What are there tools and techniques that can help you with spotting bugs at such early stage? We’re going to present you several ways of exploring problem space in order to find unproven assumptions, unknown unknowns, and risks, that may manifest as bugs during and after development.

We hear Quality Assurance shifts left, but what does it mean? We will show you how at Spartez and Atlassian we’ve moved to the very edge of left. The left where there is nothing more left. You will learn techniques that support learning process and help grow of mutual understanding of a problem. Equipped with them you will be able together with your colleagues, developers, product owners, other quality specialists, better what kind of problem feature is trying to address. Look at the feature from various perspectives to find issues. Analyse how architecture, user experience and domain meanders can affect the feature implementation and quality, identify relevant risks, and propose ways of managing them. All this accomplished by playing cards!

What are the three biggest takeaways you will take from the workshop?

  • Learn about Quality Assistance model and how it works.
  • Learn what Feature Kickoff is and how to use a deck of cards, as a physical framework one can use to drive the meeting.
  • Learn about feature decomposition techniques which unveil complexity behind feature scrutinised from various perspectives.

How this workshop is going to affect you?

  • You will learn how to shift left and help your organisation benefit from your critical mind and thinking as soon as feature idea is conceived.
  • You will start looking at a feature from various perspective and find even more relevant risks and scenarios worth exploring.

Who is this workshop for?

  • For people of all levels and all roles (Quality Specialist, Tester, Developer, Product Manager, DevOps, Designer, Support). Technical knowledge is not required but is welcomed as exercises will tackle system architecture.