|
|
Successful Projects-10 Keys to a Proper Beginning One of the primary keys to project success is orchestrating a proper beginning. In order to do this effectively, you must define the project mission, vision, and reason for being; get a handle on requirements; take the time to load the team properly; do the prerequisite work in gaining focus and clarity; and decide on the development methods and strategies. In this presentation, learn the five keys to forming your team and the five keys to successfully starting a project.
|
Robert Galen, Network Appliance, Inc.
|
|
|
Is That Your Final Answer? Auditing Your Measurement Program More and more organizations are committed to establishing an effective measurement program. Big or small, measurement takes time and resources. The overriding key to measurement program success is accuracy. Organizations with established metrics programs typically institutionalize an audit activity to maximize their investment. Explore the current approaches being used to audit measurement activity. Learn why auditing is so important, and what and when to audit within your organization.
|
David Herron, The David Consulting Group
|
|
|
System Test Measurement-What, When, How? Elaine Soat presents an easy set of measurements to use during system testing (QA test cycle). Examine measurements taken from defect tracking and application coverage to projected testing hours versus actual testig hours. Learn how such process and measurement information is evaluated and used for proposed process improvements. Gain the ability to do comparison reporting to measure successes of process improvement within your QA test cycle.
|
Elain Soat, CarteGraph Systems
|
|
|
Using Statistics to Evaluate Process Improvement The techniques associated with Statistical Process Control (SPC) are very useful, but they are not sufficient alone to
provide inferential comparisons. An additional need is the ability to make valid
comparisons.
This paper suggests two additional techniques to help evaluate differences: inference for
difference between two means (using t tests and confidence intervals for the difference
between the means), and inference for two way tables (using chi-square tests). These basic
statistical techniques should be in our analysis toolbox, along with the traditional SPC tools.
|
Paul Below, EDS
|
|
|
Estimating Software Productivity and Quality on Large Systems Estimating productivity (e.g., lines of source code developed per hour) and quality (e.g., code defect rates) are difficult on large software projects that involve several companies or sites, emphasize reuse of Commercial-Off-The-Shelf (COTS) components or adaptation of legacy code, and require open architectures. Using actual metrics from such software development projects, this paper illustrates problems encountered and lessons learned when measuring productivity and quality. These include: how to count different types of code; effects of lengthy development times on productivity/quality; variability
between estimates obtained from different models; and tracking and reporting metrics on productivity/quality for projects based on incremental or evolutionary development.
|
Jack Alanen, California State University
|
|
|
Estimating in the Web World Discover the techniques used by estimators to overcome the challenges they are confronted with in attempting to estimate totally new development environments in the Web/e-commerce world. Typical challenges include how to scope functionality, assess realistic developer efficiency, and tailor the lifecycle processes. Learn how to use these techniques to estimate new project environments and effectively communicate the results of your analysis. Case studies will be provided to illustrate the techniques and their practical application.
|
Lawrence Putnam, Jr., QSM, Inc.
|
|
|
Statistical Process Control (SPC) for Software Inspections Attempts to create user-friendly statistical process control (SPC) charts for software inspections often have
failed. A principle cause of these problems is the failure to recognize the asymmetric distributions of the
critical control variables, and to incorporate this fact into control chart design. This paper provides innovative guidelines for inspections SPC.
|
Don Porter, Motorola
|
|
|
Software Metrics "State of the Practice" In this session, Peter Kulik presents the results of KLCI's third industry survey on software metrics usage conducted in the fourth quarter of 2000. Based on feedback from practitioners, you will explore topics such as metrics usage and best practices, tips to enhance metrics programs, strategies to implement and improve a metrics program, and tools favored to support metrics capture and analysis.
|
Peter Kulik, KLCI, Inc.
|
|
|
Effort Tracking Made Easy Tracking effort is often a difficult cultural change to implement. Projects working toward Capability Maturity Model (CMM) Level two behaviors struggle with effort tracking for many reasons, including tool restrictions, resistance, and complicated processes. Lynn Cole shares insight and techniques that she has both successfully implemented and seen implemented by others. Discover the simple steps that you can take to start capturing and using effort data about a project.
|
Lynn Cole, Spherion Technology Architects
|
|
|
The Impact of Team/Personal Software Processes Several years ago, the Naval Oceanographic Office initiated its process improvement effort with Team Software Process (TSP) and Personal Software Process (PSP) as its foundation. Learn about the areas in which TSP/PSP made a significant impact on implementing change relating to the organization's CMM maturity level. Discover how the structure provided by TSP/PSP facilitated the implementation of a Quality Assurance program, and explore the major impact TSP/PSP had on the organization's ability to establish a baseline of historical project data.
|
Edward Battle, Naval Oceanographic Office
|
