The Latest
eXtreme Programming: Managing Agile Development[presentation] 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. |
Robert Martin, Object Mentor, Inc.
|
|
SM/ASM 2002: The Business Case for Software Quality[presentation] 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. |
![]() |
|
Mentors, Models, and the Making of Managers: Special Panel Discussion[presentation] Each of us has a story about how we came to be managers in software organizations. Many of us became managers because we were good developers. Some of us studied management in school. |
Moderator: Esther Derby ( Esther Derby Associates, Inc.)
|
|
Read My Lips: No New Models![presentation] 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, Process Impact
|
|
Speaking to Your Management: What Do You Do When They Do Not Listen[presentation] This presentation explains some of the language barriers and experience barriers between management and quality assurance professionals. |
![]() |
|
Software Improvement Feedback Loops: How to Develop a Learning Organization[presentation] Over the past twenty-five years, the Software Engineering Laboratory (SEL) at NASA/GSFC has studied mechanisms for improving the software process and product. |
Victor Basili, Software Engineering Laboratory
|
|
Thinking About People, Process, and Product: A Principle that Works at Work[presentation] 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. |
Dwayne Phillips, U.S. Department of Defense
|
|
A Practical Framework for Software Measurement[presentation] 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. |
David Card, Software Productivity Consortium
|
|
A Force for Change-Using Resistance Positively[presentation] When we try to improve our organizations, we inevitably encounter resistance. This presentation describes how to turn resistance into a resource. |
![]() |
|
Launching a Web Development Team[presentation] Based on a real-life case study, learn how one Fortune 500 manufacturing company-with four development groups in two locations-created a flexible and cost-efficient Web development solution to meet the needs of an expanding business. |
Thomas Vlasic, John Deere Co.
|
|
Organization: The Forgotten Dimension[presentation] Explore the software project manager's actual, perceived, and desired position in an organization. |
Mark Servello, Change Bridge, Inc.
|
|
Predictive Metrics to Estimate Post Project Costs[presentation] How much will it cost to support your software project based on current estimations? |
Geoffrey Facer, Intel Corporation
|
|
Three Numbers to Measure Project Performance[presentation] We present a method which produces at any time during the execution of a big software |
Thomas Liedtke and Peter Paetzold, Alcatel
|
|
From Zero to 100: Project Metrics in an Investment Bank[presentation] 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. |
Barry Young and Arun Banerjee, Goldman Sachs and Co.
|
|
Better Testing-Worse Quality?[presentation] 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. |
![]() |