F1	Implementing Software Process Change (CKA #5)	Neil Potter
F2	Applying Agile and Software Development Techniques to Process Development (CKA #1)	Nelson Perez
F3	Measuring Software Processes (CKA #2)	Alfred Sorkowitz
F4	Mastering the Software Product Lifecycle: Development to Support (AKA #2)	Dr. Timothy Korson
F5	Development and Configuration Management of Requirements (AKA #1)	Al Florence
F6	Hands-On Workshop on Measurements (AKA #10)	Marty Safirstein & Cheryl Saar

F2: Applying Agile and Software Development Techniques to Process Development 
Nelson Perez

This tutorial covers CKA area #1 of the International Software Process Improvement Certification (ISPIC) requirements.

Introduction:

This tutorial presents techniques borrowed from the Agile and software development world to both design processes and to reduce the overall time to achieve institutionalization of new processes. The topics to be covered are:

• overview of agile techniques
• applying Agile methods to process improvement
• strategies to facilitate the change process
• applying software development techniques to process development
• process tailoring
• process development planning
• effective process rollout management strategies
• lessons learned from a real-world example

Outline:

• Learning Objectives
• Learning Mechanism
• Unit #1: What is Agile?
  • What is Agile Development
  • What are its strengths?
  • What are its challenges?
  • How do we manage it?
  • Can it be used by other disciplines?
• Unit #2: Applying Agile to Process Development
  • (Agile Development) defined
  • Agile (Process Development) defined
  • It's a balancing act: The Ying-Yang of Left & Right
  • Use a defined process as a guide
  • Make small but continuous changes
  • Create an effective strategy
  • Fix people's biggest problems first
  • Fill best practice gaps
  • Deliver outputs first, processes later
  • Pilot solid ideas not final solutions
  • Enlist the help of champions
  • Work as a team to create synergy
  • Coach and mentor to stay on track
  • Let it take on a life of its own
  • Inject more details and iterate until complete
• Unit #3: Process Development in 7 Easy Steps
  • But first a word about “the” method
  • Step 1: develop a context diagram
  • Exercise #1
  • Step 2: Identify information and work products exchanged, deliverables, communications, and data
  • Exercise #2
  • Step 3: Identify and Describe Major Processes
  • Exercise #3
  • Step 4: Analyze process data flows and relationships
  • Exercise #4
  • Exercise #5
  • Step 5: Draft high level processes (aka process “cheat” sheets) and QA checklists
  • Exercise #6
  • Step 6: Create output product templates, forms, tools
  • Step 7: Develop detailed processes
  • Process Descriptions: Typical Components
  • Process Descriptions: Crafting Policy (the difference between policy and process)
  • Process Descriptions: Process Overview
  • Process Descriptions: Entry and Exit Criteria
  • Process Descriptions: Measurements
• Unit #4: Let’s Get Agile!
  • Planning Agile Process Development
  • Exercise #7
• Unit #5: Process Tailoring
  • Metrics-Based Process Tailoring
  • Class Exercise #8
• Unit #6: Process Rollout
  • Process Rollout Management
  • Case I: 3 Projects, Same Start Date
  • Case II: 3 Project, 1 Project With Later Start Date
• Unit #7: Real-World Example and Lessons Learned
  • Real-World Example
  • Lessons Learned
• Summary
• Q&A

Learning Objectives:

• Gain a high-level understanding of agile software development techniques
• Explore how agile techniques might apply to process development
• Get hands-on experience with a defined process development methodology
• Learn how to develop processes using this methodology while doing it in an agile way
• Gain an understanding on how to deploy, refine and monitor processes within the organization
• Gain additional insight from real-world lessons learned

Biography:

Nelson Perez is president of Sierra's Edge, Inc. (an SEI Partner). With over 25 years of work experience, he has worked the entire life cycle and held numerous management and engineering positions on such high visibility programs as the B2 Stealth Bomber; NASA Space Shuttle; and National Missile Defense. Perez received his initial process training at TRW's Defense Systems Group while Dr. Barry Boehm was its Chief Scientist. He started working with the S/W CMM in 1996 as the process architect (as well as project manager and avionics simulation lead) on the US Air Force/TRW Special Operations Forces Extendable Integration Support Environment (SOF EISE) program. He turned around the program using agile techniques while employing the philosophies of W. Edward Deming, in particular those from his book “The New Economics”. Perez reduced the lifecycle from 36 to 17 months, reduced defects uncovered during system testing from 5000 to 2, performed several CMM level 5 causal analysis and improvement cycles, and forged a strong multi-contractor integrated product team. SOF EISE went on to win the 21 st Century Partnership Team Quality Award in 1998 and was voted 1 of the top 5 government programs in 2001 by a panel of experts that included Watts Humphrey and Capers Jones. In addition to modeling and simulation, he has worked a variety of other domains including security systems, information systems, computer integrated manufacturing, wireless communication, commercial software development, aircraft systems, and non-destructive testing. He has co-authored 1 NASA-related patent, has authored several papers and is an active presenter at conferences, software process improvement network (SPIN) meetings and other venues. His research interests include process efficiency, effectiveness, compliance, and institutionalization as well as statistical analysis and electronic discovery. Perez consults with companies in management, technology innovation and process and business improvement including ISO 9001:2000, CMMI, and ITIL v3.

Nelson Perez

F3: Measuring Software Processes 
Alfred Sorkowitz

This tutorial covers CKA area #2 of the International Software Process Improvement Certification (ISPIC) requirements.

Introduction:

As most Software Process Improvement ( SPI ) professionals know, there's more to developing quality software then writing and testing programs. They understand that the quality of a software product is largely governed by the quality of the Software Life Cycle Process (SLCP) used to develop and maintain it. This process can be defined, measured, and continuously improved.

This tutorial lays out the general concepts, issues, and framework for measuring the software process in order to support an organizations management information needs. This includes measuring the software process in order to find areas for improvement. Measurement is a key enabler for process improvement and enhanced product quality, as well as a mechanism for feedback and control.

This tutorial was designed to provide the Software Process Improvement professional with the measurement and analysis knowledge necessary to perform effectively.

Outline:

• Motivation for software measurement.
• How measurement can aid in the software process.
• Basic elements in the software measurement process.
• Software measurement principles.
• Life cycle application.
• Measurement categories.
• Types of software measurements.
• Project, product, and process measurements.
• Science and measurement.
• Identifying an appropriate set of metrics.
• A detailed discussion of a set of ‘best practices' metrics used successfully by industry and government. This will include metrics that can be used in all phases of the Software Life cycle Process.
• Collection, organization, and analysis of the ‘best practice' metrics.
• Group participation in a number of case studies in order to gain experience in analyzing a mix of interrelated metrics.
• An introduction to the Goal-Question-Metric (GQM) framework
• An exercise in developing specialized tailored metrics, such as ‘customer satisfaction'.
• A discussion on how to use measurement data to evaluate an organizations software process, find areas for improvement, and set new process goals.

Participants will learn:

• An introduction to the concepts, elements, and principles of software measurement
• An overview of ‘best practices' metrics used successfully by industry and government with numerous examples and case studies. For each of the metrics, there will be a discussion of the appropriate collection, organization and analysis of the metric data
• How to develop tailored, specialized measurements to support your organizations needs. The Goal-Question-Metric (GQM), and Practical Software Measurement PSM) frameworks will be discussed with exercises for developing tailored measurements for such areas as ‘customer satisfaction' and, ‘is the software ready to go operational?
• How to use measurement data to evaluate your organizations software process, find areas for improvement, and to set new process goals. This example will use real-life data, from a leading international organization's published report.

Biography:

Mr. Al Sorkowitz was a Computer Scientist with the Department of the Navy where he was responsible for developing large, real-time software intensive systems. Prior to joining the Dept of the Navy, he was Director of the Standards and Quality Control Staff, at the Department of Housing and Urban Development. While at HUD, he initiated a successful testing procedure to improve the quality of unit testing that utilizes automated tools and testing metrics. A paper on this effort was published in a special issue of the IEEE Computer Society magazine "Computer" devoted to Software Quality Assurance, and was later reprinted and widely distributed in the Department of Defense Computer Institute "Selected Computer Articles" The seminars presented by Mr. Sorkowitz are the practical hands-on “lessons learned” by himself and his staff, developing software in-house, as well as the experience working with a large number of software contractors. Mr. Sorkowitz has published papers and has presented seminars on Software Metrics, SQA, and Testing at conferences sponsored by the IEEE Computer Society, ACM, DPMA, and the British Computer Society.

Alfred Sorkowitz