|
|
Agile Software Development: The Home of 31 Flavors You've heard of eXtreme Programming (XP) and perhaps Scrum. How about Crystal Clear, Adaptive Software Development, Dynamic Systems Development Method, Rational Unified Process for Agile Development, and Feature Driven Development? These are some of the many variations of Agile development methods. Join Jeff McKenna as he explores the many flavors of Agile development methods and explains the similarities and differences. Find out what aspects of Agile development can help your organization’s development team in its particular environment. If you are considering Agile development and need to decide in which direction to go, this session is for you. Although a one-hour session cannot provide all the information you will need, you can explore what is common-the philosophy, the values, the characteristics-and what is different-the methods, the coverage, the costs-about different Agile approaches.
|
Jeff McKenna, Agile Action
|
|
|
Agile and Adaptive Project Management - The Declaration of Interdependence Whereas the Agile Software Development Manifesto is a short and sweet list of principles for developers, the Declaration of Interdependence for Agile Project Management is more of a mouthful. The Declaration of Interdependence was written to provide concrete guidance for software projects and projects in general with applicability to general management. In constructing it, a dozen senior consultants, designers, and managers-project, product, and line-validated that it covered their individual core operating frameworks. In this talk, noted software designer, manager, and methodologist Alistair Cockburn, a co-author of both documents, unravels the six rules of operation in the Declaration of Interdependence. In the Declaration, project managers agree to increase ROI, deliver reliable results, expect uncertainty, unleash creativity and innovation, boost performance, and improve effectiveness.
|
Alistair Cockburn, Humans and Technology, Inc.
|
|
|
Achieving Meaningful Metrics from Your Test Automation Tools In addition to the efficiency improvements you expect from automated testing tools, you can-and should-expect them to provide valuable metrics to help manage your testing effort. By exploiting the programmability of automation tools, you can support the measurement and reporting aspects of your department. Learn how Jack Frank employs these tools with minimal effort to create test execution
status reports, coverage metrics, and other key management reports. Learn what measurement data your automation tool needs to log for later reporting. See examples of the operational reports his automation tools generate, including run/re-run/not run, pass/fail, percent complete, and percent of overall system tested. Take with you examples of senior management reports, including Jack's favorite, "My Bosses' Boss Test Status Report"-names will be changed to hide the guilty. Regardless of the
|
Jack Frank, Mosaic Inc
|
|
|
Navigating the Minefield of Open Source Test Tools Each year more and more open source development tools, including test tools, are available. By choosing to use open source test tools, companies expect to save money and take advantage of the community of shared development. Recently, there seems to be an abundance of open source testing tools being released, including tools for automated regression, load testing, test management, and defect tracking. But how do you know which tools are right for you? Based on his real-world experiences using such tools, Jeff Jewell covers the issues that you are likely to encounter as you evaluate open source testing tools. Learn where to find open source test tools, the challenges you
face in choosing these tools, and what you will need to do once you find the right tools. Find out if your organization is ready to use open source tools and how to find the right tools for you.
|
Jeff Jewell, ProtoTest LLC
|
|
|
Testing Inside the Box These days, we hear a lot about unit testing, testing for programmers, test-first programming, and the like. Design techniques for such tests and for improving system testing are often called white box test designs. Join Rex Black as he explains the basics of white box testing and compares
white box with other types of testing. Find out how the metaphor of "boxes" can inform-and confuse-us. Rex discusses the basis path tests, including cyclomatic number as a measure of complexity and a way to determine the number of tests necessary to cover all paths. He walks
|
Rex Black, Rex Black Consulting
|
|
|
A Tester's "Wonderful Life" in an Agile Development Shop Some subscribe to the notion that agile methods-such as eXtreme programming (XP) and test-driven development-eliminate the need for QA and testing specialists. Others, including Greg Grivas, subscribe to the belief that QA/test is needed in every aspect of Agile development. While gathering requirements as stories or use cases, the test specialist takes on the roles of consultant, facilitator, questioner, and possibly leader. After the code is developed, reviewed by users, unit tested, and close to production-ready, the QA specialists subject the software to further tests: smoke, regression, endto-end, performance, load, usability, exploratory, and more. In the final phase of delivery, the code is subjected to all the different testing techniques again, and bugs are immediately converted to requirements and corrected at a fast pace.
|
Greg Grivas, Administrative Office of the U.S. Courts
|
|
|
Put an End to the Defect Report-Fix-Check-Rework Cycle Many software organizations have mature defect tracking processes and tooling. Defect reports are often the primary means by which testers and developers communicate, and many teams run their development priorities from the defect tracking system. Bad news. We now find ourselves swimming in defect reports, the majority of which are irrelevant, out of date, repeated, not reproducible, and difficult to associate to the features we've committed to deliver. The solution is to adopt techniques that pull testing forward in the software lifecycle so we replace most of the defect reports with "failing" test cases that are transitory in nature, easily reproduced, and require little management
overhead. The result is that we dramatically reduce our defect management burden, improve our responsiveness to customer feature requests, and ship with higher software quality.
|
Richard Leavitt, Rally Software Development
|
|
|
Making Test Data More Agile Flexible, reusable, and restorable test data for both the unit and system level is an absolute necessity for testers working on Agile development projects. For teams following a more traditional development process, Agile approaches for handling test data can enhance testing efforts as well. Discussing Agile testing approaches, such the ObjectMother pattern, Peter Schuh explains how testers design tests and test frameworks to survive the ever-changing data structures found in Agile projects. Learn how an Agile process allows testers to get much more mileage out of test data sets during and after the initial development project. Leave with a set of practices and techniques to apply directly to Agile development projects or modify for their current development environment.
- The many dimensions of application test data
- Produce and maintain better tests and test data with Agile approaches
|
Peter Schuh, Peter Schuh
|
|
|
Test Improvement for Highly Reliable NYSE Trading Systems With billions of dollars changing hands every day, financial trading systems demand extremely high accuracy and reliability. So, how do you improve test process performance in the areas of time to market and efficiency and at the same time reduce failures? Over the last three years, using process and project measurement data as a guide, SIAC has focused on doing exactly that. Steve Boycan highlights the key elements of the process changes that have led to SIAC's current performance: the use of a rigorous requirements engineering process; controlled parallel and iterative work flows; changes to the level of abstraction in test documentation; emphasis on test planning, analysis, and design; causal analysis; and improving the test team's skills.
|
Steve Boycan, SIAC
|
|
|
Applying Use Case-Driven Testing in Agile Development Use Cases provide a user-focused sequence of events that also can serve as a template for functional testing activity. In an agile environment, use case-based testing brings testing earlier into the process and helps teams more quickly deliver higher levels of functionality to their customers. Testing with use cases also provides early peer review for the logic of intended functions. Involving testers in use case development and harvesting use case scenarios for test case development has shown great practical benefit in numerous application development projects. Dean Leffingwell describes the use case-based testing method and highlights practical tips for applying the technique. Learn to employ use cases to express functional requirements and how use case scenarios can serve as templates for testing activities.
- An overview of use case development practices
- Accelerating test development with use cases
|
Dean Leffingwell, Consultant
|
