|
|
Three Numbers to Measure Project Performance We present a method which produces at any time during the execution of a big software
development project a reliable prediction of the total duration and of the total cost to expect
at project completion. The basic idea presented in our paper is to correlate cumulative cost consumed to current
completion reached, and to learn out of this about the future of the project. Prerequisites
are a cost consumption plan and a deliverables completion plan. The approach is
presented both theoretically and on hand of a real life case. Special attention is paid to
project management techniques related to the method.
|
Thomas Liedtke and Peter Paetzold, Alcatel
|
|
|
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.
|
|
|
B2B and B2C Software Project Management—So What's Different? Learn how to understand and address the unique and not so unique aspects of Internet-based business-to-consumer (B2C) and business-to-business (B2B) project development. Based on three case studies used to illustrate the important aspects of Internet project development, you will cover the full project lifecycle--from inception to launch--highlighting key principles and practices along the way. The case studies will include an information-centric Internet Web site (corporate brochure site), and electronic commerce site (consumer), and a business-to-business exchange.
|
Rick Smith, ObjectSpace, Inc.
|
|
|
Predicting Software Errors and Defects This paper introduces a fault model that predicts the number of errors and defects throughout the development cycle. Project managers can use this information to quantitatively determine if the development process is in control, may be going out of control, or is clearly out of control. This model is able to adjust estimates based on the most current data available.
|
Mark Criscione, Motorola
|
|
|
Put Your Power to Work! Power is the ability to create value. If you want to create more value in your organization, you must learn to tap the abundant resources of power. The four most abundant power sources are 1) your own inner resources; 2) the physical world; 3) interacting with another person; and 4) working in teams to achieve a shared purpose. Winner of Best Presentation at SM 2001, Dale Emery returns to help you learn to harness your own power resources-for your benefit and the benefit of others.
|
Dale Emery, Sun Microsystems
|
|
|
Measures that Predict Change Prediction becomes more accurate when there are measured trends to show the way. Knowing what to collect and review is only half of the process of predicting change. The rest of the methodology is understanding the data and being able to predict changes so that the project team can proactively respond to change events. Learn how organizations within EDS have begun to accurately predict changes. Explore the methods, decisions, and the necessary steps taken by EDS to develop and use metrics and measures that support key management decisions.
|
Gail Borotto, EDS
|
|
|
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
|
|
|
Warp 6, Mr. Sulu: The Future of Software Development As a manager, you have many readings which help you monitor your course. Choosing a direction is a different matter. Like the crew of any Star Trek episode, you may have to make a decision based on the unknown. The best choice may not be based on what you know-but what is possible. For years we have built software in roughly the same way. Becky Winant discusses an emerging new discipline sitting on the horizon-complete with higher-level communication tools, practical knowledge capture, and advanced simulation software-that is poised and ready to change the face of software development as we know it.
|
Becky Winant, Esprit Systems Consulting, Inc.
|
|
|
Gaps, Traps, and Overlaps: Communication Flaws and How to Fix Them In some organizations, communication flaws are rampant and muddled messages are the norm. Success in software efforts is often hindered by communication that is incomprehensible, ambiguous, misdirected, ill-timed--or lacking when it is most needed. The result? Rocky relationships, topsy-turvy teamwork, precarious projects, and crazed customers. The situation is not hopeless, though. In fact, making changes is surprisingly easy. In a presentation that is both serious and light-hearted, Naomi Karten shares ideas, experiences, and advice to help you detect, correct, and prevent some of the most common communication snafus.
|
Naomi Karten, Karten Associates
|
|
|
The Story Software Defects Tell about Project Management We often evaluate and design software processes and activities as if putting them on lists and schedules will automatically make them happen. Yet software development also includes complex human interactions that must be planned and managed in order to gain best results, or to even survive. Drawing upon over one hundred candid engineers' comments from twenty root-cause analysis brainstorming sessions of frequently occurring defects, Bob Grady reveals fascinating insights into project management backgrounds, methods, training, and weaknesses. Into these insights, he weaves the use of personality preferences with project management methods to help you avoid common pitfalls in ways that engineers themselves prefer.
|
Robert Grady, Hewlett-Packard Co., Retired
|
