In agile, everything we do is an experiment. Product development is no different. We think we know what the customer wants, and the customer thinks they know what they want, but it turns out we're all wrong! To get to validated discoveries about our features, we must understand how to write a better hypothesis for our development experiments. This session focuses on challenging the mindset that we are validating options during our experiments. Natalie Warnert will show you how to eliminate options that don't work with data and feedback by looking at your product hypotheses as tests that cannot be proven. This way of testing your product design preserves options and helps to eliminate choosing the wrong thing because of your confirmation and customer biases. Natalie will present key metrics you can use to help guide your experiments and practical ways to look at your ideas as something to test, rather than validate.

You’re a professional project manager or ScrumMaster. Your software development projects never fail because you follow all the best practices. Right? We all know better. Unfortunately, many projects fail, and they fail due to issues outside the team's control. The reality is that we need...

As companies realize the need for rapid application development, they are embracing DevOps methodologies. But implementing DevOps practices without establishing a culture of quality often results in lower quality software or a poor customer experience, which impacts the business bottom line.

Quality starts with requirements. In small to mid-size companies, it is not uncommon for the communication chain to be broken. Florin Ursu shares ways to avoid miscommunication through a streamlined process in which requirements are communicated to both developers and testers...