| |
| 1 |
7/20/99 |
Conference Welcome |
|
Cheryl Jones, PSM Project Manager |
| 2 |
7/20/99 |
Conference Keynote:
The Use of Measurement in Managing the F/A-18E/F Acquisition |
RADM Joe Dyer will discuss the use of measurement during his tenure as the
F/A-18E program manager. His presentation will focus on the use of measurement
in tracking progress through detailed earned value and as the basis for risk management.
Both the acquisition office and contractors had real-time access to a shared database,
greatly facilitating communication between all parties.
The F/A-18F was the first winner of the DoD's Excellence in Acquisition Award.
Dr. Paul Kaminksi, Under Secretary of Defense for Acquisition Technology,
noted the program's continuous sharing of information as a key factor in the
program's achievements.
This is a rare opportunity to hear about the value of detailed measurements
from a high-level decision-maker that used them on a daily basis in managing
one of the most successful acquisitions to date. |
RADM Joseph W. Dyer, Commander, Naval Air Station Center, Aircraft Division, Patuxent River, MD |
| 3 |
7/20/99 |
OSD Software Measurement Initiative |
This presentation will provide an overview of a new initiative implemented
by DoD providing independent assessment of software-intensive programs.
The top-level assessment process and technical framework will be described. |
John McGarry and
Kristen Baldwin, US Army ARDEC - TACOM |
| 4 |
7/20/99 |
Software Engineering Body of Knowledge Project |
Recently, the state of Texas has begun the licensing of software engineers.
Legally speaking, in most states it is illegal to call yourself a "software engineer"
at all; Texas is the first state with a mechanism to be licensed as one.)
This is just one indication of the demand for professional accountability in
the practice of software. Before we can license software engineers, though,
we need to test them. Before we can test them, we need to train them. And,
before we can train them, we need curricula. The Software Engineering Body of
Knowledge (SWEBOK) project is a joint venture of the IEEE Computer Society
and the ACM to develop a single document that will characterize the things that
software engineers should know and provide references to where the information
can be obtained. It will be used as a basis for licensing examinations,
competency certification, and curriculum development and accreditation. |
Jim Moore, IEEE Computer Society |
| 5 |
7/20/99 |
Using PSM to Help Crisis Projects |
This presentation will discuss how PSM was used successfully on a large "crisis"
project. By using PSM, issues related to customer confidence in the product's quality,
schedule predictability, workforce problems, and process stability was brought to
light. Measures were put in place to address and provide visibility into these
issues. Use of measurement was incorporated into the day-to-day project activities,
and were presented and used by both the project team and customer representatives.
Benefits included regained control of the project; improved, more objective
communications; and improved schedule predictability. In addition, the connection
between measurement and process was made, and the resulting process
streamlining/improvement that resulted will be discussed. |
Beth Layman, Senior Associate, TeraQuest Metrics, Inc. |
| 6 |
7/20/99 |
Enterprise Performance Measurement - An Introduction |
Enterprise-level executives make decisions that affect the health and performance
- competency, competitive position, and continued profitability - of the organization
in its entirety. Software and systems development however may be only some of the
many corporate concerns. Investments in software and systems engineering capabilities
and process improvement must often compete with investments in other business and
functional areas. This presentation will introduce an approach to understanding
the business value of software and systems investments and some of the techniques
available to managers for making effective investment decisions. |
Robert MacIver, Software Productivity Consortium |
| 7 |
7/20/99 |
DCMC Software Performance Evaluation Maturity Model |
With the growing complexity of software design and development, a credible,
consistent and practical approach is necessary across the Defense Contract
Management Command (DCMC) to support customer needs. Information DCMC provides
should enhance program office decisions associated with cost, schedule, and
performance. To assist in performance evaluation and improvement, the DCMC's
Software Center has developed a performance model derived from features within
the Software Engineering Institute (SEI) Software Acquisition - Capability
Maturity Model - (SA-CMM). This maturity model focuses on the software measurement
process that all Contract Administration Offices are required to have. |
Guy Mercurio, DCMC |
| 8 |
7/20/99 |
Measurement Practices in High Maturity Organizations |
The application of statistical process control (SPC) and quality management
techniques to projects within software organizations is relatively new. However,
as organizations progress through the repeatable and defined levels of the
Capability Maturity Model (CMM) they reach the point at which adoption of these
techniques makes business sense. The CMM defines the application of rigorous
quantitative techniques as a benchmark for Level 4. Unfortunately, the measurement
and analysis skills required for the implementation of these techniques is
sufficiently different from those of lower levels of maturity, that they often
create a barrier. This presentation will introduce and define the role of
measurement in achieving higher levels of process maturity. Applicable techniques
and examples pertaining to the quantitative management of software will also be
discussed. |
Don Dortenzo, Software Productivity Consortium |
| 9 |
7/20/99 |
Implementing Metrics for OO Testing |
Object oriented development is widely used in today's software development,
but how do we test? Metrics derived from a code analysis can be used to indicate
where potential problems may be lurking. In this talk we will discuss code analysis
metrics for object-oriented software, and how they can assist in testing. |
Linda Rosenberg, NASA |
| 10 |
7/20/99 |
Tailoring PSM for Process Improvement Measurements |
The FAA has undertaken a major process improvement initiative using its
own developed integrated CMM [FAA-iCMM] approach. A major requirement
is that each process area measures its status to reach level
2 capability. The FAA chose to adopt the PSM methodology to
address process measurement issues. With the initial help of
PSM, the FAA has conducted a series of process measurement workshops
for various FAA projects. This will address how PSM material
was tailored for FAA process issues and what the results and
lessons learned have been. |
Joe Caravello,
Don Gantzer, Federal Aviation Administration |
| 11 |
7/20/99 |
Measurement in the Capability Maturity Model Integration (CMMI) |
This presentation will provide an overview of the draft CMMI Product Suite
that is sponsored by DoD with participation from industry and other federal
agencies. Joe will discuss how measurement is incorporated as part of the
practices that guide process improvement. |
Lt. Col. Joe Jarzombek, U.S. Air Force, ESIP |
| 12 |
7/21/99 |
Experience Implementing an Issue-Driven Measurement Approach |
This presentation describes our experience implementing a set of issue-driven
measures to solve the problem of extremely long build durations for a program
maintaining a complex, 2M LOC system. The impetus for trying this measure came
from a PSM workshop for that program. The result was that in 2 months of trial
and error with implementing and displaying the measure, a series of actions
took place to fix several layers of problems with the roles, responsibilities,
procedures, processes, environment, and tools to reduce the build duration from
6 weeks to 1 day. Lessons included optimization of build problem categories
that fit the program and user understanding; involving the right people;
jump-starting the improvement process; sufficient training; yet-another-form;
and the death of the measure. |
Karen Bourgeois, Principal Software Scientist, Lockheed Martin |
| 13 |
7/21/99 |
Software Risk Management Standard Update |
A new standard on risk management is being developed. Dr. Charette chair of the
risk management standard working group, will review the concepts and principles
behind the standard and its implications for organizations. Dr. O'Brien will
evaluate the standard from the perspective of an organization that has been
actively performing risk management for over a decade for its strengths,
weaknesses and organizational impact. |
Dr. Robert N. Charette
, ITABHI Corporation,
Dr. Pat O'Brien, Rockwell Collins |
| 14 |
7/21/99 |
Benefits from Implementing a SPI Program |
Faced with stiff competition and declining budgets many organizations are
asking what they can expect in return-on-investment (ROI) from implementing a
process improvement program. This briefing will explore the importance of
baselining your capabilities at the start of a process improvement initiative.
Mr. Putnam will also review the benefits that the Software Engineering Division
at Hill AFB experienced from their Software Process Improvement efforts. |
David Putman, SEPG Lead, U.S. Air Force |
| 15 |
7/21/99 |
A Business Case Approach for Process Improvement |
This presentation will define a business case approach for introducing and
evaluating cost-effective performance catalyst on engineering projects. The cost
impacts on ROI of the performance catalyst are evaluated before, during and after
the project. They have been careful to say that catalyst introduction can improve
project performance, but the catalyst introduction must be planned and managed
effectively and must be evaluated carefully. |
Wayne Sherer, Chief, Process & Technology, U.S. Army TACOM-ARDEC |
| |
| 1 |
PSM Training Course |
This ½ day course provides an overview of the guidance included in
Practical Software Measurement: A Foundation for Objective Project Management,
Version 3.1a. The course is intended as an introduction to PSM for those with
little or no prior PSM experience. |
Betsy Bailey Clark, Ph.D, &
Brad Clark
, Ph.D, Software Metrics, Inc. |
| 2 |
SPICE and Other Flavors: Software Process Assessment using ISO 15504
|
This training course will provide a detailed analysis of the framework
for process assessment in ISO 15504, placing it in the context of international
developments in the area. It will address the questions of why an organization
should choose to start an assessment program, and discuss the practical
issues that an organization faces when starting such a project. The
information presented will be the most current available, being based upon
the approved and published version of ISO 15504 and incorporating results
from the second phase of the SPICE Trials, which concluded in April 1998.
It will address the proposals for revision of ISO 15504 currently under
consideration. The workshop includes a detailed discussion of the relationship
of the SPICE Framework to existing assessment approaches such as the
Capability Maturity Model, as well as to other International Standards
including ISO 9001 and ISO 12207. |
Terry Rout, Software Quality Institute, Griffith University, Australia |
| 3 |
PSM Insight Training |
A demonstration of PSM Insight version 3.10 will be provided. The
major features of the tool, which implements the PSM measurement process,
will be summarized. Students will have hands-on use of the tool. |
Dave Morris, Independent Engineering, Inc. |
| 4 |
Review of Revised PSM Guidance |
This workshop will focus on resolving major technical revisions to the PSM
guidance to be documented in Version 4.x of the guide. The proposed new
issue-category-measure structure will be reviewed along with new guidance
in the area of systems engineering and product engineering. Relationships to
ISO/IEC 15939, 12207, 15504 and 9001/9004 will be discussed. |
Joyce Jakaitis, American Systems, Corp. |
| 5 |
Risk Management Standard Review |
This workshop will review the draft of IEE P1540, the proposed Software
Risk Management Standard. The purpose will be to provide substantive comments
and feedback to the risk management standard's working group before the draft
standard is finalized. |
Dr. Robert N. Charette, ITABHI, Corp. |
| 6 |
Process Improvement Measurement |
This workshop will focus on continuing efforts to apply the guidance
provided by PSM to process improved initiatives. The workshop will build on the
initial concepts developed at the 1998 PSM User Group Conference and the 1999
TWG Meetings. The goal will be to complete the adaptation of the PCM I-C-M
structure to process improvement and to develop a technical approach to
tailoring the PSM implementation guidance to meet the needs of process
improvement initiatives. |
Don Dortenzo, Software Productivity Consortium |
| 7 |
Measuring and CMMI |
This workshop is intended to address informative content that should be
included in the CMMI Measurement & Analysis Process Area to help individuals
understand how measurement capabilities should be "matured" as organizations
increase their capabilities. The workshop will also provide a forum for participants
to review a draft "Measurement Plan" template that is intended to provide a guide
for an organization that will be implementing a measurement program consistent
with the CMMI. |
Lt. Col. Joe Jarzombek, USAF, ESIP |
| 8 |
Risk Management Standard Review Workshop Summary |
|
|
| 9 |
Integrating PSM and SPICE |
The PSM framework for software measurement sets out a mechanism for
identifying appropriate measures based upon the establishment of issues relevant
to the management of a project or process. ISO/IEC TR 15504 sets out a framework
for evaluating the capability of processes in the software life cycle, based upon
a scale of capability levels. This paper shows the relationship between the PSM
Framework and the measurement framework in ISO 15504. The relevance of this work
to process improvement efforts is discussed and the relevance of the current trials
of ISO 15504 by the SPICE project is explored. |
Terry Rout, Software Quality Institute, Queensland, Australia |
| 10 |
Review of Revised PSM Guidance Workshop Summary |
|
|
| 11 |
Process Improvement Measurement Workshop Summary |
|
|
12 |
Measuring and CMMI Workshop Summary |
|
|
