|
|
|
STAREAST 2006 Keynote Sessions
Wednesday, May 17, 2006 8:45:00 AM
| |
Your Development and Testing Processes Are Defective
Mary Poppendieck, Poppendieck, LLC
Verification at the end of a software development cycle is a very good thing. However, if verification routinely finds important defects, then something is wrong with your process. A process that allows defects to build up—only to be found and corrected later—is a process filled with waste. Processes which create long list of defects are . . . defective processes. A quality process builds quality into the software at every step of development, so that defect tracking systems become obsolete and verification becomes a formality. Impossible? Not at all. Lean companies have learned how wasteful defects and queues can be and attack them with a zero tolerance policy that creates outstanding levels of quality, speed, and low cost—all at the same time. Join Mary Poppendieck to learn how your organization can become leaner.
Mary Poppendieck A popular speaker and author with thirty years of experience in the Information Technology industry, Mary Poppendieck has managed solutions for companies in a variety of disciplines, including supply chain management, manufacturing systems, and digital media. As a seasoned leader in both operations and new product development, she brings a practical, customer-focused approach to software development problems. In her classes Mary applies lean principles to Software Development problems and offers a fresh perspective on software development processes. Her book Lean Software Development: An Agile Toolkit was awarded the Software Development Productivity Award in 2004. |
| | Wednesday, May 17, 2006 10:00:00 AM
| |
Inside The Master's Mind: Describing the Tester's Art
Jon Bach, Quardev Laboratories
Exploratory testing is both a craft and a science. It requires intuition and critical thinking. Traditional scripted test cases usually require much less practice and thinking, which is perhaps why, in comparison, exploratory testing is often seen as "sloppy," "random," and "unstructured." How, then, do so many software projects routinely rely on it as an approach for finding some of its most severe bugs? If one reason is because it lets testers use their intuition and skill, then we should not only study how that intuition and skill is executed, but also how it can be cultivated and taught to others as a martial art. Indeed, that's what has been happening for many years, but only recently have there been major discoveries about how an exploratory tester works and a new effort by exploratory testing practitioners and enthusiasts to create a vocabulary. Join Jon Bach as he describes the new language of exploratory testing and how it may revolutionize the way it is perceived.
Jon Bach is Corporate Intellect Manager and Senior Test Consultant for Quardev Laboratories, a Seattle test lab specializing in rapid, exploratory testing. He is most known for being co-inventor (with brother James) of Session-Based Test Management (a way to manage and measure exploratory testing) and most recently the developer of Open-Book testing. In his ten-year career, he has led projects for many corporations, including Microsoft, where he was a test manager on Systems Management Server 2.0 and feature lead on Flight Simulator 2004. He has presented at many national and international conferences and is a Program Chair for the 2006 Conference for the Association for Software Testing. |
| | Wednesday, May 17, 2006 4:30:00 PM
| |
Testing: The Big Picture
Brian Bryson, IBM Rational Software
If all testers put all their many skills in a pot, surely everyone would come away with something new to try out. Every tester can learn something from other testers. But can a tester learn something from a ski-instructor? There is much to gain by examining and sharing industry best practices, but often much more can be gained by looking at problem solving techniques from beyond the boundaries of the Testing/QA department. Presented as a series of analogies, Brian Bryson covers the critical success factors for organizations challenged with the development and deployment of quality software applications. He takes strategies and lessons from within and beyond the QA industry to provide you with a new perspective on addressing the challenges of quality assurance.
Brian Bryson At IBM Rational, Brian Bryson is a member of the technical marketing team that plans and delivers IBM Rational's software quality toolset. Prior to joining the IBM Rational group in 1995, Brian spent several years in Quality Assurance. Holding various positions from Tester to QA Manager, Brian studied and developed the best practices required to implement effective quality automation. A certified accountant and former instructor at Carleton University in Ottawa, Canada, Brian has delivered IBM Rational's message of software quality throughout the lifecycle to both students and quality professionals. |
| | Thursday, May 18, 2006 8:30:00 AM
| |
The Software Vulnerability Guide: Uncut and Uncensored
Herbert Thompson, Security Innovation, Inc.
Warning: This talk contains graphic examples of software failure . . . not suitable for the faint of heart. This "no holds barred" session arms testers with what they really need to know about finding serious security vulnerabilities. Herbert Thompson takes you on an illustrated tour of the top twelve security vulnerabilities in software and shows you how to find these flaws efficiently. Each vulnerability is brought to life through a live exploit followed by a look at the testing technique that would have exposed the bug. Testers and test managers will leave with a keen awareness of the major vulnerability types and the knowledge and insight to fundamentally improve the security of the applications they support and test.
Herbert Thompson Chief Security Strategist at Security Innovation, Herbert Thompson earned his Ph.D. in applied mathematics from Florida Institute of Technology. Herbert is co-author of How to Break Software Security and The Software Vulnerability Guide and is the author of numerous papers on software security and testing. He has spoken on software security testing throughout the United States, Europe, and Asia. At Security Innovation, Herbert directs the security strategy of the company and trains developers and testers at Fortune 500 companies on software security. |
| | Thursday, May 18, 2006 4:15:00 PM
| |
Testing and the Flow of Value in Software Development
Sam Guckenheimer, Microsoft
High quality software should be measured by the value it delivers to customers, and high quality software process should be measured by the continual flow of customer value. Modern processes have taught us that managing flow is all about the constraints restricting that flow. Testing, rather than being thought of as a conduit in that flow, is often perceived as an obstacle. It doesn’t help that most testers struggle to answer the questions that their managers ask: What has and hasn’t been tested? What do we need to test next? Where do we need to shift resources? If it works in the lab, why isn’t it working on those production machines? Where do we need to fix the performance or security? The ability—or inability— to answer these questions can determine the success and budget of a test team as well as how it is valued by its organization. Sam Guckenheimer explores these questions with metrics examples from both healthy and unhealthy projects. He contrasts the use of these metrics to current practices, which often only emphasize effort and bug counts. In these examples, Sam uses Microsoft Visual Studio Team System (VSTS) to collect and report measurements and to suggest corrective actions.
Sam Guckenheimer is the Group Product Planner for Microsoft Visual Studio Team System and Microsoft Solutions Framework. He is responsible for the end-to-end external design of the next releases of these products. Sam has been a developer of Automated Software Quality and Enterprise Lifecycle tools for eight years and has been a practitioner for twenty years as a tester, developer, product manager, and business manager. He holds five patents on software lifecycle tools. A Phi Beta Kappa graduate of Harvard University, Sam is a frequent speaker at conferences such as STAR, EuroSTAR, PNSQC, Quality Week, and the International Conference on Software Quality. His book Software Engineering with Microsoft Visual Studio Team System is scheduled for publication by Addison Wesley in early 2006. |
| | Friday, May 19, 2006 8:30:00 AM
| |
Risk-Based Testing in Practice
Erik van Veenendaal, Improve Quality Services BV
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. Hear about his practical experiences, problems he’s encountered along the way, and the results he has achieved.
TMM®, TMap®,and TPI® are registered trademarks of Sogeti USA LLC.
Erik van Veenendaal Founder of Improve Quality Services BV, Erik van Veenendaal CISA has been working as a practitioner and manager in the IT industry since 1987. As a test manager and test consultant, Erik implemented structured testing and carried out test process improvements activities, based on TMM® and TPI®, in a large number of organizations in a variety of industries. He is the author of numerous papers and books on software quality and testing including the best-sellers The Testing Practitioner and Testing According to TMap®. Erik is a regular speaker at international testing conferences and a leading ISEB accredited trainer in the field of software testing. |
| |
|
|
