In my third post of “Five Testing Questions with” I have the honor of interviewing Lisa Crispin, co-author of “Agile Testing”, agile testing coach and practitioner. I think Lisa’s answers provide very concrete advice and insightful views on how to improve your work as a professional tester, regardless if you are working on an agile environment or on a more waterfall-like approach.
Tag Archives | Agile
Every Tester needs to be an Agile Tester
Agile Testing is not really a methodology but an approach to managing the process and the approach of your testing team. As such, you can use it regardless of, or even in accordance with, any methodology used by your company to manage their overall project. Read this post to understand why every tester should actually be an Agile Tester!
Switching to Agile Testing, not as simple as changing your t-shirt
In addition to all my other tasks in PractiTest, I am a tester working and consulting on a number of Agile projects. In total I’ve been in testing for over 15 years and doing agile testing for close to 5 years. Here’s a fact some people tend to overlook, just like any other profession, to become [...]
When your job is NOT TO TEST
Ever wondered if you can actually test less and perform other operations that will help your product achieve higher levels of quality in production?
Maybe this is what we should aim for when we define our job as QA (Quality Assurance) Engineers and not as Testers…
You must choose correctly what NOT to measure!
“It’s not only about what you have in your metrics, it’s also about what you leave outside of them.” This is the principle I tried to communicate to an organization I was working with lately.
A short post about the importance of defining your metrics correctly and communicating what you want to achieve and what you are willing to pay for it, up-front and clearly.
Agile Thinking instead of Agile Testing
Is there such a thing as Agile Testing? I’m not sure there is…
You don’t need to work on an agile team to work and test based on an Agile Thinking mindset.
This QABlog is brought to you by:
