Conference Presentations

A Unified Model for Software Management

This is the presentation that puts all the concepts into perspective. The speaker constructs a model of the software development company as a layered organization comprised of core values at the center, then radiating out to best practices, software lifecycles, software management processes, and finally support tools and systems. Wael Amin reveals how to understand an organization's culture, identify its core values, adopt best practices, and more. His exploration runs the gamut from corporate vision to delivering quality.

Wael Amin, IT Worx
eXtreme Programming: Managing Agile Development

Extreme Programming (XP) has captured the attention of the industry by challenging many cherished beliefs held about software development and management. Not only that, it's actually delivered against those challenges. As a development process, XP focuses on producing sound software architectures while delivering required functionality to customers on time and within budget. It uses iterative development along with other controversial yet effective techniques to get the job done. Robert Martin gives us the real scoop on why XP has enjoyed so many successes, and how it can and will continue to flourish in business development environments.

Robert Martin, Object Mentor, Inc.
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
Read My Lips: No New Models!

These days, it seems everyone who wants to make a mark in the software world feels the need to invent a new model or methodology. While such models provide useful frameworks for structuring our thinking and practices, enough already! Karl Wiegers contends we don't need any more new and improved models for software engineering. Rather, we need to encourage a majority of developers to consistently and effectively apply the practices that have already been shown to work.

Karl Wiegers, Process Impact
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
Thinking About People, Process, and Product: A Principle that Works at Work

All projects involve the three P's: people, process, and product. People includes everyone who influences the project. Process is the steps taken to produce and maintain software. Product is the final outcome of the project. To keep these three in harmony, you must observe who is trying to do what to deliver what. Usually, two of the three P's are mandated, and the third one is chosen appropriately. Although this is common sense, it is not common practice. Dwayne Phillips discusses the issues and challenges that affect us all on every project. Learn about the ideas and questions to consider to help you work through these issues.

Dwayne Phillips, U.S. Department of Defense
A Practical Framework for Software Measurement

Measurement is often defined in terms of collecting data, distinguishing it from analysis-the interpretation and use of data. Clearly, the collection of data must be driven by its intended use. In this presentation, David Card presents a framework that treats measurement and analysis as an integrated process. Discover the four basic components of this framework, and learn how to use the framework to ensure that all-important perspectives and potential users of measurement are considered in the measurement planning process.

David Card, Software Productivity Consortium
A Force for Change-Using Resistance Positively

When we try to improve our organizations, we inevitably encounter resistance. This presentation describes how to turn resistance into a resource. Whatever else it may be, resistance is information about the people we are asking to change; about the environment in which the change will happen; about the changes we recommend; and ultimately, about ourselves. Learn ways to tap into that information to turn resistance into a resource for creating lasting improvement.

Dale Emery, Sun Microsystems
From Zero to 100: Project Metrics in an Investment Bank

Metrics collection, interpretation, and data quality always present a challenge to organizations. In the midst of an ever-increasing organization such as Goldman Sachs, the need for comprehensive metrics has become a top priority. Learn how one company successfully implemented a measurement initiative from ground zero using project management discipline, completion dates, scope definition, and a lifecycle approach-resulting in expanded coverage, more sophisticated usage of data, and support of the management and quality teams.

Barry Young and Arun Banerjee, Goldman Sachs and Co.
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.

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.