April 2011 - Agile Testing with Lisa Crispin

The Whole Team Approach in Practice

April 26, 2011 / Lisa Crispin / agile testing, continuous integration, exploratory testing, feedback, learning for testers, pairing, planning, shortened feedback loop, software quality, test automation, Uncategorized, Whole Team Approach / 5 Comments

I’ve just been struggling with a title for this post. Some of my ideas were: “Visibility Taken to New Heights”, “Yes, There Are Teams Who Do This Just Like In the Books”, “A Real Commitment to Continual Improvement”, “Inspiration”, but none of them really capture my amazement at what I saw visiting the team at […]

Practice, Practice, Practice!

April 22, 2011 / Lisa Crispin / agile testing, diversity, learning for testers, Publications, software quality, writing / 2 Comments

The latest issue of Agile Record is out, and includes some terrific articles by Gojko Adzic, Jurgen Appelo, Ellen Gottesdiener, Johanna Rothman, Linda Rising, Catherine Powell and several more – what an incredibly talented and diverse group of contributors! My “Agile Testing in Real Life” column is about practicing our software development (that includes testing) […]

“Our manual testing…”

April 5, 2011 / Lisa Crispin / agile testing, diversity, test automation / 5 Comments

Yesterday I had a call from a participant in my recent BayAPLN session. I completely screwed up and, when I tried to save the phone message, I deleted it, and somehow the number that my phone saved, I could not call back. So, I’d like to try to answer the question, as best I remember […]

Newly Available Online

April 1, 2011 / Lisa Crispin / agile testing, documentation, planning, Publications, Selling Agile, Transitioning to agile / No Comments

My Software Quality Connection article, Selling Agile to the CFO, has been reformatted by ITBusinessEdge into a nice little slide deck. I think it is really easy to read & digest in this new format. I have a new article on TechTarget’s SearchSoftwareQuality.com site, “Getting on the Same Page: How Testers Can Help Clarify Requirements”. […]