Episode 12 - Agile Testing, Part 1

Bob and Josh start their two-part discussion of testing in an agile team.  This first session covers numerous agile testing subjects, from the role of testers in an agile team to test driven development.

If you are viewing this from our web page, please click on the post title above, or here, to download the podcast.


  1. Thank you for your contribution with your experience. It is very interesting and helpful. Maybe you have already mentioned this but maybe there is more to talk about. The subject is engaging your very first scrum project in an organization managed by people who know nothing about scrum or so little that they just don't get it. They don't care to read about it, to hear about it and they rather struggle with their traditional way to fail than give scrum a chance. I'm reading "The enterprise and scrum" by K. Schewaber and although his strategy sounds appropiate, the truth is that
    1. First there isn't that many people in the organization to make all the teams he mentions, or say there isnt enough people willing to honestly do it.
    2. It sounds too long to make scrum happens, too much protocol. The more people involved the slowest to move on.
    3. I have heard many other people (in postcast, youtube, magazines) that say they just started doing it against all odds and made it happen across the organization because they proved it works and prove was what manager needed it to buy on to it. Of course it took a while to spread along the organization but scrum was happening before managers got 100% convinced.

    What do you guys think about it?

  2. One of the key points I make in my "Agile 101" session I give to every team I help with a transition is that Agile adoption is hard and it takes time to get it "right".

    When faced with a large team of folks who don't fully buy into Agile, I often build a super-team of those that DO buy in. Once the other teams start to see this team excel, they start asking that team what they are doing that allows them to be so successful. When that happens, the seed is planted in the organization and, with careful and consistent support, Agile will being to spread.

    You must remember that speed of change in any organization is directly proportional to its size. My favorite analogy to use when making this point is that a personal motor boat can turn around a lot faster than an aircraft carrier. Know the organization you are working with and set your expectations appropriately.

  3. Hi, I know this was a long time ago, but at 21:50, you talk about a sprint test plan 'artifact' that's used as a pre-sprint planning team discussion point. Our team would like to try out this strategy - do you have an example artifact or some further advice on this topic?