|
|
How to Find the Level of Quality Your Sponsor Wants In this paper, I'll talk about how to focus yourself to do effective testing. I'll cover where to start, what to look for, what and who are your resources. There is a level of understanding you need about the quality goals for a project. I'll give some examples of ways to figure that out without even asking questions. Or, who to ask if you could and then what to do with the information to be
effective in your testing efforts. Some of this is similar to risk based testing, which you can use in a complementary fashion. The way it is different is in its focus on the sponsor’s expectations.
|
Sue Bartlett, Step Technology
|
|
|
The Global Challenge: Quality Assurance for Worldwide Markets Many software applications are hosted in worldwide data centers, simultaneously launched with multiple language user interfaces, and continuously upgraded in rolling release cycles. Yet few software development organizations have a clear strategy for testing internationalized (I18N) products. Join presenter Steve Nemzer for an insider's view into the fascinating cultural, technical, and linguistic challenges faced by today's internationalization engineers.
|
Steve Nemzer, VeriTest
|
|
|
A Common Sense Approach to Statistical Process Control As maturing software organizations begin using statistical process control (SPC) techniques to stabilize processes and manage quality, it's imperative that their SPC implementation approach be carefully considered, especially since it involves the use of statistical analysis techniques that are unfamiliar to most people. This presentation describes an approach to implementing SPC that maximizes project personnel involvement through creative delegation, provides for the timely utilization of the data, and keeps management well informed but not overburdened.
|
Steven H. Lett, The David Consulting Group
|
|
|
Problem Resolution Cycle Time Optimization No matter how well we plan and execute software development, defects are generated and can escape to the customers. Failure to quickly resolve software problems leads to negative consequences for our customers and increases internal business costs. A quick deterministic
method to prioritize problems and implement their solution helps to reduce cycle time and costs. Achieving this goal requires several steps. The first is to determine a model that links problem resolution performance to institutional variables and problem characteristics. Statistical Design of Experiments (DOE) is a tool that provides data requirements for estimating the impacts of these variables on problem resolution. Once data has been gathered the results of statistical analysis can be input into a mathematical optimization model to guide the organization.
This paper describes such an analysis.
|
Don Porter, Motorola
|
|
|
SM/ASM 2002: The Business Case for Software Quality Each generation of technology-from mainframe to the Internet-creates many opportunities for businesses to try new things. But with uncharted territory comes exponentially increased risks. One way to reduce risk is to implement effective software quality processes. However, the investment required to improve development and testing infrastructures can be significant. Richard Bender addresses fourteen major areas of opportunity that underscore why this investment is critical if an organization is to succeed. He covers areas such as increasing project failure rate, the limited supply of software professionals, rising support costs, and the implications of eCommerce.
|
Richard Bender, Bender & Associates
|
|
|
Software Improvement Feedback Loops: How to Develop a Learning Organization Over the past twenty-five years, the Software Engineering Laboratory (SEL) at NASA/GSFC has studied mechanisms for improving the software process and product. During this time, a set of processes has evolved: the Goal/Question/Metric Paradigm; the Quality Improvement Paradigm; and the Experience Factory Organization. These processes are based on the needs for measurement and feedback loops, from project to process and project to project, creating a learning organization for building software competencies. In this presentation, Victor Basili discusses these processes, how they evolved, the lessons learned, and the effects of their application in the SEL.
|
Victor Basili, Software Engineering Laboratory
|
|
|
Better Testing-Worse Quality? Many organizations react to quality issues encountered after shipping a product by renewing their emphasis on testing. The logic is that better testing would have resulted in better software. Ironically, focusing on testing can cause worse quality. In this discussion, Elisabeth Hendrickson provides real-world examples of when better testing has resulted in worse quality and how to turn around the downward spiral.
|
Elisabeth Hendrickson, Quality Tree Software, Inc.
|
|
|
Process Improvement in Large Organizations: Walking the Maze Every problem-solving activity in an organization requires some learning. Both the stakeholders and the
facilitators of the organization need to learn as they go through change. This paper describes our first
experiences with facilitating process improvement and problem solving by focusing on congruence, building trust
relationships, systems thinking and lots of "letting go."
|
Nynke Fokma, Moebius Consultancy and Erwin van der Bij, Lucent Technologies
|
|
|
The Software Organization as a Complex Adaptive System We are living and working in the "knowledge rea" where business, technological, and organizational changes cannot be predicted or foreseen. One minute you are on top; the next minute, you are obsolete. For a software organization to sustain itself over time, it must act as a Complex Adaptive system (CAS) and operate on the edge of Chaos (EOC) as a learning organization that is continuously learning and co-evolving. Gain insight into how to become a sustainable software organization in a rapidly changing environment.
|
Nir Merry, Applied Materials and Dr. John Bruckman, Change Management Group
|
|
|
A Metrics Dashboard for IT Project Reporting Tom Olenick described the activities performed to design, develop, deploy, and maintain a Project Management Metrics Dashboard across the IT organization of a major Chicago-based securities organization. Learn how this metrics dashboard was used to facilitate project status tracking for IT management and to provide a basis for improving the efficiencies of software development activities and estimation.
|
Thomas Olenick, Olenick & Associates
|
