Episode description
Episode description
In this episode, we dive into the dynamic world of Agile testing and teamwork, contrasting it with the traditional Waterfall approach. We explore the Agile Testing Quadrants, examining business-facing versus technology-facing tests, and those that support development versus those that critique the product.
Discover what it means to be a “test-infected” developer and how the Product Owner acts as the voice of the customer. We discuss the importance of self-organization within Agile teams and how leaders can influence behavior without dictating solutions. We’ll also tackle the dangers of technical debt, the benefits of test automation, and dispel the myth that Agile means “no planning.”
Finally, we highlight how Planning Poker can be used to effectively estimate user stories.
More Resources: