Save Our Scrum
Ken Schwaber, a co-creator of scrum, says that only 25% of teams trying Scrum actually realize the gains they had hoped for. Another informal poll shows teams callling themselves "Scrumbut", "Scrumerfall", or "Scrumish" than actually claim to successful!
It is as if something conspires to make Scrum ineffective.
Let's get real. Scrum is designed to expose problems. It does not, by itself, solve the problems. In theory, Scrum provides a framework for the team to work through the solution themselves. In practice, politics, rhetoris, and lack of training often get in the way.
This talk is about understanding common Scrum problems and breaking through ruts.
In this conversation Matthew Heusser and Wade Wachs will discuss the heart of Scrum, where it goes wrong, how testing can enable Scrum success - and how team members can improve their visibility and role while contributing to Scrum and team long-term success.
Building the Business Case for ATDD TestingJoseph Ours
schedule 2 years agoSold Out!
Software development teams are under increasing pressure to deliver applications cheaper, faster, and better. As a result, many groups are using some kind of iterative or "agile" development methodology, all with the promise to achieve software faster, better, cheaper. However, shorter product releases cycles mean greater opportunity and need for regression testing. This creates resource management challenges as the burden of regression testing grows and competes with resources needed to test new feature functionality. As a remedy for this situation, many have proposed the use of test automation in the form of Acceptance Test Driven Development methods. Many managers, and even front line testers, tend to resist this approach. How can we diffuse the tension so that management will understand the necessary investments and the testers on the front line will take up the challenge with enthusiasm?