|
||||
|
“We can’t automate everything. It costs too much.” I’ve heard that concern—that test automation costs too much—multiple times when talking with folks in the middle of an Agile transition. They know that automated regression testing is important in an Agile context. But they’re concerned about the costs. And they can’t even imagine getting to a point where all . . . → Read More: Why Test Automation Costs Too Much Not everyone agrees with my definition of Agile. Dave Nicolette commented that he thinks my definition actually describes Lean. He defines Agile in terms of the Agile Manifesto. I replied to Dave elsewhere, but wanted to post my response here too since this is a topic that comes up frequently. I have trouble defining Agile solely in terms of . . . → Read More: Why I Define Agile in Terms of Results A few days ago, I tweeted that I was looking for nominations for events for an Agile timeline and am extremely grateful for all the responses I received. The request was for the keynote talk that I just presented at PNSQC. I’ve had several requests for the timeline that resulted, so I figure the easiest (and therefore . . . → Read More: My PNSQC Keynote with Agile Timeline I’ve been hinting about a new venture on Twitter, and it’s time to explain what’s going on. I’m in the process of opening a new office. Or rather, my company, Quality Tree Software, Inc. is opening a new space in our current building in Pleasanton, CA. It’s 1200 square feet of open-layout-Agile-goodness. When it’s done, it will be . . . → Read More: Creating an Immersive Agile Training Space I think it’s important to define “Agile” when I talk about “Agile Testing.” Agile is one of those capitalized umbrella terms, like Quality, that means many things to many people. And given that Agile Testing involves testing in an Agile context, it’s hard to talk about it if we have not established a shared understanding of the . . . → Read More: Defining Agile: Results, Characteristics, Practices A colleague recently described the requirements process in his (non-Agile) organization to me. In their process, the business people talk to the business analysts who talk to the systems analysts who give requirements to the programmers. As he was explaining all this, I couldn’t help but reflect on all the possible points of failure. I’ve seen conversations around . . . → Read More: Lost in Translation Certification of software professionals has been a hot topic for quite a while. At least 15 years. Maybe longer. I keep hoping that the whole thing will blow over. But it hasn’t. And it’s not going to. Too many people have too much of a financial stake in the success of certifications. Certification customers, including individuals and their . . . → Read More: Agile Certifications I was honored to be included on the lunch and learn panel at the Software Quality Association of Denver (SQuAD) conference this week. One of the questions that came up had to do with triaging bugs in an Agile context. Here’s my answer, in a bit more detail than I could give at the panel. The short . . . → Read More: Handling Bugs in an Agile Context Shameless plug alert! Dale Emery and I are offering the 3-day Agile Testing Series of classes in Pleasanton, CA on April 22 – 24, 2009, and in Portland, OR on April 28 – 30, 2009. We’ve structured the three days as a la carte offerings. You can take one, two, or all three days. Day 1 is “Adapting to . . . → Read More: New Public Classes Announced It had already been a frustrating morning. Too little sleep, and too little coffee. Squabbling kids. Traffic. Parents who didn’t know how to use the carpool lane at school and just stopped in the middle of the road, holding up traffic for 5 minutes while Junior fetched his lunchbox from the depths of the giant SUV. . . . → Read More: The #notagile Twitter Stream |
|
|||
|
Copyright © 2010 Test Obsessed - All Rights Reserved |
||||
Popular Posts