In a conversation about product quality, the product owner said, “If the testers found the problems faster, we would be done faster.” The tester said, “If the developers didn’t put so many problems in, we’d be done by now.” The developer said, “If you didn’t pressure me so much, I could have done a better […]
In Part 1, I discussed the agile project system. In Part 2, I discussed the tester’s job in agile. In Part 3, I discussed expectations about documentation (which is what the original question was on Twitter). In this part, I’ll talk about how you “measure” testers. I see a ton of strange measurement when it
In Part 1, I discussed how an agile approach changes testing. In Part 2, I discussed how the testers’ job changes. In this part, I’ll talk about expectations. Since the developers and testers partner in agile, the testers describe their approach to testing as they work with developers on the code. (This is the same
Last week, I attempted to have a Twitter conversation about agile and testing. I became frustrated because I need more than 140 characters to explain. This is my general agile picture. For those of you can’t see what I’m thinking, the idea is that a responsible person (often called a Product Owner) gathers the requirements
In Part 1, I discussed the project system of agile. In this part, I’ll discuss the need for testing documentation. In a waterfall or phase-gate life cycle, we needed documentation because we might have had test developers and test executors. In addition, we might have had a long time separating the planning from the testing.
If you read my Three Alternatives to Making Smaller Stories, you noticed one thing. In each of these examples, the problem was in the teams’ ability to show progress and create interim steps. But, what about when you have a “wicked” problem, when you don’t know if you can create the answer? If you are
When I was in Israel a couple of weeks ago teaching workshops, one of the big problems people had was large stories. Why was this a problem? If your stories are large, you can’t show progress, and more importantly, you can’t change. For me, the point of agile is the transparency—hey, look at what we’ve
Did you see Dwayne Phillips’ post today, Adding People to a Late Project? Dwayne says: Adding people to a late project only makes it later. We have known this for decades. Especially in the article he refers to, it seems as if there might be no end to the number of people added. Did anyone
I was in the midst of an assessment when the CIO came to me, and shut the door. “I have a serious question for you.” I nodded for him to continue. I put aside my papers to show him I was providing him my undivided attention. “I’m thinking of offshoring all the testers. What do
I delivered a keynote at Let’s Test in Sweden last week, “Becoming a Kick-Ass Test Manager.” A lovely gentleman, Aleksis Tulonen, recorded the audio. Thank you, Aleksis! I attempted to marry the audio to the slides. I was not successful. However, the audio is up on slideshare. You can download the slides, page through them