Lightning Talks
Presented by 8-10 of your fellow QASIG participants
The format was the “lightning talk” where each of the speakers knew that they only had five minutes to present their idea (one at a time). Each speaker had a severely limited time-frame, but could speak about anything related to testing in that time – a new idea for status reporting or measurement, a lesson they learned on a project, an experience report about a new technique they tried, or a general test principle they want to share.
Lightning Talk Speakers, Topics, and Slides (where submitted):
| Jim Hancock, Director of Quality, IT and Customer Delivery at Geospiza | Creating a Quality Index | Most software development has become “agile,” but CMM, CobiT, PMBOK, Malcolm Baldridge and other quality process metric deployments are still large and complicated. Jim will discuss how to deploy software quality metrics that meet the following criteria: objective, non-obtrusive, flexible, repeatable, consistent, holistic, efficient and inexpensive. Most importantly, the Quality Index will provide an accurate assessment of risk and quality within any SDLC upon which logical deployment decisions can be made. |
| Jeremy Lightsmith, Seasoned Agile Coach, Trainer and Facilitator | What’s Your Conflict Management Style? | There is a model of the way people respond to conflict that looks like the attached picture. I thought it would be cool to introduce it and talk about why it’s helpful and how to use it. There’s also a related questionnaire that I can leave for everyone to see how they score. |
| Jeff Brewster, Grameen Foundation | Untethering a Test Lab | Do you have a performance test lab that can only be used onsite or has expensive software? Been forced to share lab resources due to cost or space concerns? We’ll share the steps the Mifos testing team used to move their performance test lab to the cloud. |
| Tim Tapping, SDET, Expedia | How to sprint as Agile/Lean QA on the feature team | QA has challenges if we are used to building out test plans from extensive documentation which is not present in a agile/lean development environments. We need to engage early in the iteration and help the team understand that ‘quality deliverables’ are a team activity. Drawing on my recent experience at an acquired startup which was an agile shop, I can share techniques that worked for us and pitfalls to avoid. |
| Jon Bach, Manager for Corporate Intellect, Quardev, Inc. | Tested | I’m working on a talk for Ignite (Seattle) that has a likelihood of being chosen. How much of a likelihood depends on well I can define this talk about our industry to the technical masses. I could use some feedback. |
| Lanette Creamer, Test Lead, Adobe Systems | Agile Testing Ninjas | If Adam Goucher learned everything he knows about testing from Pirates, why does Lanette insist that Ninjas hold the key? What is it about stealth, speed, discipline, and skill that translates well to Agile testing? |
| Jim Benson, CEO, Modus Cooperandi | Kaizen or Death | If we don’t improve, we stagnate. If we stagnate, we perish. Life requires change, renewal, and innovation. Evolution is innovation. In life, in business, in everything, we must continuously improve. In 5 short minutes, Jim Benson will change your life through the Japanese concept of Kaizen (continuous improvement). |
| Gary Knopp, SDET, Attachmate | Chow, Expand Your Idea of Dogfood | This talk will be a quick case study of how we were able to break out of what seemed like an obvious test strategy (using or extending our existing test system) and move to a lighter-weight, component-based test approach. This new approach includes testing the component in isolation, the usage of the component in isolation, and then the system as a whole. Ultimately we were successful in using this strategy and even completed the testing 2 weeks early. |
| Michael Wolf,Perl Trainer, evangelist, programmer, community member, town crier… | TAP – Test Anything Protocol |
