LS1413 - Infusing Testing into Development throughout the Application Lifecycle
DennisSchultz 100000VA98 Visits (1066)
Yes I am about to use this blog for a shameless plug for my Innovate session. But, I would like this to be more than just a shameless plug entry. Hopefully those who attend the session (some of you will actually attend, right?) can carry on a conversation about the Developer/Tester relationship and how to better collaborate in the comments of this forum after Innovate.
My friend and teammate Tim Feeney and I will be presenting a session at Innovate 2012 on Monday at 4:15pm in Southern III in the Dolphin entitled Infusing Testing into Development throughout the Application Lifecycle. That title might require some explanation. I'm a Testing guy. I've been in the Testing game for more years than I care to admit. Back in the day, I built automated test equipment for an aerospace company. The practices of the day were pretty much waterfall. Engineering built the avionics boxes with little input from those of us that had to test them on the flight line or in the battlefield. The first we saw the boxes were when they threw them over the wall to Field Testing (Well, they weren't literally thrown. Those things are expensive.). That sort of methodology just doesn't work these days. The pace of development and innovation is so fast that you can't just do big bang testing late in the cycle. Testers need to be involved early on so that they can know what's coming and so they can provide input so things can be built so that they are testable.
So Tim and I will be showing you how you can use the IBM Rational Collaborative Lifecycle Management solutions (mainly Rational Quality Manager, Rational Team Concert, Rational Requirements Composer and Rational Functional Tester) to get QA tuned into the process earlier, keep QA engaged as changes occur and reduce the time it takes to get critical testing results and information back to Development. This isn't us versus them anymore. QA, Development, and the Line of Business all need to be on the same team executing from the same playbook. Come hang with us for an hour or so and see how we can break down some of those silos and collaborate better.