Conference Presentations
|
Risk Identification, Analysis, and Mitigation in Agile Environments Although risk identification, analysis, and mitigation are critically important parts of any software project effort, agile projects require non-traditional techniques that are much quicker and easier to use than classical risk techniques. James McCaffrey focuses-not on theory-but on realistic risk analysis methods agile teams can readily implement with lightweight tools. James explains and demonstrates how you can employ taxonomy and storyboarding methods to recognize project meta-risks and identify product risks throughout the development lifecycle. Using “central moment” and “PERIL” techniques, you'll learn to analyze these risks and develop management and mitigation strategies dynamically, while the project is underway. |
James McCaffrey, Volt VTE
|
|
 |
Simplify Your Combinatorial Testing Combinatorial testing is effective for testing multiple, non-sequential inputs that affect a common output in complex software. But, it's easy to misapply it or become a slave to the output. Learn to overcome limitations and benefit fully from this technique. |
|
|
Us Against Them How well does creating an opposing force serve to deliver on shared objectives within the same organization? A stronger argument may be to teach both business stakeholders and delivery personnel to reach across organizational boundaries to share not only the vision but also the methods used to achieve it. |
||
 |
Slicing Requirements for Agile Success Agile teams need to analyze product requirements in enough detail to build, test, and deliver the right requirements in short time frames. For the many teams that struggle to define "just enough, just in time” requirements, here's help. |
|
|
Executable Specs w/ FitNesse Selenium "Executable Specifications with FitNesse and Selenium." |
Dawn Cannan, DocSite LLC
|
|
|
Managing Your Analysis Debt What is your project's analysis debt load? What's the difference between good and bad analysis debt? What are causes and remedies for such debt? Mary Gorman and Ellen Gottesdiener explore the concept of analysis debt and consider strategies for prudent investing. |
||
|
The Key to Good Interviewing The foundation of any successful assessment is interviewing a diverse cross section of the staff. But asking the right questions and asking those questions right makes all the difference in the quality of information you can elicit from your interviewees. |
||
|
STAREAST 2006: All I Need to Know about Testing I Learned from Dr. Seuss Through the stories and parables of Theodor Geisel, we can learn simple, yet remarkably powerful approaches for solving testing problems. In a tour of common issues we encounter in testing-test planning, staff training, communications, test case design, test execution, status reporting, and more, Robert Sabourin explains how you can apply lessons from the great books of Dr. Seuss to testing. Green Eggs and Ham teaches us combinations; Go, Dog, Go teaches us the value of persistence; Because a Little Bug Went Kachoo teaches us about side effects, chaos, and risk management. Others such as Hop on Pop, Marvin K Mooney, I Can Read with My Eyes Shut, and Inside Outside UpSide Down all have important lessons about how to get things done on software projects. Learn some simple truths and take away some heuristic testing aids to become a more productive and effective tester.
|
Robert Sabourin, AmiBug.com Inc
|
|
|
Risk-Based Testing in Practice The testing community has been talking about risk-based testing for quite a while, and now most projects apply some sort of implicit risk-based testing approach. However, risk-based testing should be more than just brainstorming within the test team; it should be based on business drivers and business value. The Test team is not the risk owner-the products' stakeholders are. It is our job to inform the stakeholders about risk-based decisions and provide visibility on product risk status. Erik discusses a real-world method for applying structured risk-based testing applicable in most software projects. He describes how risk identification and analysis can be carried out in close cooperation with stakeholders Join Erik to learn how the outcome of the risk analysis can-and should-be used in test projects in terms of differentiated test approaches. |
Erik van Veenendaal, Improve Quality Services BV
|
|
|
STAREAST 2006: Testing Outside the Bachs Simply put, exploratory testing means designing your tests as you perform them. When it's done well, it's a fantastically productive and rewarding approach to testing. However, to do it well requires training, practice, and discipline. Lecture presentations about exploratory testing are a poor substitute for seeing it and doing it. So . . . plan to bring your laptop to this session and test along with James Bach and Jon Bach as they demonstrate exploratory testing in a live testing workshop. Participate or just observe as exploratory testing is performed in real time with play-by-play and color commentary. Learn how to bring structure to this apparently unstructured testing method. See if you can find bugs that they do not find as you test "outside the Bachs"! |
James Bach, Satisfice, Inc. and Jon Bach, Quardev Laboratories
|
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.