Do agile projects become the brunt of cubicle Dilbert jokes? Scott Ambler confronts Scott Adams.Agile projects are both interesting and challenging, especially for testers. Too often these projects and their processes are misunderstood or misapplied. What's most uncomfortable to testers is what appears to be a complete abandonment of any sort of serial testing flow.Moreover, the lack of upfront specifications for all features and functionality seems to be a complete affront to not only testing best practices but also common sense. Suffice it to say that a lot is misunderstood about Agile testing.
Unfortunately this misunderstanding of what can be an effective development and testing process ends up being the brunt of cubicle jokes.
Now I wouldn't say that testers assigned to agile projects see things as comically as Dilbert
, but it can be confusing for testers if the development processes don't include them. For this very reason, and based on some past experience, I was happy to find an article, titled Agile Testing Strategies, that spoke to agile testing specifically. Of all the articles I've read on agile development, this one made the most sense to me as a tester.The author, Scott Ambler, does a great job of relating agile practices to testing and breaks down this subject into 5 parts:
This is a good read and reference document for any tester trying to make sense of their agile development process. I believe that if you spend the time needed to begin to understand the agile process and use Scott's advice and testing process overlays, you'll be able to not only understand your role as an agile tester, but graduate to driving the agile testing strategies for your projects.
0 comments. Add Comment.:
Post a Comment