One of the more popular software testing methodologies today is Agile Testing. Agile allows closer collaboration between the developer, tester and business owner. This methodology allows a workable product that could be deployed into the production environment at the end of the sprint. Typically most companies have a 2 to 4 week sprint. There are usually a product owner, a scrum master and a team that makes up the 6-8 member team. The team members usually consist of developers and testers. If done right, agile testing can be an effective approach to help move quality code to production. The challenge is that there are many different variations of the Agile methodology. Most companies practice a hybrid or customized Agile approach. Since the Agile approach can be customized so many ways, there is not a one size fits all approach. Agile testing requires close collaboration and constant communication with other teams. Perhaps one of the greatest misconceptions about Agile testing is that little to no documentation is required. I have seen situations where development prefers to have less than acceptable documentation for the agile tester. While I agree that the tester does not need a full blown requirements document, there needs to be adequate information through at least a story card that will provide the tester with enough information to create a test case. My company is currently working towards less waterfall projects and more agile projects and I believe it is a move in the right direction, but it is a fundamental shift from what everyone is used to. We have had a training company that recently came in and provided some agile training and I highly recommend the investment into an onsite trainer so that everyone will understand the basic methodology. We are customizing from pure agile into a more hybrid approach in order to meet our business needs. We are going to have 8 sprints going at a time for a conversion project we are undertaking so it is important that the organization is ready to go and everyone understands the role they will play. We are optimistic that using the agile methodology, the business the software they need and be able to provide input along the way versus having to wait towards the end of the life cycle.
- Think You Know QA? Challenging 16 Software Testing Myths
- (no title)
- API Testing 101: A Comprehensive Guide for Beginners
- 500 ChatGPT Prompts
- 10 Keys to Agile Transformation
- ISTQB Agile Tester Certification Exam Training Course
- Impact of COVID-19 on Software Testing Industry
- When Test Automation ROI Doesn’t Make Financial Sense
- What is the Cucumber Testing Tool?
- What is Gherkin Framework for Behavior Driven Development?