Agile Testing and Development: A Case Study

“Going agile” has a positive reputation of allowing teams to collaborate while allowing more room for flexibility, adaptability, and transparency throughout the product development process. However, this doesn’t always mean that it results in a smoother and error-free software development and testing process.

This month’s Meetup presentation takes an insightful look into a real world agile project that went horribly wrong from the point of view of Bob Cook, Senior Product Development Manager at Sophos.

Despite doing all the things that the Agile Manifesto says to do, the project encountered many unexpected and critical defects late in the development schedule. A project that was projected to be complete in four months took six months to deliver.

Want to know what happened and why? Want to hear what this team did under the difficult circumstances? Interested to learn how your team might avoid a similar fate? The beauty of a software testing network is that we can learn from each other’s experiences, so come out on Wednesday, November 2nd to join the discussion.

As always, feel free to contact us with any comments or questions you may have beforehand, or simply be ready to share them during the Meetup. We look forward to seeing you!

Bio: Bob Cook, Senior Product Development Manager

Bob Cook is a Senior Product Development Manager at Sophos where he has spent the last ten years in a variety of roles delivering quality software with a team of very talented developers, test analysts, and test automation engineers. The years at Sophos have been educational and have taught him why everyone should be concerned about software quality and security. Previously, Bob spent 12 years at Creo learning how to build high performance software development teams from the ground up.