
Below is a list of presentations that will be given during the two day conference of ICSPI (April 4&5th, 2006). To view a presentations outline; click on the presentations title.
Tuesday, April 4, 2006
Wednesday, April 5, 2006
|

New Technologies in Support of Multiple Releases
Barbara Dumas
Director of SCM Solutions
McCabe Software, Inc.
Introduction:
According to industry surveys, well over 50% of software companies are reporting an increase in the frequency of releases resulting in an overlap in supported code lines. The number of Independent Software Vendors (ISVs) supporting multiple releases in parallel is also on the rise. This translates to an even greater need for version control tools that can effectively support parallel code streams. This paper discusses the use of process and technology to address the requirements of organizations struggling to maintain multiple releases in parallel.
Outline:
- Short Discussion of the Dependent Delta Model
- Best Practices in Controlling and Releasing Change
- Introduction Selective Migration
- Adding Selective Migration to the Process
- Risks Associated with Support for Parallel Releases
Learning Objectives:
- Identifying various methodology used for version control
- Best Practices in Controlling and Releasing Change
- Change Management Process
- Best Practices in Naming Parallel Releases
- Identifying Risks in the Application Lifecycle
Biography:
With over 25 years of experience in SCM, Ms. Dumas' previously held executive level positions include Project Management, Engineering and Management Consulting. Barbara has worked internationally with large customers to provide Software Configuration Management Consulting with a focus in software development process for financial environments and complex environments. She currently serves as Director of SCM Services at McCabe Software, a provider of Application Lifecycle Management Solutions.

Continuous Improvement, Make it Visible!
Ben Linders
Manager Operational Development & Quality
Ericsson Telecommunicatie B.V.
Introduction:
Communication is an important factor in improvement programs. Communication pictures the goals and approach of an improvement program. It can motivate people to commit to change, by showing expected benefits and early results. But wrong or too much communication can also frustrate people, getting them to resist changing.
Many improvement programs are run by technical persons, in a technical environment. Often communication is undervalued and underestimated, and perceived as difficult. It is something that people are inexperienced in, which makes them feel uncomfortable. But if they get started, and take some hurdles, they can get better in it. This presentation provides hands-on information, and hint & tips.
This presentation will show how vital communication is for improvement programs. It supplies a set of tools and techniques to improve the visibility of targets and results, and will explain how this has been used to monitor and steer continuous improvement in an R&D organization. Views on continuous improvement from different stakeholders are included, to show their needs on communication.
Learning Objectives/Outline:
Understand the importance of visibility in continuous improvement
An overview of communication tools, with deployment for improvement programs
Advantages and risks of communication
Show the different needs from stakeholders regarding communication
Show how targets can be set and measured on continuous improvement
Biography:
Ben Linders is Specialist Operational Development & Quality at Ericsson Telecommunicatie B.V., the Netherlands. He has a Bachelor in Computer Science, and did a Master study on Organizational Change. He works in process- and organizational improvement for more then 15 years, implementing high maturity practices, to improve organizational performance and bring business benefits.
Since 2000 he leads the Defect Prevention program. He coaches implementation of Root Cause Analysis), Reviews and Inspections, and has defined and applied a Project Defect Model, used for quantitative management of the quality of products and effectiveness of verification.
Also he introduced and supports the measurement system, manages continuous improvement, and is an expert and coach in several Organizational Performance & Quality areas.
He is a member of several (national and international) SPI and quality related networks, has written several papers, and regularly gives presentations. Recent presentations were at the ICSTest 2004 conference, European SEPG 2004 conference, and the Better Software 2004 conference.

Pains and Gains to Maturity
Ambrish Srivastava & Jesse DeGuzman
SQA Engineer's
Tata Consultancy Services & Motorola Inc.
Introduction:
The Motorola Networks business Customer Solutions & Information (CSI) organization provides Information Technology (IT) support to several business areas in several countries within Motorola. Up until June of 2004, the Networks business CSI was an un-assessed organization according to the Methodology of the Software Engineering Institute (SEI). CSI organization adopted the process improvement framework of the CMM model. This paper is an exposition of the organization's hardships and elations toward achieving the CMM level 3 credential and continuing the unfinished journey to further process improvements. This papers also details the explorations of possible solutions to several encounters, ensuring that the solutions are effective and unified across the global expanse of the organization. Its intended members of the audience are those who are engaged in Software Process Improvements.
Outline:
- Information Technology (IT) support to several business areas in several countries within Motorola.
- An un-assessed organization according to the Methodology of the Software Engineering Institute (SEI).
- Hardships and elations toward achieving the CMM level 3 credential
- Continuing the unfinished journey to further process improvements.
- Explorations of possible solutions to several encounters
- Solutions are effective and unified across the global expanse of the
Learning Objectives:
- Understanding Issues and solutions
- Identifying risks and mitigations
- Unified framework for process improvements
- Changed Management
- Quality Management structure
Biography:
Ambrish K Srivastava during his experience of 6 years in TCS has led and executed assignments in the realm of Software Quality area, Application Development and Maintenance and has driven a number of Quality initiatives in and outside TCS. He has extensive experience in Project Management, Estimation, SPC, Client and Team Management. On the Process Improvement Front, He has executed consulting project in Taiwan . He was Assessment Team member for internal CMM L5 Assessments. He is actively involved in TCS integrated-Quality Management System project audits, internal process assessments in line with CMMI L5 and PCMM L5, and SEPG activities. He is trained on CMMI methodology by Ron Radice. He has taken part actively in internal process assessments in line with CMMI L5 and PCMM L5 at TCS.
Jesse DeGuzman is a 22 year Motorolan. Jesse's career with Motorola started in manufacturing as an Industrial Engineer implementing improvements in line balancing, manufacturing facilities, processes and materials management. Jesse's expertise includes creating simulation models for manufacturing load balancing and Quick Changeovers. Jesse led the Manufacturing teams achieving the first Motorola ISO9000 certification in 1995. Jesse's recent experience embraces participation in various Oracle implementation to Global regions and becoming knowledge expert in the BOM/Engineering module. Jesse is currently an SQA Engineer for the Networks business Customer Solutions and Information (CSI) organization and recently received training in CMMI.

Optimized Implementation Methodology (OIM)
Kulpreet Singh Nanda
Software Process Consultant
Patni Computer Systems Inc.
Introduction:
PROBLEM STATEMENT Process is a buzz word to achieve high quality of products in IT world. Most of the organizations having ‘mature' process experience would agree that process design (definition) and its implementation are the key factors to obtain good returns from a process. Process implementation causes defined processes to be performed routinely, resulting in institutionalization throughout the organization. Institutionalization is achieved by blending process training & mentoring, support & communication, tool training, support mechanisms, metrics, and infrastructure forcontinuous improvement. Most of the time, achieving good process definition is easy compared to good implementation of the process. The foremost challenge is to align behaviors of employees to accomplish process compliance.
The existing industry practices such as audit or assessment help gauge health of the process at higher levels rather than gauging the depth of implementation of the individual process at a granular level. Most of the time, we don't know the state of implementation granularly. Hence the actions which are required to be taken to address root cause are taken at high level, leaving the process implementation to an ineffective stage.
SOLUTION
OIM (Optimized Implementation Methodology) is a focused methodology which can measure implementation at granular level & draw a roadmap for process improvement to overcome the challenges of ineffective implementation.
This methodology leverages the existing techniques & concepts like PDCA (plan, do, check and act), RCA (root cause analysis), SQC (Statistical quality control) and tools like QFD (quality function deployment), Relative Prioritization Metrics, weighted scoring etc. It starts with measuring and understanding the current state of implementation effectiveness. Further it helps creating a roadmap to ensure process institutionalization. This way of measurement is granular enough to provide deeper understanding of root causes of ineffective implementation.
Outline:
- FUNDAMENTALS OF PROCESS DOMAIN
- IMPLEMENTATION CHALLENGES
- SOLUTION : OIM (Optimized Implementation Methodology)
-
Logically break the process into sub-processes /procedures/ tasks.
- Use Relative Prioritization Metrics to calculate & understand the relative importance of the sub processes with respect to the process goal.
- Create questions (with objective guidelines) which can gauge the state of implementation of each sub process at depth.
-
Use QFD to calculate and understand the weights of the questions depending upon their relationship with the important sub processes.
- Gather data about process compliance.
- Calculate the Implementation Effectiveness Score and analyze the data for identifying the areas of improvement.
- Define action plan for areas of improvement and categorise them into people, process and tools.
- Gather the compliance data at defined intervals and monitor the impact of action plan.
- THE MODEL
- CASE STUDY
- KEY SUCCESS FACTORS
- CONCLUSION
Learning Objectives:
- Challenges of Process Implementation
- What is OIM (Optimized Implementation Methodology)?
- How to gauge Process Implementation at depth using OIM?
- Advantages of OIM
- Integration of OIM with existing practices of Assessment and Audit
- How to use OIM for a process environment
Biography:
Kulpreet Singh Nanda works as a Software Process Consultant at Quality and Delivery Innovation Department, Patni Computer Systems Inc. He has worked on various quality and process improvement initiatives like ISO 9000, CMM, CMMI, TQM and Six Sigma.Kulpreet is a Certified Software Quality Analyst by QAI, FL and certified Six Sigma Green Belt by PATNI.
He has more than 6 years of experience in the field of Quality Management and 1 year of experience in Marketing & Advertising. He has been a member of SEPG and worked as in-charge of Internal Quality Audits for Patni. Kulpreet has successfully conducted process improvements for Patni and its clients and he is currently deployed at client's site on a process consultancy assignment for Patni.
Kulpreet has following experience with the subject of paper & presentation:
- Methodology Development
- Methodology Pilot
- Methodology Implementation


Metrics and SPC Analysis Techniques that Really Help in Quantitative Project Management
Dr. Kanhaiya Jethani
Senior Consultant
Tata Consultancy Services
Introduction:
Statistical process control has its origins in manufacturing industry where these techniques are used to monitor and control the performance of single machines or processes. Software industry has also started using SPC techniques for quantitative management of processes. However, there are dissimilarities between the manufacturing and software industry which have a bearing on the applicability of SPC techniques.
Quite often the metrics and SPC analysis technique selection is not accorded due importance. Metrics and SPC analysis techniques are routinely selected to satisfy the requirements of software process improvement frameworks. Considerable time and effort is spent in collecting metrics and doing SPC analysis without realizing the benefits. This may be due to inadequate understanding of the linkages between the selected metrics and the underlying processes.
The SPC analysis techniques may also not be selected correctly due to lack of understanding about the desired process monitoring and control. This paper discusses the pitfalls of incorrect usage and benefits of choosing appropriate metrics and SPC analysis techniques based on observations in several organizations.
Outline:
- Introduction
- The Premise of SPC techniques
- Differences between manufacturing and software environment
- Metrics definitions
- Common Metrics Usage
- Pitfalls in common usage of metrics
- Examples of incorrect and correct usage of metrics
- Precautions while defining metrics for software processes
- Common usage of SPC Analysis
- Examples of correct and incorrect usage of SPC techniques for analysis
- Precautions while selecting SPC techniques for analysis
- Conclusion
Learning Objectives:
- How to avoid incorrect metrics definition
- How to ensure correct metrics definition
- How to avoid incorrect selection of SPC analysis techniques
- How to ensure correct selection of SPC analysis techniques
Biography:
Dr. Kanhaiya Jethani is currently working in the Quality Consulting Service Practice of TCS. He has been involved in Software Process Improvement projects for clients in Taiwan , Singapore , Spain , USA and Japan . He has previously worked as SEPG head in TCS for 2 years. He has been associated with TCS for 15 years and worked on many software projects in the area of Process Control for steel, cement and chemical industries in India . He is a Certified Software Quality Analyst (CSQA) and Project Management Professional (PMP). He is an Assessor for Software CMM®, and a Candidate SCAMPI Appraiser. As an Assessor he has experience in conducting a number of CMM and CMMI assessments and gap analysis internally within TCS and for external customers.
A Doctorate in Chemical Engineering from Oklahoma State University, USA, he was also a Post-Doctoral Research Fellow at Oklahoma State University, USA and University Department of Chemical Technology (UDCT), Mumbai, India. He is a member of PMI.


Software Quality Metric for Complex Systems
Evelyn F. Moritz
Consulting Member of Technical Staff
Avaya
Introduction:
In the System Test and Beta phase of product development, two questions often arise:
- Are we on track to launch the product on the target date?
- How does the quality of this release compare with previous releases?
For complex software products, the answers to these questions are not straightforward. A number of metrics are needed to adequately capture the software quality and often these metrics indicate contradictory information. For example, the defect find rate may be low (good) but a number of critical open (unresolved) defects may still exist; or there may exist a large number of open medium severity defects but system stability is solid. A method was needed to provide a simple representation of product quality to monitor progress during system test and product trials to facilitate business decisions regarding when a product was at an acceptable quality level for general availability.
Once the metric was established, we needed to verify its accuracy with customer data. Is Release X really better (or worse) than Release Y?
A Software Quality composite metric was developed 3 years ago and has been in use for the past 6 releases of AVAYA's largest software product. It has helped us answer the fundamental questions mentioned above. Additionally, data gathered from customer sites has substantiated that the metric is reasonably accurate. This approach is now being used by other projects at AVAYA.
The primary purpose of the metric is to provide a means of distilling a large amount of technical data into a format that can be better understood by business leaders. It is not meant to replace the underlying need for a variety of quality measures.
Outline:
- What is a Software Quality (SQ) composite metric
- Why have a composite metric
- Examples of how quality information was presented to business leaders in the past
- Advantages of a composite metric
- What type of software products would benefit from an SQ composite metric and when would a composite metric not be applicable.
- What measures should be considered as candidate components for an SQ composite
- Specific metrics chosen for the SQ composite metric (there are 10)
- Other candidate metrics
- How are target values (goals) established
- Establishing composite SQ goal for software release based on discussions with Product Managers – Framing the expectations for product quality
- Should a release be targeted to improve quality?
- Maintain existing quality?
- Will degradation in quality be tolerated due to introduction of new technology into the marketplace?
- Establishing component targets based on historic data
- Examples of the metric in use
- Graphs showing actual vs. target progress of a new release
- What an “on target” release looks like
- What happens when quality is not “on track” – adjustments to graph when launch date is slipped
- What happens to graph when content is removed
- Bar chart showing release-to-release quality comparison
- Caveats
- General concerns and challenges regarding any software metric
- Specific concerns regarding a composite metric
- Using customer defect data (software product defects found at customer sites) to determine software release quality
- What data needs to be collected
- Challenges associated with collecting/processing data
- Some simple (though potentially inaccurate) approaches
- A more accurate (and sophisticated) approach
- Graph showing actual release data
Learning Objectives:
- Challenges with interpreting software quality data in the business context
- Metrics/measures to track product quality during the system test interval
- How a software quality composite metric can be used to track product quality and facilitate product launch decisions
- How to create a software quality composite metric
- Examples of how a composite metric is being used on a large commercial software system.
- Challenges and concerns regarding software metrics in general and a composite metric in particular
- Challenges associated with determining if product quality has improved once a new release has launched (general availability)
- Examples of some straightforward methods and their pitfalls
- Example of a more sophisticated approach that is currently in use
Biography:
Evelyn Moritz received an MS in Computer Science from the University of Colorado , Boulder in 1978 and joined AT&T Bell Labs that year, developing software tools for PBX switching systems. She moved to System Test in the 80's with a focus on network and performance testing of large switches. From there, she became a coordinator of System Test activities responsible for quality assurance of Lucent's Enterprise switching products. During this period she participated in a variety of process improvement activities and developed a common system test process that became standard for the Lucent Enterprise product line.
She has had direct experience with the "end-game" of every major release of Lucent/AVAYA Enterprise Communications software products for the past 10 years. These software products are in use at over 50,000 sites world-wide. She has navigated the seas of change in the telecommunications and software development industries, adapting processes to respond to today's demands for rapid time-to-market, while still maintaining a high standard of product quality.
As a Consulting Member of Technical Staff at AVAYA, she has developed a suite of software metrics to measure both product and process quality. She continues to consult with AVAYA projects to develop better test strategies, improve test processes and improve overall product quality.


Thriving in a Diverse Environment Through Technology Change Management
Barbara Dreon
Technology Change Management Lead
Northrop Grumman Corporation
Introduction:
It can be a challenge to envision how to apply Technology Change Management (TCM) in an organization that serves many unrelated customers with a myriad of systems and technologies. Northrop Grumman has adapted its approach to TCM to accommodate this diversity. The presentation highlights the market for and benefits of TCM, touches on a paradigm for success, and couples an industry model used for technology change with mechanisms used by Northrop Grumman to strengthen its technology monitoring capabilities and its ability to more efficiently deploy a technology across multiple projects. Supporting data for the ideas are drawn from industry and from within the company. These ideas can be adapted for use in other organizations. The presentation is accompanied by a detailed white paper.
Outline:
- Brief background: concepts and context for understanding technology change management (TCM) approach
- Examples from industry and within Northrop Grumman showing the usefulness and benefit of technology change management
- Common challenges to deploying TCM in a diverse environment
- Overview of the TCM process in use at Northrop Grumman
- Technology Identification and Monitoring
- Technology Evaluation and Selection
- Technology Planning
- Technology Development and Insertion (including technology replication)
- The importance of people in the success of technology transfer
- Enablers to transfer technology to disparate recipients (organized in terms of a model for learning or technology adoption known as the Patterson-Connor model)
Learning Objectives:
- Be able to define technology change management (TCM) and related terms
- Understand why TCM is important and beneficial
- Be aware of an instantiation of a TCM process that is used successfully in a diverse environment
- See the Patterson-Conner Model applied to change adoption and combine it with ideas to increase success in transitioning technology changes to multiple parts of an organization
- Recognize some opportunities and issues for technology insertion and technology transition
- Based on industry data and company experience presented, be ready to select some ideas to apply in another organization
Biography:
Ms. Dreon is a Technology Change Management Lead in Northrop Grumman Corporation. She has over 10 years of experience in process improvement for software and systems engineering and works for a company that has achieved over 18 CMMI Level 5 ratings. She has an M.S. in Operations Research and enjoys helping projects and groups apply process discipline to creatively suit their goals. She is also an instructor and has provided past presentations at industry forums on such topics as technology change management, process improvement, process asset libraries, and measurement.


Me Facilitate the Session: Fundamentals of Meeting Facilitation
Clyneice Chaney
Quality Manager
Project Performance Corporation
Introduction:
Facilitated sessions are being used in a variety of ways, from gathering requirements, identifying risks, designing processes and performing inspections and reviews. The facilitator's role is to help a group to its best thinking. A good facilitator is helpful when a group is trying to deal with new or difficult issues. In the main, a facilitator helps people persevere as they confront the inevitable confusion and frustration associated with trying to integrate different views and approaches with their own. The more people who learn to facilitate the better. This presentation walks you through the basic steps to become a better facilitator.
Outline:
- Meeting and Facilitation
- Key Facilitator role
- Five Principles of Facilitation
- Meeting Planning and Preparation
- Managing the Session
Learning Objectives:
- Understand the facilitator role in meetings and improvement sessions
- Understand the principles of good facilitation
- Know how to prepare for a meeting as a facilitator
- Know how to manage the facilitation session
- Know how to manage the data and information from a variety of “types” of facilitated sessions
Biography:
Clyneice Chaney, Corporate Quality Manager with Project Performance Corporation brings over 20 years of testing, quality assurance and process improvement experience. Clyneice holds certifications from American Society for Quality as a Certified Quality Manager, Quality Assurance Institute's Certified Quality Analyst, and Project Management Institute's Professional Project Manager. She has served on the Board of Examiners for Virginia and Georgia 's State Quality Awards.
Focusing on process improvement and procedure development in the software testing and quality assurance areas, Clyneice has successfully lead process improvement, methodology development, and reengineering projects for organizations wishing to improve their software development, testing processes, and tool implementation.
Clyneice is currently an instructor for the International Institute for Software Testing and has presented technical papers at the Software Engineering Institute: SEPG Conference, American Society for Quality: Quality Manager's conference, Quality Assurance Institute International Testing conference and STAR East Testing and the Quality Assurance conference.


Wasted Days and Wasted Nights: Leveraging Your Appraisal Teams as a Resource
Tim Davis
Senior Engineer Manager
Raytheon Missile Systems
Introduction:
The scene opens on the program's personnel frantically trying to finish up the task of putting best representative evidence into the PII database before Appraisal Team arrives on Monday for the next readiness review, ok at this point any evidence will do. Frustration is written on these frantic faces, as the appraisal team has been her twice now and the keep saying the same thing, “These rocks are no good, go get different sent of rocks!!” And in the minds of the program folks are the repeated thoughts: “ If there so darn smart how come they don't just come and get the data themselves. Then I would not have to be here ‘til mid-night again.”
Scene two opens and the appraisal mini-teams are grinding on their third late night, trying to dig through the contents of the PII data base and make some sense of how the evidence is representative of the process areas being reviewed. Someone yells out in frustration “ When are these guys going to learn to simply give us the evidence we need that confirms that the process is being executed at the program level???” Heads nod in recognition that they probably have gotten closer this time, but they ain't there yet.
Raytheon Missile Systems experience this frustrating series of do-overs early on, when going down the path towards achieving CMMI level 3. In fact at the rate that the programs were spiraling in on getting the right evidence, there was a real risk that the schedule for the goal of achieving that level 3 was a risk. RMS quickly realized that what was needed was a method of bringing the appraisal team's knowledge of the model and PII's in to the program's data collection process without the normal back and forth communication which results from information requests only the author can decipher. What resulted was the implementation of series of meetings between individual appraisal team members and the program personnel assigned as evidence collectors. Detailed information provide by the appraisal team member allowed the program personnel to gain insight on what the CMMI model was looking for down at the SP and GP level. The program personnel were then able quickly identify what types products best represented evidence that the program was meeting the intent of the model. In the case of multiple pieces of evidence, the appraisal team member provided feedback on which products were the most relevant to the SP or GP being discussed.
The impact of these reviews far exceeded expectations as noted in the findings from the SCAMPI B that followed these reviews. The quality and relevance of the evidence went up dramatically and the quantity of the evidence and risk went down dramatically. And neither group, evidence collectors or appraisal team, were spending wasted nights collecting or reviewing bad evidence. In this presentation, we will offer up details of how this process was implemented and how it can be used by any organization to streamline the collection of PII information.
Outline:
- Past Experiences
- Reason to Do It Better
- Shoulder to Shoulder Process
- Benefits
- Results
- Summary
- Questions
Learning Objectives:
- Why the traditional process caused confusion and delays
- There is a better, faster way to do things
- How the shoulder to should benefits the organization and people, as well as the SCAMPI
- How to save time in your SCAMPI preparation
- How not to mess up the things that are working well
- The benefits of doing shoulder-to-shoulders – time, cost, frustration, learning
Biography:
Tim Davis is currently a senior engineer manager at Raytheon Missile's Tucson facility and heads a systems engineering department which supports the Air-to-Air and Land Combat product lines. His thirty one year career with the company has been split almost evenly between embedded tactical software development and systems engineering activities.
His tour of duties as a lead software developer have included numerous CMM assessments up to and including CMM level 4. This legacy followed Tim to the systems engineering environment, where he has been providing active support for achieving the Corporate CMMI goals. During 2003, Tim was an Appraisal Team Member for two SCAMPI “B” level appraisals and the SCAMPI “A” SW/SE level 3 appraisal of the Raytheon SAS Business Unit. Currently, he is assigned as an Appraisal Team Member for the Missile Systems CMMI level 3 initiative as well as an ATM for the Raytheon SAS CMMI level 4 efforts.


Using Object-oriented Metrics to Improve Software Development
Andy Cobb
Instructor
University of Louisville
Introduction:
The paper focuses on a case study in which high level object-oriented design metrics are used to predict lines of code and defects. These models are unique in that they use high-level metrics, available during the early design phase and extracted from Unified Modeling Language class diagrams, for the prediction models. These models are presented with the purpose of aiding project managers and software managers in making decisions during the software development process.
Outline:
- Introduction/Problem Definition
- The value of discovering complex or defect-prone classes early in
- Determining/Allocating coding resources
- Determining/Allocating testing resources
- Background
- Object-oriented Metrics
- Validation of the metrics
- Metrics that we used
- Our model for code size prediction
- Our model for defect prediction
- Applying the metrics
- Design Phase
- Coding Phase
- Testing Phase
- Conclusion
Learning Objectives:
- Provide definitions for several object-oriented metrics
- Provide background on how object-oriented metrics are used in the improvement of software development
- Provide a model for prediction of lines of code from high-level object-oriented design metrics
- Provide a model for defect prediction from object-oriented metrics
- Propose methods for applying these models to the software development process
Biography:
Andy Cobb has worked as an Information Systems professional for six years as developer, development manager, manager of architecture and VP of technology. He was involved in a major software process improvement initiative with a Fortune 200 company in which he investigated many of the concepts presented here. He is currently a PhD candidate in the Computer Engineering and Computer Science program with a focus on objected-oriented software process improvement.


A Practical Approach to Process Improvement
Robert Fantina
Corporate Process Analyst
NorthwesTel, Inc.
Introduction:
Many organizations struggle with improving processes while trying to meet deadlines. They know that the implementation of efficient processes will greatly aid in meeting schedules, remaining within budget and creating high-quality products and services. Yet determining what process changes need to be made, and then implementing them, is often seen as too time-consuming regardless of the value they will bring. The rush to get products and services to market ahead of competitors often overwhelms all other considerations.
This presentation will provide participants with the tools needed to identify the areas of highest concern, determine the changes that need to be made and then implement them, without any significant drain of time from project work. Participants will complete exercises relating to their own organizations that they can use as a starting point for process improvement. Information will be provided on how to help change-resistant cultures to ensure success.
It is not unusual for organizations to be intimidated by the thought of a process improvement initiative. They picture costly consultants, a significant time commitment by their employees, and months before they see any benefit. This presentation will provide the participants with tools that can be easily and quickly implemented on their own projects or within their own organizations, and that will bring results within weeks, not months. Certainly there is a commitment of time, but it will be shown to be an investment rather than an expenditure.
As part of the exercises, templates will be distributed that will be useful for the participants. Seeing and using the templates will assist with the learning process, as each participant relates what is taught in a very direct way to his/her own work environment. Whether it is a project manager needing to gain control of his/her own projects, or a company director, vice-president or CEO who sees the need for better controls, they will leave this presentation with the tools necessary to start and complete an effective process improvement initiative.
Outline:
- Introduction. I will discuss each area and include experiences I have had in order to assist with learning.
- Basic overview of process improvement areas
- Project Planning
- What it means
- Why it's needed
- Reasons it's often avoided
- Project Management
- How to manage to the plan
- Requirements Management
- Advantages of a template
- Need to baseline
- Need for formal change control
- Subcontractor Management
- Benefits to the organization
- Common reasons for failure
- Formula for success
- Quality Assurance
- Setting quality assurance standards
- Accountability
- Configuration Management
- Problems that it prevents
- Simple methods to implement it
- Determining Major Problem Areas
- Gap Analysis
- Use of template for each area (template will be provided)
- Exercise: Complete the templates as they relate to your organization.
- Question/Answer period
- Prioritization
- Determining what areas in your organization need immediate focus.
- What problems are causing the most ‘pain'
- What efforts will bring the best results most quickly?
- What areas, if addressed, will have the most significant impact
- New Process Creation
- Obtaining input from key stakeholders
- How long should this take?
- Overcoming objections
- Documenting process drafts
- New process review
- Review new and/or revised processes with the stakeholders who provided input
- Approximate time commitment asked for
- Implementation
- Obtaining buy-in from resistant personnel
- Common reasons for resistance
- Overcoming management resistance
- Overcoming team-member resistance
- Introducing the new process
- Selecting a pilot project
- Training the team
- Ongoing monitorin
- Revising the process
- Rollout of new process
- Overview training
- Coaching and mentoring
Learning Objectives:
- How to start
- Explanation of Gap Analysis
- Exercise on Gap Analysis
- Prioritization
- Discussion on problems
- Root cause analysis
- Creating a process
- Interviews with stakeholders
- How to approach them
- Dealing with resistance
- Templates for new processes
- What they should contain
- Recommended, tailorable format
- Reviewing drafts with stakeholders
- Piloting the process
- Selecting a project
- Training the project team
- Maximizing opportunities for early success
- Assuring that the selected project has ‘early adapters’ on the team.
- Rollout to the organization
- Training the team
- Overview training
- Detailed training
- Dealing with resistance
- Understanding its causes
- Addressing the cause
Biography:
Mr. Fantina has been involved in process improvement since 1996. As a project manager at Lucent Technologies in New Jersey he was responsible for implementing CMM Level 2 and 3 processes, and coordinating CMM assessments.
His next assignment was on a CMM Level 2 initiative at Merrill Lynch in Princeton , NJ . There he revised current processes and worked with stakeholders to assure that the processes were CMM Level 2 compliant, and yet were workable within the current corporate culture.
Later, at Charles Jones, LLC, also in NJ, he successfully implemented a variety of processes designed to assist the organization in maintaining budgets and delivering services on time. This included the implementation of project planning and tracking processes and tools, as well as a requirements process and configuration management. He successfully bridged the gap between the business side of the company - mainly marketing – and the technical side, enabling a smoother working relationship between them and thus more effective project implementation.
At each organization he successfully overcame the resistance that is common, especially when long-term employees have been performing their duties in a specific manner for an extensive period of time.
Following his two-year assignment at Charles Jones, LLC, Mr. Fantina served as Process Facilitator/Training Coordinator on a CMM Level 3 initiative at Motorola in Florida . The organization was successfully assessed at Level 3 in December of 2004.
Currently Mr. Fantina is an employee of NorthwesTel Inc. in Whitehorse , Yukon Territory , Canada . His main area of focus is New Service Introduction. Similar to his earlier positions, his current role involves him in both business process improvement and software development process improvement.
Mr. Fantina is the author of Practical Software Process Improvement , published by Artech House Publishers in March of 2005. The book is replete with examples from his wide experience in process improvement.


Agile Principles Applied to Software Process Development
Mary Behnke
Software Process Engineer
Raytheon Missile Systems
Introduction:
This presentation will describe the Agile principles from a process perspective, how these principles can be applied to the development and maintenance of software processes. This presentation will also discuss how the Agile methods “fit” the CMM/CMMI.
Outline:
- Agile Principles and how they apply to software and software process
- Incremental and Iterative process definition
- Adaptive planning and processes
- Lessons learned
- Metrics
- CMM/CMMI compliance
Learning Objectives:
- Understanding of the Agile principles and how they apply to software process
- Using Agile principles to develop/maintain incremental and iterative software processes
- How adaptive planning can be used for process improvements
- Use of metrics to aid in process improvement in an Agile environment
- CMM/CMMI compliance in an Agile
Biography:
Mary Behnke has over 19 years of software development experience. She started working at the Naval Air Warfare Center as a software developer and tester. She was a software lead for both development and maintenance programs, defining the software processes for the developers, SQA and SCM and managing software teams. She was the SEPG lead for 2 years at the Naval Air Warfare Center . She worked at a medical devices company and started an SQA organization in the IT department. Mary started working at Raytheon Missile Systems in 1999 as a Software Quality Engineer. She became the Air-To-Air Software Process Engineer (SPE) in 2000 and has been providing software process expertise in support of the programs within the Air-To-Air product line. Mary has been developing and implementing Agile processes for the Air-To-Air product line for the past 2+ years.


Successfully Implementing and Improving Processes in a Dynamic, Concensus-Driven Software Organization
Bob Reed
Product Lifecycle Management System Manager
Synopsys, Inc.
Introduction:
Have you ever worked with a team to overhaul their development processes and the product still fails? Or have you watched a team who is following all the right steps in product development, but you sense that the “content” within the process may be wrong? Or a team dramatically improves their product testing and quality, but still the product bombs with the customers?
The solution: With any process or quality improvements, always make sure there's a Product Strategic Planning Process. (Having a corporate Strategic Planning Process is not enough!)
In this presentation, Bob motivates people who think about process and quality improvement to also think about the Strategic Planning Process. He outlines a blueprint for a Strategic Planning Process and explains how the process can drive significant “non process” improvements, such as getting the right people and getting the right reporting structure. He uses audience participation to discuss how much to implement, and how to extract valuable knowledge from a team that may never have thought about strategic planning. Then he provides a valuable tool to solve the next set of challenges: How do you make sure that the execution matches the strategic planning? At what level do you write requirements without overwhelming the team? At what level do you write specs and develop detailed plans? Throughout the presentation, Bob uses examples from his latest work with a “strategically challenged” product team.
Outline:
- Audience survey
- Role
- Strategic challenges?
- Participation in strategy and strategic planning
- The Problem
- Strategic Planning Process Blueprint
- Implementing a Strategic Planning Process
- How much to implement
- Training
- Examples of Mining the valuable information within a team
- Extracting needed “non-process” improvements
- Going from Strategy to Implementation
- Tool for ensuring alignment at all levels of planning
- Determining the level for requirements, plans & specs
- Driving “non-process” improvements
- For more information: the Reading List
Learning Objectives:
- Understand the “non-process” elements to an organization, product or project that may cause it to fail.
- Understand Strategic Planning
- Awareness of the need for a Strategic Planning process
- How to implement and facilitate Strategic Planning
- How to extract and solve non-process issues
- How to ensure execution of a Strategic Plan
Biography:
Bob Reed (BSEE 1988 Oregon State University; MSCE 1989 Stanford) is the expert at Synopsys in Product Lifecycle Management. Synopsys develops software tools in the Electronic Design Automation industry to help its customers, such as IBM, Intel and HP, design and verify complex integrated circuits.
Bob started his career at Intel as a microprocessor applications engineer. When he moved to Synopsys 12 years ago, it was just growing out of startup. Bob became much more fascinated with how to design and build great teams and organizations rather than designing and building hardware and software. Bob has spent the last eight years of his career working at all levels of Synopsys in implementing everything from Strategic Planning to how software programmers integrate their code. He has worked on organizing teams, developing processes, training…with team members from all functional groups, such as Marketing, applications engineering, support and R&D.
Although Synopsys has grown considerably, it still retains a very dynamic, fast-paced, and consensus-driven culture. Meanwhile, Bob has worked with very little formal authority, so he has developed many skills and techniques that create amazing results in the teams and business units he's helped. Even more amazing is that he has worked “out of his home” for the past six years so that his children could grow up near their grandparents. With about three days a month of travel, he's produced dramatic changes in organizations from across the US to India , China and Europe .


Metrics as an Early-Warning System for Software Development Projects
Willy Druyts
Business Process Analyst
AGFA
Introduction:
Software development projects are often said to rarely reach their objectives within their constraints of time and budget.
An early-warning system that collects and reports metrics on key project characteristics can trigger corrective measures timely and set the project back on its intended course.
The selection of the appropriate metrics is essential to be effective.
Each metric must be available early, relate to a particular (development) process to enable a drill-down to root causes and appeal to the various stakeholders of a development project. The latter can be summarized as:
- People working in the project: the developers, the architect, testers, etc…
- People managing the project: the project manager, his or her core team members, etc…
- People controlling the project: sponsors, a steering committee, portfolio managers, etc…
The required technology ranges from simple to having an enterprise-level complexity:
Most tools offer basic reporting facilities to count the number of items being currently worked on; e.g. the number of lines of code, the number of defects, etc…
Slightly more advanced is automating the collection and use the tool's API or consolidating information from various sources in a single database.
Experience though, has shown that determining the information needs up-front is difficult. If required, data warehousing technology can be considered.
As in any metrics-project, the true challenge is in mobilizing the people and the organization. The detrimental effects of not involving stakeholders and of inappropriate use have already been described in great length. All apply in this case.
The presentation includes a description of the system being used in the author's development environment. The aforementioned aspects will be covered as well as the link to the process improvement program.
API : Application Programming Interface. Most tools expose their functionality not only via the user interface, but to an external application as well. This ‘interface' is called the API.
Outline:
- Problem statement :
- discover ‘bad smells' sufficiently in advance to allow corrective actions
- provide suitable information for the various stakeholders
- Requirements for correctly defining and interpreting project information
- State the performance ( improvement ) objectives
- Define the context : the methodology, the project lifecycle, the processes and deliverables
- Track the best practices and lessons learned
- The Goal-Question-Metric paradigm revisited
- Technology choices
- Out-of-the-box possibilities of software development tools
- Extending standard features by using the tool's API
- Reasons ( not ) to consider data warehousing technology
- The Human and organizational side
- People don't like being measured
- Organizational measures to support a measurement culture
- An implementation example
- Project items being tracked :
- Adherence to various best practices
- Size indicators and growth rates
- Final performance
- Link to the process improvement program
- The technology
- The organization
- Lessons learned
Learning Objectives:
This presentation demonstrates
- how to create an early-warning system that is capable of providing the right information and take corrective measures in a timely manner
- which technologically is available to unlock the information that is already available
- which measures to take to mobilizing the stakeholders
Biography: Willy Druyts is business process analyst for AGFA ( www.agfa.com ).He is responsible for the process improvement program and software development tools at AGFA’s Belgian R&D centre for development of medical imaging systems.
It is his primary role to define and manage projects such as the introduction of iterative development practices, increase product development predictability in geographically dispersed development centres.
His interest in metrics to make software development characteristics more tangible originate from the latter project. Each project takes a holistic view on software development and covers a broad area in software engineering; from requirements engineering over development and unit testing through verification and project management.
As QA-representative for his R&D site, he leads and participates in various activities pertaining to regulatory compliance; such as the validation of software tools, gap analysis, audit preparations, etc…


Help IT Demonstrate its Value: Measurement for Performance and Value
Clyneice Chaney
Quality Manager
Project Performance Corporation
Introduction:
Everyone would agree that 21 century Information technology (IT) organizational is an essential and integral component of corporate operations anode that technology plays a dominate role in corporate strategy. As IT becomes a more critical component of organizational strategy and consumers a growing share of enterprise spending, IT executives are under increasing pressure to demonstrate and measure their accomplishments. These issues are difficult, and to further complicate it there is continued debate on appropriate IT metrics. IT metrics are one of the primary challenges faced by IT executives today.
This presentation focuses on Understanding what to measure so that a demonstration of value can be made. A review of performance measures from the IT perspective, Quality/Testing organization, Customer focus and Development organization focuses will be presented.
Outline:
- IT and Measurement: Where are We Today
- What Needs to Be Measured
- IT Performance
- Quality/Testing Performance
- Customer Focused Performance
- Development Organization Performance
- Putting Performance Metrics in Place
Learning Objectives:
- Understand the need for performance measures in today's environment
- Understand performance measures for an IT organization
- Understand performance measures for Quality/Testing organization
- Understand performance measures for Customer Focused perspective
- Understand performance measures from the Development Organization perspective
- Review high-level steps in implementing new measures
Biography:
Clyneice Chaney, Corporate Quality Manager with Project Performance Corporation brings over 20 years of testing, quality assurance and process improvement experience. Clyneice holds certifications from American Society for Quality as a Certified Quality Manager, Quality Assurance Institute's Certified Quality Analyst, and Project Management Institute's Professional Project Manager. She has served on the Board of Examiners for the Virginia State Quality Exam and the Georgia State (Oglethorpe) Quality Award.
Focusing on process improvement and procedure development in the software testing and quality assurance areas, Clyneice has successfully lead process improvement, methodology development, and reengineering projects for organizations wishing to improve their software development, testing processes, and tool implementation.
Clyneice is currently an instructor for the International Institute for Software Testing and has presented technical papers at the Software Engineering Institute: SEPG Conference, American Society for Quality: Quality Manager's conference, Quality Assurance Institute International Testing conference and STAR East Testing and the Quality Assurance conference.


Used Cars and Lead Appraisers – Lessons Learned
Tim Davis
Senior Engineer Manager
Raytheon Missile Systems
Introduction:
Choosing a lead for your CMMI appraisal team is often like choosing a new car. If you only look at the “polished exterior”, “recently cleaned carpets” and a “quick drive around the block” as your selection criteria for a used car, you are at high risk of getting less than you hoped for in a vehicle. To mitigate this risk, most of us do a lot of homework before ever hitting the used car lots. These same observations are true when comes to choosing the person who is going to have the most direct influence on your organization's goal of a successful CMMI appraisal.
Raytheon Corporation has a total of six business units that been involved in a variety of CMMI appraisal activities, from achieving initial CMMI level 3 to striving to achieve level 4 and 5. Each of the business units has gone through a somewhat arduous and ill defined process of selecting an appraisal lead to support the variety of process improvement and SCAMPI appraisal efforts. And like procuring a used car, the results have been just as varied.
The RMS business unit was faced with that decision recently and concluded that if DAR was good a good model for program decisions, then the application of the DAR principles could be used to select an appraisal team lead. Contacting the other Raytheon business units about their lessons learned from experiences with the lead assessor or assessors that they chose for their CMMI activities. Using this information, RMS developed a set of criteria for a “Lead Appraiser Trade Study”. This paper will provide the details of that criteria, along with SAMPLE outputs from the trade study that reflect the impact of applying weighting factors to the criteria. The intent is to provide an objective framework that could be used by any organization to “Do Their Homework” before making that all important selection of a lead appraiser from the multitude of candidates to be found on the “Lead Appraiser Lot”.
Outline:
- Past Experiences
- Today's Goal
- Applying DAR to the Selection
- Establishing Criteria Through Lessons Learned
- What's Important to Your Organization
- Filling the Candidate Pool
- Summary
- Questions
Learning Objectives:
- Avoiding past mistakes
- Developing criteria to apply to the selection
- Weighting the criteria
- Aligning your organization's needs to a lead appraiser
- Ensure your organization selects a lead appraiser that meets your needs
Biography:
Tim Davis is currently a senior engineer manager at Raytheon Missile's Tucson facility and heads a systems engineering department which supports the Air-to-Air and Land Combat product lines. His thirty one year career with the company has been split almost evenly between embedded tactical software development and systems engineering activities.
His tour of duties as a lead software developer have included numerous CMM assessments up to and including CMM level 4. This legacy followed Tim to the systems engineering environment, where he has been providing active support for achieving the Corporate CMMI goals. During 2003, Tim was an Appraisal Team Member for two SCAMPI “B” level appraisals and the SCAMPI “A” SW/SE level 3 appraisal of the Raytheon SAS Business Unit. Currently, he is assigned as an Appraisal Team Member for the Missile Systems CMMI level 3 initiative as well as an ATM for the Raytheon SAS CMMI level 4 efforts.


Managing Agile Requirements
Wayne Allen
Product Development Manager
Corillian Corporation
Introduction:
Tracking, organizing and managing requirements for agile projects has unique challenges that can trip you up if you don't have a process for dealing with them. This interactive session will show you how to cope with the agile requirements lifecycle. We will talk about where requirements come from, accounting for the planning horizon, "technical" stories, requirements that are "too big", defects, changing requirements, testing, documentation, rework and more. An overview of tools from low tech to high tech will also be covered.
Outline:
Each portion of the presentation will be started with an open discussion of problem attendees are experiencing and what others have tried to do to solve similar issues. Each area of discussion will be captured and made available
- Requirements
- Planning & estimating
- Re-planning based on information gathered from completed iterations
- Non-development activities
- Tool support
Learning Objectives:
- How to manage functional requirements in an iterative process
- How to translate iterative schedules into completion dates
- How to incorporate feedback into an iterative schedule
- How to integrate quality assurance, documentation and other non-development tasks into an iterative plan.
- What types of tools are available and when they are appropriate
Biography:
Wayne Allen is a Product Development Manager for Corillian Corporation. Over the last 19 years he has worked on building appropriate software solutions for various types of organizations both public and private. Over the last 5 years he has specialized in helping organization transition from big bang software delivery to incremental delivery to help increase project success rates and customer satisfaction. During this time he noticed a lack of attention from the Agile community on the non-development roles such as product management, quality assurance, documentation and user interface design. He has been working specifically with these groups to discover ways to improve the larger issue of whole product delivery in addition to the software portion.


A Metrics Perspective for CMMI® Level-4 Organization: Case Study
Sameh S. Zeid
Process Improvement Program Manager
ITSoft
Introduction:
The presentation will address implementation of Metrics in and off-shore software development organization. The Metrics program was implemented to meet CMMI® Level-4 requirements. The CMMI® level 4 provides a platform for continuous process improvement based on metrics values. It gives platform for predicting project performance and serve to have objective language among practitioners. The presentation will address infra-structure for CMMI® Level 4 company and how processes have been evolved till they satisfied the requirements of this level. The presentation will explain the use of Process Performance Baseline and Quantitative Project Management based on Metrics foundation laid in lower levels of the CMMI® Level 4. The presentation will emphasize on quantitative improvement in operational performance using selected metrics.
Outline:
- Business and Operational Benefits of having a Metrics Program
- Uses of Metrics
- A look at some of common metrics
- An infra-structure used to establish a Metrics program for a CMMI® level 4 organization
- Locate and understand Metrics requirements in CMMI® Process Area and Maturity Levels
- How Process Cycle are impacted by implementing CMMI® Level 4 Metrics Requirements
- HR dimension of metrics implementation
- Understand Process Performance Baselines and how they are used by projects.
- A metrics based improvement cycle
Learning Objectives:
- Value the use of Metrics in Software Processes
- Impact of metrics on the way people can work
- Examine and Infra-structure of a Metrics program that was implemented in CMMI® Level 4
- Understand the Process Performance Baselines and Quantitative Project Management
- A look at some of common metrics used during project
Biography:
Sameh S. Zeid skills and Interests include:
- Member of Project Management Institute (PMI) and IEEE.
- Project Management Professional (PMP) from PMI since, July 2001. PMP certification valid till Dec/2007.
- Instructor on various topics of Project Management including Risk Management, Procurement Management, Project Integration and PMP preparation courses.
- Completed the official courses offered by Software Engineering Institute (SEI) on:
- Introduction to CMM, Introduction to CMMI, Intermediate Concepts of CMMI ® , Mastering Process Improvement, Consultation Skills, and CMMI ® Implementation Essentials.


Practical Examples: Using Metrics Trend for Process Improvement
Deborah Devadason
Associate Consultant
Satyam Computer Services Ltd., USA
Introduction:
This presentation shares the practical examples how an innovative approach of using metrics trends for process improvement. Process improvement within software organizations is gaining momentum. More
Organizations today are initiating software process improvement efforts. One of the effective tools to be used in the journey is metrics trend analysis. This presentation shares examples of metrics analysis such as tracking defect discovery rates to predict product release dates, predicting schedules, costs, using control charts to stabilize and improve software processes or to assess process capability, evaluating defect discovery profiles to identify focal areas for process improvement etc.
This provides overview on how to predict or affect future performance using measurements and to manage and improve software processes. These goals invariably can be achieved through metrics trend analysis. This also helps to understand the implications and distinguish between valid and invalid use of measurements. Through this presentation you will be able to understand where responsibilities lie for making predictions come true. This approach is applicable to any industry or any model-based organization (ISO 9001:2000, CMM, CMM-I) as measurement is the heart of any quality process. This also shares some of the industry metrics available for and process improvement Benchmarks
Outline/Learning Objectives:
The audience will be able to understand and appreciate the following:
- How does matured organizations use metrics trends for process improvements
- Practical examples of how various metrics can be analyzed and reported with
- How to use metrics for predicting future performance
- How to show the results of Process improvement to management
- Able to understand some of the industry benchmarks
Biography:
Deborah Devadason is Associate Consultant of the Software Process Consulting Team at Satyam Computer Services, USA , (an SEI CMM & CMMI level 5 Company) with over 9 years of experience in Quality Management. In her CMM and Quality consulting assignments for US and Japanese clients, she has played a key role in Process Definition and Process Integration and Metrics Implementation. She had also successfully implemented Statistical Process Control (SPC) and Process Re-engineering. She holds dual Master degree in Technology and Science. She is a Certified Quality Manager (CQM), Certified Project Management Professional (PMP), holds certification in SPC (Statistical Process Control), MiC Australia and is a certified ISO: 9000 auditor. She has expertise in CMM, CMMI, EFQM models and Six Sigma. She has published papers in International and National Conferences. She has made impressive presentations at multiple organization wide symposiums on Quality Models.


Implementing Project Quality Gates: The Pain, The Agony, The Success
Clyneice Chaney
Quality Manager
Project Performance Corporation
Introduction:
Many projects don't have enough quality controls in place to ensure a quality product. This lack of controls results in products that proceed through the life cycle with major problems and that cause difficulties late in the project when it is costly and time-consuming to fix. This presentation provides a case study of the implementation of a process improvement project design to place the proper controls at the right place to increase product quality.
Outline:
- The Problem
- Organizational Culture: AS IS
- Identifying the problem
- The Fix
- Process improvement initiative
- Integrated Improvement Team
- Process Design and Development
- Implementing
- Lessons Learned
- Things that went wrong
- Things that worked
Learning Objectives:
- Role of process action teams in process improvement
- Steps to implementing improvements
- Tools and templates used for
- Prerequisites for Improvement initiatives
Biography:
Clyneice Chaney, Corporate Quality Manager with Project Performance Corporation brings over 20 years of testing, quality assurance and process improvement experience. Clyneice holds certifications from American Society for Quality as a Certified Quality Manager, Quality Assurance Institute's Certified Quality Analyst, and Project Management Institute's Professional Project Manager. She is a 2003 Georgia Oglethorpe State Quality Award Examiner
Focusing on process improvement and procedure development in the software testing and quality assurance areas, Clyneice has successfully lead process improvement, methodology development, and reengineering projects for organizations wishing to improve their software development, testing processes, and tool implementation.
Clyneice is currently an instructor for the International Institute for Software Testing and has presented technical papers at the Software Engineering Institute: SEPG Conference, American Society for Quality: Quality Manager's conference, Quality Assurance Institute International Testing conference and STAR East Testing and the Quality Assurance conference.


New Generation Software Product Quality Metrics
Raghavan M
General Manager and Head-Quality
Aztec Software and Technology Services Limited
Introduction:
Traditionally, software organizations for a long time now, have been implementing Measurements and Metrics Programs such as variances in size, schedule, effort and cost, productivity, review efficiency etc. and also, product quality metrics such as post delivery defects, defect density These companies have particularly strong processes and development methodologies which are in alignment with high industry standards/models such as SEI-CMM, CMMI etc.,
This paper analyzes the efficacy of these metrics from the point of view of software product organizations. It also deals with some of the drawbacks of these metrics programs and the need for a change. Ideas for a new generation of product quality metrics program, which is in better-sync with the needs of today’s industry, have been evaluated and presented. The suggested Metrics involves measurement of parameters such performance, scalability, maintainability etc. The criteria for measurement/classification of these product quality attributes have also been discussed.
Going further, the paper also deals with implementation details and presents a work-sheet to compute such metrics across the products/projects and across the organization.
Outline/Learning Objectives:
- Introduction
- Current metrics Practices
- Recent Trends and Need for Change
- New Metrics Program
- Basis for Measurements
- Next Steps and Conclusion
Biography:
Raghavan heads the Quality Function and is responsible for all Process related initiatives at Aztec. He has about 17 years of experience in software industry, of which about 5 years have been in Product Testing, 8 years have been in technical project management and 4 years in Process Quality. He has been associated with Aztec since August 2000, and has managed several projects involving Database, Java/J2EE and C/C++ technologies.
Prior to joining Aztec, Raghavan was associated with IBM Global Services India. There, he was instrumental in the development e-business practices. Over a period of 7+ years, Raghavan performed varied roles at IBM including Project Manager, Development Leads, Test Lead and also, had a 3.5 years long stint with various product groups at IBM Boca Raton, Austin and Raleigh. Most recently, as Program Manager, Raghavan was responsible for managing multiple projects in the e-business area and also, as head of e-business competency, including interactions with Global Customers, various IBM Product groups, Services units. Raghavan was also involved in the various Process quality initiatives and was an active member of the Software Engineering Process Group (SEPG). He also served as a member of the SEI CMM Assessment Team, during the Level 5 assessments.
Raghavan also worked with Hewlett Packard India , Indian Space Research Organization and DCM Data Systems for 5 years prior to joining at IBM, where he was involved with product development, product test software development, testing of the onboard Control Software for Indian Satellites.
Raghavan M is well versed in implementing Project Management processes and practices in large projects, Quality processes, models /standards. His strengths include Unix and operating system internals and Testing.


How to Work with Geographically-Diverse Teams
Bob Reed
Product Lifecycle Management System Manager
Synopsys, Inc.
Introduction:
For the past six years, Bob has worked out of his home managing projects, software releases, implementing process improvements—all while only traveling on average three days a month. He has worked with teams spanning the globe, and especially with team members and groups of teams who are in different locations. His techniques and perspective can be applied to anyone who needs to manage remote teams, travel less, or just spend a day-a-week telecommuting to save time and gasoline.
In this lively, interactive and humorous presentation, Bob presents the system that he uses to work with individuals and teams around the globe. He works with the audience to apply it to several real challenges from the audience.
Outline:
- Audience survey
- Your role in “remote” situations
- Your challenges
- The benefits of working remotely
- Business benefits
- Process benefits
- The challenges of working remotely
- Bonding
- Communication
- Hallway conversations – impossible or imbalanced
- Loss of body communication
- Collaboration
- Discussion
- Visual presentations
- The Machine
- The process system attributes
- Teams
- Roles
- Interfaces
- Operations
- Communication
- Planning
- Visibility
- Escalation
- Machine Builder & Operator Role
- How to build The Machine when it isn't your formal role
- When to travel
- Solving the audience's challenges
Learning Objectives:
- Thinking differently about “geographically diverse” teams
- How to build a system to help teams operate successfully over long distances
- What to do if you are not formally in charge of a needed system.
- How to run the system from any location and position
- How to minimize travel and maximize its benefits
Biography:
Bob Reed (BSEE 1988 Oregon State University; MSCE 1989 Stanford) is the expert at Synopsys in Product Lifecycle Management. Synopsys develops software tools in the Electronic Design Automation industry to help its customers, such as IBM, Intel and HP, design and verify complex integrated circuits.
Bob started his career at Intel as a microprocessor applications engineer. When he moved to Synopsys 12 years ago, it was just growing out of startup. Bob became much more fascinated with how to design and build great teams and organizations rather than designing and building hardware and software. Bob has spent the last eight years of his career working at all levels of Synopsys in implementing everything from Strategic Planning to how software programmers integrate their code. He has worked on organizing teams, developing processes, training…with team members from all functional groups, such as Marketing, applications engineering, support and R&D.
Although Synopsys has grown considerably, it still retains a very dynamic, fast-paced, and consensus-driven culture. Meanwhile, Bob has worked with very little formal authority, so he has developed many skills and techniques that create amazing results in the teams and business units he's helped. Even more amazing is that he has worked “out of his home” for the past six years so that his children could grow up near their grandparents. With about three days a month of travel, he's produced dramatic changes in organizations from across the US to India , China and Europe. 

Challenges in CMM/CMMI Implementation – An Experience Sharing
Raghavan M
General Manager and Head-Quality
Aztec Software and Technology Services Limited
Introduction:
To start with, most of the work that was being carried out offshore was Application Development (and Maintenance) where the full-gamut of the entire Application Project execution used to be owned by the Service Provider. The Execution Model more or less looked as depicted below.

Of late, we have seen a new trend wherein:
- Offshore Dedicated and Distributed Development centers are a reality
- Offshore Team is considered as an extended arm of the Customer
- Agile Development Practices are gaining prominence
- Agile is wrongly defined as “no processes”
- Agile implies co-located teams and hence, “no offshore”
The new execution Model depicted below:
 We, at Aztec Software and Technology Services Ltd., have lived through this changing scenario, over the years. As we align our Software Execution Processes through the Industry Standard SEI-CMMi Model, since, the model looks at the Project execution in a manner more similar to the model depicted in Figure 1. Since, in reality, the project execution model is more similar to the one depicted in Figure 2, the scope for interpretations of CMMi advocated practices are much higher than ever. The assessments also have to be sensitive to this and make adjustments accordingly.
This presentation discusses the challenges we face (due to the change in execution model) in detail and explains how we solved them. Outline:
- Introduction
- Traditional Model of Offshore Project execution
- Recent Trend and Execution Model in Offshore Project
- Challenges in
- Software Lifecycle, Estimation and Project Planning
- Software Requirements Phase
- Architecture and Design
- Implementation
- Reviews
- Verification and Validation
- Acceptance Testing
- Measurements and Metrics
- Closing Remarks
Learning Objectives:
- The new scenario and execution Model is here to stay; will become much more pronounced as “offshoring” and “outsourcing” becomes the norm in the Software Industry
- Scope for interpretations during assessments is much higher than before
- Future assessments and Audits must be sensitive to the changing scenarios
- This might even trigger bigger changes in interpretations and may be, even in the Model.
Biography:
Raghavan heads the Quality Function and is responsible for all Process related initiatives at Aztec. He has about 17 years of experience in software industry, of which about 5 years have been in Product Testing, 8 years have been in technical project management and 4 years in Process Quality . He has been associated with Aztec since August 2000, and has managed several projects involving Database, Java/J2EE and C/C++ technologies.
Prior to joining Aztec, Raghavan was associated with IBM Global Services India. There, he was instrumental in the development e-business practices. Over a period of 7+ years, Raghavan performed varied roles at IBM including Project Manager, Development Leads, Test Lead and also, had a 3.5 years long stint with various product groups at IBM Boca Raton, Austin and Raleigh. Most recently, as Program Manager, Raghavan was responsible for managing multiple projects in the e-business area and also, as head of e-business competency, including interactions with Global Customers, various IBM Product groups, Services units. Raghavan was also involved in the various Process quality initiatives and was an active member of the Software Engineering Process Group (SEPG). He also served as a member of the SEI CMM Assessment Team, during the Level 5 assessments.
Raghavan also worked with Hewlett Packard India , Indian Space Research Organization and DCM Data Systems for 5 years prior to joining at IBM, where he was involved with product development, product test software development, testing of the onboard Control Software for Indian Satellites.
Raghavan M is well versed in implementing Project Management processes and practices in large projects, Quality processes, models /standards. His strengths include Unix and operating system internals and Testing.
Raghavan holds a Bachelor's degree in Electronics & Communications and a Master's degree in Electrical Engineering from Indian Institute of Technology, New Delhi , India.

 Rules of Engagement: Getting Past the Rhetoric to Truly Effective Software Process Improvement
Kevin Weiss
CEO of The Capability Group & Philip Crosby Associates
Introduction:
You've heard the ancient saying, “every battle is won before it is fought”; is your software process improvement effort positioned for success or is your team fighting valiantly for a lost cause? Successful change agents work hardest to define the rules for change because they provide their teams an often overwhelming advantage. However, most process improvement leaders ignore this critical element, letting the organization continually redefine the nature, location, and pace of change.Before blaming organizational resistance on a lack of management support, change leaders must assess whether they have firmly established these basic protocols that dramatically improve the odds of success.
Learning Objectives:
In this session, you will learn:·
- Why a common language is critical for successful process improvement
- The protocols that must be in place before successful improvement begins
- Why supportive management can be worse than no sponsorship at all
- How to continually assess the organizational terrain and align your team for success
- How improvement teams too often sabotage their own success.
As with any change effort, organizational skirmishes will occur and unforeseen issues will arise, but the proper rules of engagement limit their effects and allow your team to ultimately succeed. By understanding these critical rules, you can focus your energy on winning the few, important battles that lead to successful process improvement.
Biography:
Kevin Weiss is the CEO of The Capability Group and Philip Crosby Associates, firms that help organizations achieve increased profitability and customer loyalty through organizational change and process improvement. He has been at the forefront of improving performance in transaction and service environments, and has consulted for a variety of companies including General Electric, Shimano, Seagate Technologies, American Express , Sony, Oracle and the American Society for Quality.
Prior to founding The Capability Group, Kevin served as a Quality Leader and Master Black Belt at General Electric Power Systems, a US$6 billion manufacturer, installer and servicer of Power Plants and Power Generation Equipment. There he designed and executed a Six Sigma Quality Strategy for a US$140 million global business unit with 300 employees, served on the company's Quality and Information Management Councils, and coached cross-functional teams executing large-scale process improvement projects in the areas of Finance, Human Resources, Engineering, Information Technology, and Risk Management.
Kevin led the first large-scale project to redesign a commercial process using Six Sigma principles at GE Power Systems. He developed the methodology to integrate process and information technology improvements within a single project, and directed a team of 30 full-time people and several hundred part-time members to execute the plan. The project redesigned 77 business processes that spanned 5 geographic sites and 4 functional areas, created direct annual savings of US$25 million, and provided a platform for significant top-line growth.
Kevin completed GE's Financial Management Program and held a number of finance positions at General Electric in both manufacturing and service environments. He also served in the United States Navy's nuclear propulsion program, where he lead an engineering division of a nuclear submarine.
Kevin is a Cum Laude graduate of the University of California , Berkeley with degrees in Economics and Statistics. He is a member of the corporate board of G. Loomis, Inc., a subsidiary of Shimano America Corporation.


Advanced Process Quantification

Tom Gilb
Independent Consultant
Introduction:
Advanced Process Quantification : 10 Practical Principles for determining your critical-few objectives for process improvement. How to measure, estimate, and evaluate the effects of a process improvement effort for critical stakeholders"
Outline:
- Introduction:
- You should not seriously tackle your process improvement unless you have stated and agreed your long term improvement objectives quantitatively. Process improvement is the ‘means'. To manage it meaningfully, to sell it to top management, you must develop and present a clear ‘bottom line' verifiable trackable notion of the ‘ends'
- You not only need to realistically set your ambition levels, but you need to be able to estimate the projected impact on those objectives of your investments in process improvement. You also need to measure quickly and continuously your progress towards those goals
- Most process improvement programs are not good at any of this. They are therefore doomed from the start to fail and be discredited
- This talk will show you how to quantify, measure and estimate – and will illustrate with real case studies and examples
Learning Objectives:
- Learn how to quantify any process improvement objective
- Learn how to deal with the critical set of your process improvement objectives: many simultaneous objectives
- See varied examples of process improvement quantification
- Get the basic idea: a process improvement is only as good as the measurable lasting effect it has on your official objectives in practice.
Biography :
Tom Gilb is a freelance consultant, teacher and author serving clients in Europe and the US. His newest textbook, Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage", was published in the US August 2005. He has also written “Principles of Software Engineering Management” (in 20 th printing) and is Principal author of “Software Inspection” (in 13 th Printing). He specializes in software quality design and management. He lives in Norway, when he is not travelling.
He has taught and consulted with Medtronic, Cray Research, United Defense and other companies in Minneapolis. With Ericsson and Nokia in Dallas. Motorola in Austin. His methods are also in use at Hewlett Packard, Intel, GE, IBM, Citigroup, Symbian, Philips Medical Systems, Microsoft, Ericsson, Nokia, DoD and many other companies.

Executive Eye: What does CMMI Level 5 mean for the CIO

Venguswamy Ramaswamy
Director of Sales and Delivery for the Global Consulting Practice at Tata Consultancy Services
Introduction: Capability Maturity Model® Integration (CMMI®) is a process improvement approach that provides organizations with the essential elements of effective processes. It can be used to guide process improvement across a project, a division, or an entire organization. CMMI helps integrate traditionally separate organizational functions, set process improvement goals and priorities, provide guidance for quality processes, and provide a point of reference for appraising current processes. This keynote presentation will present a direct view from the prism of Executive lens.
Learning Objectives/Outline: The session will focus on the following facets of Enterprise Quality transformation:
- How is the foundation of a Quality culture laid for the organization What are the building block components How is the quality program architected How to lead and manage ‘Change'
- The business benefits of a Quality driven organization
As with any change effort, organizational skirmishes will occur and unforeseen issues will arise, but the proper rules of engagement limit their effects and allow your team to ultimately succeed. By understanding these critical rules, you can focus your energy on winning the few, important battles that lead to successful process improvement.
Biography:
Venguswamy Ramaswamy is the Director of Sales and Delivery for the Global Consulting Practice at TCS. Prior to this role, he was heading the Process Consulting Group at TCS.
As Director of Sales and Delivery Support - Global Consulting, Venguswamy Ramaswamy, has the responsibility to take TCS' consulting offerings including Software Quality Solutions, Six Sigma Solutions and Creativity & Innovation Solutions to the large customer base of TCS. The practice is responsible for defining and developing various process solutions that can be accepted and implemented across different organizations globally.
Swamy spent a significant period of time leading the Six Sigma Program as a Quality Leader for the TCS-GE Relationship, SEEPZ, Mumbai, India. Swamy has been the TCS-GE relationship manager and has been responsible for managing TCS relationship with General Electric.
A certified quality analyst, his focus shifted towards leading the Six Sigma Quality Initiative for the relationship. In this role, he has led a team of Master Black Belts and Six Sigma deployment leaders within the relationship. His other responsibilities were, leading the Center of Excellence initiative and the Digitization efforts of TCS. Swamy holds a Masters in Computer Applications from University of Madras, India .


Process Improvement – An Effective Converged Release Management in Diverged Applications and Environments
Renuka Devadson
Senior Software Release Engineer
Fidelity Investments
Introduction:
This presentation shares a practical experience of a release engineer. This presentation demonstrates the efficiency and advantages of having a single point release team for an organization. The often neglected code migration from one environment to another can result in unclean, non sync and non-production like environments. This results in loss of testing efficiency and post production defects thereby affecting the project quality. The effect of which when noted is then difficult to restore. The key focus of this presentation is converged release, establishing repeatability, security and metrics for release. Many innovative approaches and shared experience from various leading organization is incorporated to make the single point release management effective. This proven approach is easy to adopt and customize. This effective approach has a range of benefits that impact from a small team to an entire organization.
Outline:
- Insight to Release Management
- Manage Migration
- Release of code or Code migration into various environment like multiple test , production, disaster recovery, etc…
- Support developers, testers and operations by communicating and promoting code in a multi environment scenario.
- Manage Environments
- Responsible for environment sync.
- Works closely with the ‘change management process'
- Importance
- Guarantees best environment for testing efficiency
- Process Improvement Motivation
- Avoid collision or conflicts among and between applications in various environments.
- Establish repeatability in code migration to multi environments.
- Automate the communication process.
- Ensure security.
- Assess risk in case of back out (uninstall) scenarios.
- Boost team spirit of Release engineers.
- Measurement of effectiveness
- Disadvantages of a diverged Release Management
- Absence of the BIGGER picture
- Communication gap
- Application dependencies not governed
- No consolidated test environment
- Discovery of problems in production
- Security Risk
- Environment sync and stability is at risk
- Disintegrated code promotion
Learning Objectives:
- Identifying various methodology used for version control Best Practices in Controlling and Releasing Change Change Management Process Best Practices in Naming Parallel Releases
- Identifying Risks in the Application Lifecycle
Biography:
Renuka Devadason is a Senior Release Engineer in EPS (Enterprise Processing Service) of Fidelity Investments. She has over 7 years of diverse software experience that ranges from Development to Project Management including Quality Assurance. Currently her chief work and focus is on Process Improvement and Repeatability of project “Release” into multi environments like production, test, development and disaster recovery. She has implemented solid workflows that ensure repeatability, sanity, integrity and stability of code migration into different environments at various stages of the software life cycle. Her work at Fidelity focuses on building process and methodology for efficient and effective center point quality release management that is applicable across various environments and applications of an organization.
Previous to working at Fidelity Investments, Renuka worked at a global IT Consultancy and Services provider which is ISO 9001:2000 certified and assessed at SEI-CMMI Level 5 and P-CMM Level 3. Here, she held different roles in assorted flavors of software project life cycles like development, maintenance and enhancements. She has also played effective roles of software quality assuror and internal auditor for multiple projects. Some of her notable achievements are, implementation of process improvement for a major US client using SIX SIGMA's DMAIC methodology and automation of code migration process towards SOX (Sarbanes Oxley) compliance.

CMM/CMMI Process Improvement and Results - A Global Corporation Perspective
Ron Weidemann
Division Quality Director
NCR Corporation
Introduction:
The concept is to share our successes and failures of moving from CMM to CMMI. Showing actual results from using CMM and CMMI, both process and product improvements. Will also be sharing how CMM or CMMI can be used with both the Waterfall and Agile development models. I will also share how and what measure we use for all process areas. I have been to conferences to see real measures and actual results only to be disappointed. Attendees to this presentation will go away with real measures and actual results.
Outline:
- Company History with SW/CMM-CMMI
- Why Move to CMMI?
- When to Move to CMMI
- Methodology Used to Migrate
- Problems That Arose
- Choosing the Right Representation of the model
- Current Direction
- Current Accomplishments & Implementation Schedule
- This can work with Agile Development Model
- Process Measure Examples
Learning Objectives:
- I will share actual experiences of being a CMM Level 4 organization moving to CMMI and the successes and problems that arose
- I will discuss whether to use the Staged or Continuous Representation (will give them guidance on how to choose the right one for their organization)
- I will share what we would change if we were to do it over again
- I will show how both the Waterfall and Agile Development models will work with CMM/CMMI
- Will share guidance on whether to include IPPD in your CMMI implementation
- I will show all of the actual metrics we use to monitor our process and products, these have evolved over the past 3 years and will share what we learned
Biography:
Ron has been working with CMM since 1997 and have been an SEI Authorized Lead assessor since 1998. I have conducted over 25 CMM Assessments and 5 CMMI appraisals. I have led several organizations to CMM Level 4 and 5. I am the SEPG/EPG Chairman and have been for company for the past 6 years. I lead all internal process improvements. We have had recent success using CMMI with the Agile Development model.

The Cost of Quality and the Individual Contributor
Maude Harris
Quality Assurance Analyst
Intuit Inc.
Introduction:
The Cost of Quality is an important measure of success for any company where the human factor is involved in the production of a product. Individual contributors, when aware of the cost of quality, understand the concept as it applies to the broader corporate level or the individual product level. This presentation delivers a foundation that provides understanding for the cost of quality at the individual contributor level. This understanding can improve production, reduce rework and contribute to the work life balance of the individual which can lead to employee engagement. The session provides a qualitative exercise that can assist individual contributors in assessing their personal cost of quality.
Outline:
- The Literal Cost of Quality
- Costs associated with the Cost of quality
- Necessary Costs
- Prevention Costs
- Inspection Costs
- Avoidable Costs
- Inspection Costs
- Failure Costs
- Internal Failure Costs
- External Failure Costs
- The Quality Grid
- What you do
- Right Things
- Right Things Wrong
- Right Things Right
- Wrong Things
- Wrong Things Wrong
- Wrong Things Right
- How you do it
- Things Done Right
- Things Done Wrong
- Estimating Your Cost of Quality
- Example of take away exercise for individual contributors
- Quality Grid
- How you do it
- What you do
- Employee Engagement, why understanding the Cost of Quality creates Engagement
- What values does a company assume to assure Employee Engagement.
- How does an employee know she is engaged
- The significant link between employee engagement, customer loyalty, and profitability
- Responsibility of the individual contributor to assure personal quality
- Why We Must Focus on the Cost of Quality
- Statistical Information
- Ideas and focus to take back to individual contributors
- Take Away Questions/Advice for Individual Contributors
Learning Objectives:
- The importance of the frontline employees grasp on the reality of the Cost of Quality and how it applies directly to their job functions.
- Notice traits of engagement in front line employees.
- Help create engaged employees.
- A take away exercise that shows employees at any level their personal Cost of Quality, which leads to personal changes facilitating improvement.
- The ability to see traits of engagement in front line employees.
- Reminders of how important your employees are exercises and methods you can use to remind them and yourself of this fact
Biography:
Maude Harris is a Quality Assurance Analyst for Intuit Inc. Is currently a member of Intuits corporate Test Management Working Group. She has initiated and collaborated on many of the Process Improvement initiatives currently implemented. Involvement in the implementation of the processes below has created an understanding of the importance of process socialization. Processes involved in include but are not limited to, creation, roll out and training of new software production life cycle, Requirement Traceability Schema, Enterprise E2E test process improvement effort, Software Testing Terminology, Document Template definition and roll out. From her observations the Author recognizes the importance of understanding process changes by the front line employees. This understanding can lead to realization of self-worth, personal goal completion, understanding management's goals, and company goals which can create employee engagement. Maude Harris has presented at Intuit Inc Technical Forum, Create the Offering 2005. She has received a Best Business Practices/Organizational Excellence certification from SDSU 2005.

Comparative Study of Internal and External Assessments
Sreehsa Sanne & Vinayak Guttal
Consultant & Sr. Quality Analyst
Satyam Computer Services Ltd.
Introduction:
Quality Assessments are done to check the health of an organization and to identify improvement opportunities in their quality journey. These assessments can be done either externally or internally based on the objectives and business needs of the organization. Information available on internal assessment as compared to external assessment is limited. In this paper we provide a set of guidelines and prerequisites for selecting an appropriate assessment and also highlight pros and cons associated with them. An attempt is made to compare internal with external assessment with respect to time, cost and schedule. Outcome of an internal assessment can always be questioned due to the fact that they are conducted informally. Results of internal assessments can be biased and manipulated as compared to external assessments. The results of internal assessments may not provide a complete and true picture as compared to external assessment. External assessments can be expensive. Internal assessments can be very good tool if used with clear objectives of process improvement and management support. Organizations need to invest in internal/external assessments wisely so that their objectives are achieved. This paper will provide you an unbiased comparison, so that decision process can be improved. From the study and experience, authors felt that a combination of external and internal assessment can yield better results. These observations are purely based on authors' experience and exposure in this subject area.
Outline:
- Basics of Assessments
- Need of Assessments
- Management commitment
- Criteria for selection
- Unbiased comparative study of Self(Internal) assessment and External assessment
- Advantages and Disadvantages
- Conclusion
Learning Objectives:
The audience will be able to understand and appreciate:
- Internal and external assessment
- Benefits and drawbacks
- Selection of assessments
- Decision making process
Biography:
Sreesha Sanne is a Consultant of the Software Process Consulting Team at Satyam Computer Services, USA, (an SEI CMM & CMMI level 5 Company) with over 15 years of experience in Manufacturing / S/w development and Software Quality Management. In his ISO 9000/ CMM / CMMI and other Quality consulting assignments for US, UK and European clients, Sanne has played a key role completing end to end projects in ISO 9000 and CMM / CMMI. Process Definition and Process Integration / automation and Metrics Implementation are prime areas of interest. Sanne was responsible to successfully and repeatedly get organizations certified under ISO series. Sanne has a Masters in Technology and engineering and worked as Lead auditor. As a Certified Project Management Professional (PMP), completed 5 projects on time and cost. Also developed expertise in Function points, RUP / Rational suite of products, Six Sigma and TQM. Sanne has published papers in International and National Conferences.
Software:
- A statistical approach for comparing Tick IT and CMM – Part –1, Published in British computer society-Jan-2004.
- W-Model, Guidelines for Embedded Process – Presented in international SEPG conference – QAI- 2002 .
- Non-software : Six papers were published in different national and international papers.
Vinayak Guttal is a Sr. Quality Analyst of the Software Process Consulting Team(QPRIME) at Satyam Computer Services, USA, (an SEI CMM & CMMI level 5 Company) with 8 years of experience in Software design, development, testing and Software Quality Management. In his ISO 9000/ CMM / CMMI and other Quality consulting assignments for US and Indian clients, he played a key role in implementing these models in the various organizations. He guided organization for their non model based process improvement journey. He also has extensively worked in area of testing, measurement, software configuration management.
He holds a bachelor degree in Engineering. He is Certified Software Quality Analyst (CSQA), Brianbench certified Software quality Assurance and certified Internal Quality Auditor. He also has expertise in various software development models like SSAD, OOAD and trained in RUP. Vinayak has contributed in
- “A statistical approach for comparing Tick IT and CMM” published in British computer society in Jan-2004

A Communications-Driven Approach to Implementing the CMMI
Shawn Presson
Director of Organizational Practice
Apogen Services, LLC
Introduction:
We use the phrase “form follows function” to drive design for manufacturing, architecture, and most other projects. This gets lost, however, when many organizations try to interpret the CMMI. The “form” of the improvement efforts tend to be that of documentation projects, and the “function” of increased visibility and communication often are forgotten. This presentation will cover fundamental concepts of communication loops, and will discuss how components of the CMMI directly relate to components of communication. Specific examples will be given of how organizations have successfully avoided the documentation trap to make the CMMI support business goals.
Outline:
- Components of Communication Loops
- sender/recipient: “ping”-acknowledge
- encoding-decoding: message
- processing
- encoding-decoding: response
- feedback processing
- medium and noise
- Evolutions of Communication media through history
- Impacts of language
- Impacts of technology
- Impact of modern communication behaviors by ancient habits
- Still-useful practices
- Outdated practices
- Relationships of CMMI components to communication components
- Generic Practices
- Specific Practices
- Helpful/hampering real-world examples for each practice drawn from industry experiences
- Accurate and misleading uses of the word “communication” in the CMMI
- Interpreting CMMI components when developing organizational process assets
- Architectural considerations
- Timeline considerations
Learning Objectives:
- Attendees will be exposed to fundamental elements of communication, and will be challenged to re-think activities that often get labeled as “communication”
- Attendees will become aware of common practices that obscure rather than support communication of practices
- Attendees will become aware of innovative ways of thinking about fulfilling principles within the CMMI
- Attendees will be challenged to rethink architectural and content assumptions about process assets
- Attendees will be challenged to reassess schedule and business drivers for process improvement
- Attendees from the acquisition community will obtain a broader understanding of the behavioral and cultural indicators of process maturity than the typical document-driven view
Biography:
Shawn Presson's background encompasses project management, process improvement consulting, and internal process improvement. Over a decade of software engineering combined with seven years evaluating and consulting systems development companies has provided him a firm understanding of the issues involved with custom software development. He has performed training and hands-on process improvement within organizations from various domains, including DoD/government, aerospace, pharmaceuticals, microprocessors, banking, commercial software consulting, networking, transportation systems, and document imaging. Having served as PPQA Lead and SEPG Chair, Mr. Presson fully understands the real-world challenges in mapping process improvement efforts to organizational needs. His experience evaluating organizations using the Software Engineering Institute's (SEI) Software Capability Evaluation (SCE) methodology has given him clear insight into how companies attempt the implementation of models such as CMMI and SW-CMM, and in-depth insight into common causes of success and failure. As an authorized instructor of the SEI's Introduction to CMM Integrated (CMMI) course, he has a strong appreciation for the challenges in communicating model-based process improvement concepts. Mr. Presson is a candidate Lead Appraiser under the SEI's SCAMPI methodology. His primary goals in training, appraisal, and consulting is to help organizations tie process improvement goals directly to financial, mission, and other business goals. His approach emphasizes flexibility in process definitions that enable organizations to add assets based on CMMI, SW-CMM, ISO, IEEE, PMBOK, ITIL, and other industry guidance with minimal rework and disruption.

Leverage Earned Value Management with Function Point Analysis
Ian Brown, CFPS
Senior Associate
Booz Allen Hamilton
Introduction:
In the Earned Value Management (EVM) approach, as work is performed, it is ''earned'' on the same basis it was planned - both the original plan and agreed to changes. Today more and more software projects are using this approach. Function Point Analysis has been shown to be a reliable method for measuring the size of computer software based on detailed requirements and specifications. Function points can be leveraged throughout the EVM process to establish cost and schedule baselines, control project scope over the life cycle, and quantitatively assess percent complete. This presentation provides an oversight of EVM concepts of as applied to software development and the key conditions necessary to profitably employ this management technology. The presentation also demonstrates how companies can use function point analysis to improve the information provided by the approach.
Outline:
- Purpose
- Earned Value Management (EVM) Overview
- Function Point Analysis (FPA) Overview
- Applying FPA to EVM complimentary suit
Learning Objectives:
- Gain an understanding of Earned Value Management and how it differs from traditional project management
- Identify three key requirements for successful EVM
- Gain a high level understanding of function point analysis concepts and the benefits of FPA
- Learn how function points can be applied to support the EVM approach and how FPA can help meet the three key requirements
Biography:
Ian Brown, a senior associate with Booz Allen Hamilton, leads the firm's Quantitative Software Analysis capability. He has 8 years of experience in software measurement and analysis, CMM/CMMI, and goal-question-metric (GQM) implementation. Ian was elected to the Board of Directors of the International Function Point Users Group (IFPUG) in 2004 and serves as the Secretary and Director of Communications and Marketing. He has presented at several software conferences, including the Better Software Conference & Expo, the IFPUG Annual Conference, and the Practical Software Quality and Test Conference. Ian is a Certified Function Point Specialist (CFPS) and has earned a bachelors degree from Cornell University and a master degree in public policy from Harvard University. He has worked closely with the firm's Earned Value Management (EVM) capability to integrate software measurement concepts with EVM and is currently implementing the approach on a large maintenance and enhancement task at the Federal Deposit Insurance Corporation.


Support the CMMI Initiatives with Well Designed Measurement Constructs
Agnes E. Nanu
Associate
Booz Allen Hamilton
Introduction:
If you ever found yourself being overwhelmed by the idea of measurement, this is the session for you. Very often we face the question: what evidence do we have that measures are collected and analyzed in a consistent, and repeatable way? Too often, when people are measuring, they don't use the same processes and procedures. In other words, every time when we don't specify how the measures are collected, and analyzed, we leave room for assumptions and interpretations, and such, for errors in our analysis. The fundamental basis for process improvement is to have accurate, and reliable measures. The measurement construct is a simple but very powerful concept that addresses this problem.
Outline/Learning Objectives:
The use of well designed measurement constructs allows us to have more accurate, reliable measures, which are essential for dependable, and repeatable processes, and as such, fundamental for process improvement.
- Learn how to implement the PSM key concepts and procedures
- Learn how to determine what we need to measure versus what we can measure
- Establish key components of a measurement construct according to each type of measure identified (base measure, derived measure, and indicator)
- Identify issues and challenges related to the measurement constructs
- Learn how to make the measurement constructs part of the measurement and analysis process
Biography:
Mrs. Nanu is an Associate with the Economic and Business Analysis Team of Booz Allen Hamilton. She has a Master in Business Administration from the University of New Orleans, Louisiana, and a Master in Science in Electronics and Telecommunications, from the Polytechnic Institute, Bucharest , Romania .
Ms. Nanu has over 20 years of professional experience in strategic planning, market analysis, contract negotiation, software cost estimation, measurement, performance management, and process improvement. Her other areas of expertise include CMMI, Practical Software Measurement (PSM), and Function Point Analysis (FPA).

“PROSO - Project Schedule Optimization” Model using Empirical Methods: Breakthrough in Stakeholders' Expectation Management
Anoop Kumar
Program Manager (SEPG)
Infosys Technologies Limited
Introduction:
Time overrun and inability to fulfill stakeholders' expectations are the two most chronic problems in software development. Recent benchmarking studies by Capers Jones indicate that only 66% MIS projects are completed on time. One of the root causes for this phenomenon is improper schedule estimation. Typically, schedule estimation is done using Empirical Models available in public domain such as COCOMO, COCOMO II etc, which describe the relationships between effort and elapsed time. However, these models do require refinement to address organization specific scenarios and capabilities. Apart from that, the impact of team size on elapsed time often remains unaddressed. Besides, these models do not provide “what-if” capability to the decision makers when confronted with stakeholders demand to shorten the project time lines.
This paper explores various existing models and establishes the empirical relationship among effort, team size and elapsed time to ensure Project Schedule Optimization (PROSO) using actual performance of the recently completed projects. Over 500, high-maturity (CMMI Level 5) development projects performance has been analyzed to create this model. Stakeholders do look out for crunching optimal elapsed time. PROSO further allows decision makers to analyze the impact of schedule crunch on various product and process quality metrics e.g. Overall Defect Removal Effectiveness, Defect Density, Effort Overrun, Field Defect Density etc. This powerful capability allows the project team to set realistic expectations and take a balanced view of project's expected performance.
Comparison has been made with the industry-best schedule estimation models and it has been found that PROSO is much more precise and accurate than so far published models for the organization specific requirements. This has been extensively deployed to facilitate improved estimation and validation of the time schedule, thereby creating immense business value.
This study reinforces the fact that estimation models using organizations' own data provides much better insights into schedule estimation issues. Team size apart from effort is found to be the two most important factors impacting elapsed time, which are factored in PROSO. In addition to that, PROSO simulates the project performance for different extent of schedule crunch. It has proved to be a strong tool in the hand of project managers and other decision makers to effectively negotiate with the stakeholders and set realistic expectations.
Use of PROSO has resulted into improved on-time delivery of projects (up from 88% to 92%). This has enabled decision makers to predict the adverse impact of schedule crunch. For instance, crunching optimal schedule by over 20% leads to approximately 4 times higher Field Defect Density than the normal levels.
Outline:
- Importance of schedule estimation
- Trade-offs in project scheduling
- Organizational environment
- Comparison of available schedule estimation models
- Structured approach for empirical model building by examining the key factors impacting elapsed time
- Model building through multiple regression analysis, validation and comparison of results using a large number (over 500) of high process maturity projects (CMMI Level 5)
- Impact of schedule crunch on key result metrics
- Implementation experience and road ahead
- Business Results
Learning Objectives:
- Comparative analysis of known schedule estimation models
- Key factors impacting project schedule estimation
- Relationship among team size, effort and elapsed time
- Impact of schedule crunch on Overall Defect Removal Effectiveness, Defect Density, Effort Overrun, Field Defect Density in quantitative terms
Biography:
Anoop Kumar is working as Program Manager – Software Engineering Process Group (SEPG) from May 2000 at Infosys Technologies Limited, a CMM/CMMI Level 5 company, headquartered at Bangalore , India . He is primarily responsible for bringing out continuous improvement in Software Project Management and Estimation processes by systematically analyzing quality and process performance results. His other key responsibilities include improving organization-wide metrics & measurement program, implementing large change management initiatives across the organization, benchmarking, and imparting training on application of the statistical techniques for quantitative project management.
He has introduced several new practices in the area of measurement to improve software process capabilities. These practices were presented in the SEPG Asia Pacific Conference, held in 2002 at Bangalore , India and were adjudged as the Best Practices. Besides, he has come up with many decision-making models by analyzing the correlation among different software metrics for estimation, project monitoring and control. These have resulted into significant reduction in effort overrun, defect injection rate and improvement in schedule adherence.
While reviewing projects estimated elapsed time, it was observed by the authors that typically, schedule estimation is done using empirical models available in public domain such as COCOMO, COCOMO II etc. Careful analysis of the performance of the completed projects clearly indicates that organization-specific models could serve this purpose better. Besides, these models do not clearly address the impact of team size on elapsed time. Apart from that, they have not established quantitative relationship between the extent of schedule crunch and projects' expected performance. Whereas, decision makers when confronted with stakeholders demand to shorten the project time lines due to business considerations. These have been the key motivation for coming up with Project Schedule Optimization (PROSO) model.
Anoop has in-depth experience in using various Quality Management models /techniques like ISO 9000, MBNQA, CMM / CMMI and Six Sigma. He has consulted several Fortune 500 companies in the areas of estimation, quantitative project management, setting up of measurement program etc.
Prior to joining Infosys, he has worked in Tata Steel, the most cost-effective producer of steel in the world, from February 1992 till April 2000 in the areas of statistical process control, process benchmarking, implementation & audit of ISO 9000 quality systems, operations research and facilitation of company wide quality improvement programs. He is a graduate in Metallurgical Engineering with Post-Graduate Diploma in Industrial Engineering.


Steering Agility: Detecting, Understanding and Correcting Agile Process "Smells"
Wayne Allen
Consultant
Introduction:
Agile methodologies are just as prone to mistakes, deviations and subversion as any other methodology. Learn about ways to identify these process "smells" so that corrective action can be taken. Just because you are using one of the agile software development methodologies (XP, Scrum, FDD, DSDM, etc) doesn't mean you won't run into trouble because of lack of knowledge, good intentions, old habits or plain old subversion.
Join us for an interactive discussion about some common ways that agile projects get off track, factors that lead to the situation, evaluating the situation in relation to agile principles and practices and whether corrective action should be taken.
Outline:
- Introduction
- Solution Stories
- Specialists
- Estimation Problems
- Lack of Testing
- Customer can't/won't Steer
- Audience Supplied "Smells"
Learning Objectives:
- Recognize common agile problems
- How to evaluate problems in relation to agile principles
- How to work with teams to change behavior
Biography:
Wayne Allen has been consulting/coaching organizations on adopting agile methods since 2000. Starting in 2002 he began specializing on the areas outside the core of agile development, namely product management, quality assurance, interface/interaction design, documentation and project management.

Mission Assurance in the Operational Environment – A Case Study
Ronda R. Henning
Senior Scientist
Harris Corporation
Introduction:
The modernization of a critical infrastructure is a daunting task. When the system is a national critical infrastructure, it comes under additional scrutiny. Especially when the system migrates from a dedicated network to a service based architecture. In these circumstances, continuous deliveries of assured services are required for a successful implementation. This presentation examines the legacy network and contrasts the existing network assurance capabilities with the evolving services-based assurance architecture. The requirements as specified during the acquisition are examined, and lessons learned during requirement validation are presented. From this assurance foundation, the operational assurance and system certification approach are presented. The integration of verification, configuration management, operational procedures, and contingency management are discussed, and the rationale for assurance trade-offs presented. Finally, the evidence that the operational assurance techniques are functioning as required is presented in the case study of four hurricanes and their impacts on mission operation.
Outline:
- Introduction -- the existing network
- how it was created
- how it was tested
- “don't fix it, it's not broken”
- Evolving to Services
- Why move to services
- How services are characterized
- The implications for assurance
- Assurance mechanisms applied
- Security Perimeter
- Change Management
- Configuration Management
- Contingency Management
- Policies, Procedures, Software Development
- Verification
- Making it all function together – the final steps
- The independent audit process
- Training the team
- Test under Fire
- Hurricanes Frances, Jeanne, Charlie, Ivan
Learning Objectives:
At the end of this presentation the audience will:
- Understand that, even if the legacy system is being discarded, it must be understood
- Have a good understanding of which development disciplines impact mission assurance
- Understand the tools and techniques used to implement mission assurance in an interdisciplinary environment
- Be capable of validating mission assurance claims
- Be an informed consumer of assurance services.
Biography:
Ronda R. Henning is a Senior Scientist at Harris Corporation, Government Communications Systems Division; a Melbourne, Florida based international communications company. Ms. Henning is the Network Security Manager for the FAA Telecommunication Infrastructure (FTI) Program, a $1.7- Billion dollar network infrastructure modernization of the National Air Space communications networks. In this assignment, she has been responsible for the security architecture, security operations management, and security certification of the replacement system. The network evolves the FAA from a point-to-point ad hoc network to a communications services oriented architecture. Prior to this assignment, she led the Harris Information Assurance center of excellence in the definition of security architectures for the National Crime Information Center modernization (NCIC 2000) and the Eastern Test Range Modernization Program for the U.S. Air Force.. Ms. Henning also served as principal investigator on the Network Vulnerability Visualization Architecture (NVVA) program, and the Integrated Design Environment for Assurance (IDEA) program. Prior to her employment at Harris, Ms. Henning worked in information security research and development at the National Security Agency, specializing in multilevel database management architectures and applications. She is a Certified Information Systems Security Professional (CISSP), Information System Security Engineering Professional (ISSEP), Information System Security Management Professional (ISSMP), and a Certified Information Security Manager (CISM). Ms. Henning holds an M.B.A. from the Florida Institute of Technology, an M.S. in Computer Science from Johns Hopkins University, and a B.A. from the University of Pittsburgh.

Roadmap for Effective Implementation Of CMMI
Diane M. Burwick
CEO/Principal Consultant
Business Process Solutions
Introduction:
In the year 1513, Machiavelli said, “Let it be noted that there is no more delicate matter to take in hand, nor more dangerous to conduct, nor more doubtful in its success, than to set up as a leader in the introduction of changes.” In most cases, this still holds true today. If your organization is having difficulty implementing Level 2 and/or Level 3 of the Capability Maturity Model Integration (CMMI), it is probably due, at least in part, to the method or techniques being used to affect the change. To those who have become frustrated along the way or are just beginning the journey, this session will provide a roadmap to help you. Rather than theory, this seminar will provide practical guidance and instruction on the high-level steps for the complete lifecycle of process improvement, from "how to get started" to "a successful appraisal." The session will focus on the two following learning objectives: 1) learn how to overcome resistance to change and other typical obstacles to process improvement, and 2) understand the elements of the major steps for effective implementation.
Outline/Learning Objectives:
- Brief Introduction to CMMI
- Overview of the model
- Maturity Levels for Rating based on Staged Representation
- Process Areas (PAs) within each Level (or using Continuous Representation)
- Roadmap for Implementation
- How to Get Started
- Document an Initial Strategic Plan
- Perform Gap Analysis
- Update Strategic Plan and Create Charter
- Develop a Tactical Plan
- Everybody Plays, Everybody Wins
- Identify resources
- Create roster
- Provide orientation to resources
- Organizational Implementation
- 10 Basic Steps
- Kickoff Meeting and Overview Training
- Building the Infrastructure
- Formation and Startup of EPG
- Baseline PA Handbooks (or Process Manuals) and Standard Operating Procedure
- Formation and Start-up of a Quality Management Board (QMB) or Management Steering Committee (MSC)
- Baseline Project Management Plans
- Implementation on Projects
- Putting It All Together - Approach Based on IDEAL lifecycle
- A Successful Appraisal
Biography:
Diane M. Burwick - CEO/Principal Consultant of Business Process Solutions, an education and consulting services organization that provides assistance with process improvement using the CMM or CMMI model. Ms. Burwick is also President of parent-corporation Business & Personal Solutions, Inc. and author of the popular book “How To Implement the CMM,” first and second editions. Prior to 1996, Ms. Burwick provided consulting to some of the largest defense contractors in the D.C. area, and worked for two years at CPI/MicroAge as a Technical Account Manager where she provided consultation and professional services to local government, large school districts, and universities. During 1996-1998, in her position within the defense services sector of a large IT company, she was tasked with training and implementation to ensure CMM compliance. During 1998 and 1999, as CMM Lead of the Mentor-Protégé Program, Ms. Burwick led entire companies through the lifecycle of process improvement using application development processes in accordance with the CMM. She developed and/or customized best practices for individual projects and instructed project managers in their use.
Since then, Ms. Burwick has provided training and performed consulting for many commercial businesses and government agencies on all of the CMM or CMMI Level 2 and 3 Process Areas. She is widely regarded as a CMM Subject Matter Expert and is an entertaining and informative speaker. In 2002, Ms. Burwick developed a small set of streamlined procedures to ensure thorough and effective (yet practical) risk identification, assessment, and management. This program for Risk Management was rated as a best practice in two formal CMM-Based Assessments in 2002! Ms. Burwick has also developed other industry best practices in the areas of Time Tracking and Project Estimation.

A Case Study in Globally-Distributed Lean Software Development
Jerry Bernsten
Senior Technical Manager
Honeywell Aerospace Software CoE
Introduction:
The Honeywell Aerospace Engineering Software Center of Excellence (SWCOE) is responsible for the definition and deployment of software development processes and software productivity improvements across the Honeywell Aerospace engineering organization. The Honeywell SWCOE has identified the application of lean principles as a means to achieve the desired improvements. To identify and prioritize projects – for improving productivity, reducing cycle time, and eliminating waste – the SWCOE conducts lean assessments of software development projects using the Honeywell Velocity Product Development™ (VPD™) method. This presentation will discuss the VPD™ assessment method and resulting improvement projects, the application of iterative development methods to this globally-distributed development project, and the results.
Outline:
- Introduction
- SWCOE in Honeywell Aerospace
- Honeywell and Six Sigma and Lean: VPD™
- Honeywell VPD™
- Case for Change
- Assessment Methods
- CMMI
- VPD™
- Selected Approach
- Baseline process and tools
- Current State : Value Stream Mapping
- Undesirable Observations
- Lean C&E Matrix
- Reality Tree
- Leverage Points
- Future State
- Results: Improvement Projects
- The Iterative Development Project
- Background
- Planned Approach
- Iteration Value Stream
- Iteration Planning
- Actual Iteration Performance
- Iteration Evaluation
- Summary
Learning Objectives:
- Discuss a methodology for applying lean principles to product development.
- Demonstrate the lean product development methodology in an application to a software project.
- Demonstrate an application of Rational Unified Process and its quantitative results.
- Demonstrate simple metrics for measuring project success.
- Describe an approach for planning and evaluating iterations between globally-distributed sites.
Biography:
Jerry Berntsen holds Honeywell Six Sigma certifications for both Black Belt and Lean Expert. He has worked in the field of software development for 25 years. In the last five years he has been applying Six Sigma to software development. Jerry used the project described in this presentation to obtain his lean certification.
Jack Janelle holds a Honeywell Lean Expert Certification. He has worked for 27 years in the field of avionics software and systems, with 18 years at Honeywell. He has focused on software process improvement for the last 10 years, most recently applying lean principles to software development.
Dan Houston has worked in the field of software development for 18 years. He received his doctorate in industrial engineering at Arizona State University with research on simulation of software development processes. He is a Honeywell Six Sigma Black Belt and currently works as an internal consultant supporting the quantitative management of Honeywell software development teams.


One NASA: Sharing Knowledge through an Agency-wide Process Asset Library (PAL)
Baraka J. Truss (Author/Presenter)
Grey Settle (Author)
Project Lead
NASA, Marshall Space Flight Center
Introduction:
This presentation will cover the key purpose and components behind implementing the NASA PAL website. This presentation will present the current results, describing the process used to create the website, the current usage measure, and will demonstrate how NASA is truly becoming ONE. The target audience for the presentation includes those currently implementing the CMMI model and looking for PAL adoption techniques.
Outline:
- Agency PAL Background
- Website purpose
- Characteristics of the website
- User accounts status
- Website content size
- Usage percentages
- NASA's benefits from PAL
- General Recommendations
Learning Objectives:
- Website purpose
- Characteristics of the website
- User accounts status
- Website content size
- Usage percentages
Biography:
Mrs. Truss is currently a member of the Flight Software Branch in the Engineering Directorate at Marshall Space Flight Center. Her assigned task is Project Lead for the Software Process Improvement effort within the Flight Software Branch. Her responsibilities include preparing the Group for the Software Engineering Institute Capability Maturity Model and Capability Maturity Model Integration Level 3 assessment and training/orientating employees on software processes/model. In fulfilling her task Mrs. Truss fully understands the Software Engineering Institute Capability Maturity Models, the software process of the Flight Software Branch and the software process for the Agency. Mrs. Truss is the prime point of contact for populating/managing the NASA Software Process Asset Library (PAL). In conjunction with this assignment, Mrs. Truss also support the NASA and MSFC Software Working Groups in which she is a member and has served on sub-groups that research and feedback vital software information to the Working Group.
Mrs. Truss is also the chairperson of the Software Engineering Process Group for the Flight Software Branch in which she and other team members are responsible for implementing software process improvement within the Branch. Mrs. Truss has been the COTR for the COTS IV&V task, a Co-Principle Investigator for Complexity Model research and is also responsible for tracking the training of employees in the Branch. Mrs. Truss is also a part-time faculty member of the computer science department at Alabama A&M University where she instructs undergraduate students in the field of computer science. Her duties include managing course curriculum, evaluating student knowledge retention and motivating students with the vast knowledge that the computer world has to offer. This task allows students to be prepared for the changing world of computer technology through lecture and hands-on experience. In addition, Mrs. Truss also serves on the University Industry Advisory Board which is a feedback mechanism for the University to remain informed of new technologies in the current computer industry and assists with ABET accreditation.


Staying On The Road To Maturity
Bob Pierce & Barbara Dreon
Systems Engineer & Technology Change Management Lead
Northrop Grumman Corporation
Introduction:
Northrop Grumman has been successful at achieving high maturity ratings against the CMMI model and in implementing process improvement across the breadth and depth of the organization. DES is just one example of that success. This presentation takes a brief look into some of the techniques DES uses to maintain high maturity and to ensure all organizations benefit from the process improvement experience.
Outline:
- Brief background on the organizational context
- DES current maturity level and how we got here
- Current process improvement practices DES uses for high maturity
- Ongoing continuous improvement techniques
- Lessons learned and future challenges
Learning Objectives:
- Understand the effort and challenges necessary when seeking higher maturity levels
- Become familiar with several continuous improvement techniques
- Become acquainted with the lessons learned by an organization with mature processes
- Understand the challenges of maintaining high maturity
Biography:
Mr. Pierce is a member of Northrop Grumman's Defense Enterprise Solution (DES) business unit Engineering Process Group (EPG) and is the EPG Chairman for a CMMI Level 5 project within DES. Mr. Pierce has been an EPG Chairman and active in process improvement since 1997. He was a member of one project's EPG when they were appraised at CMM Level 3 and Chairman of the EPG for the same project when the project was appraised at CMMI Level 5. Mr. Pierce currently manages a project that identifies candidates for future CMMI appraisals and mentors projects in obtaining CMMI compliance. He currently owns the organizational process for Product Integration and Technical Solution and has previously owned the process areas for Risk Management and Quantitative Project Management at the project level. Mr. Pierce holds a Bachelor's degree from Fontbonne University in St. Louis, Missouri and a Master's degree from Duquesne University in Pittsburgh, Pennsylvania. He has been on the faculty of Fontbonne University and of Washington University in St. Louis.
Ms. Dreon is a Technology Change Management Lead in Northrop Grumman Corporation. She has over 10 years of experience in process improvement for software and systems engineering and works for a company that has achieved over 18 CMMI Level 5 ratings. She has an M.S. in Operations Research and enjoys helping projects and groups apply process discipline to creatively suit their goals. She is also an instructor and has provided past

Lean & Pragmatic Project Tracking that Works
Cees Michielsen, ITIB
Introduction:
The presentation demonstrates how project teams have struggled with making a practical and sustainable implementation of Project Tracking over a period of four years. It clearly identifies a number of bottlenecks and practical process and organizational problems. Examples are shown that help to understand the needs for information from the team leader's side as well as from the engineers side. Several tools were tried to support project tracking and most of them focused on the team leader's view of the project. Despite the functional capabilities of the tools and of the team leaders, the situation remained unsatisfactory: the team leader did not get the information he/she needed and the engineers had to supply similar data in various tools. Consequently, data became incomplete and inconsistent quickly after the introduction of yet another tracking method. The solution to the problem was found in combining working methods that were already implemented and were common practice both for the engineers and team leaders. The configuration system was intensively used throughout the organization and was task-based. For transparency, these tasked were mapped one-to-one on the work breakdown for a product release. The tooling, process and organization were adapted slightly, but significantly to address priorities and changes to the existing work. Tracking was easily automated once the usage and rationale was explained to team leaders and engineers. Although the added value was questioned heavily in the beginning, now everyone is very enthusiastic about the results. Automated database queries make it possible to give weekly, personal feedback that helps engineers to focus, prioritize and manage changes more easily.
Outline:
- Case context (industry, large project, multi-discipline)
- History in the organization on planning & tracking
- Needs project team leaders and engineers
- Existing working practices (incl tooling)
- Gap analysis (needs vs current practice)
- Solutions (most of them did not work)
- Why the solutions did not work
- Analysis of lessons learned
- Current working method (why is it successful)
- Metrics (insight into a year of tracking)
- Next steps (higher level metrics, risk management)
Learning Objectives:
- How an industrial organization implemented project tracking
- What needs to be considered when implementing a ‘foreign' model
- What the concept of stakeholders means in this context
- How to make tracking work in a lean & pragmatic way
- How this step enables the organization to manage changes better
Biography:
- 1986 - 1997; SW engineer; team leader; SW process coach; R&D process coach in a large multi-national Electronics company
- 1997 – 2001; ICT consultant; supporting Software development factories; setting-up Service Management organizations using ITIL; managing ISO projects; ad interim Quality Manager;
- 2001 – 2005; Product Creation Process coach at a printer-copier manufacturer; R&D of 1100 people; multi-disciplinary systems development; main focus on communication, management of change; Quality assurance; Anticipating development;
- 2005 - started ITIB.

Estimation for Small & Large Teams - a Ready to Use, Scalable Model
Manoj K Upreti & Shanmukha Polepeddi
Consultant/Process & Quality Consultant
MetLife Inc. & Cognizant Technology Solutions
Introduction:
Providing technological solutions to a dynamic and changing business environment poses unique challenges to software development. Reliable and accurate effort estimation is essential for business negotiations and project planning for software development project, in order to avoid losses, last minute development crises or business failure.
Though there are innumerable models available for estimating effort and cost, most of them do not address processes used for both new systems development as well as for maintaining or transforming existing systems.
This session is aimed at presenting a flexible, measurable, and auditable estimation model using the parameter-complexity method, developed to address this unique business context.
The model uses parameter size and complexity, which is independent of technologies and implementation decisions, as a basis for development and calibration of effort estimates. Definitions of Size, complexity and productivity are established and re-used by the project team and the organization. Collective knowledge of team members is used to calculate size and productivity values in their area of expertise.
The model is structured to clearly indicate which phases of the selected lifecycle and which activities are covered. Uncertainties of the changing project scope or business context can be identified and quantified to finally adjust the estimates.
We applied this model to develop a simple MS Excel based tool. The approach is to determine the size of software elements by breaking them down at the implementation level and obtaining estimates and agreement by the team. The tool allows scaling from a high level to detailed estimates, and to capture and use historical data.
Usage of this tool significantly improved the estimation process and addressed real life challenges with estimation, such as estimating with little information and re-estimating as information becomes available, and estimating for functions that span several release cycles.
Outline:
- Estimation challenges
- Real life situations
- Lessons learned from industry
- Applying parametric complexity model
- Why size and complexity?
- Model overview
- Building Flexibility
- Estimation for Product development and maintenance projects
- Independence of technologies
- Calibration of Estimation
- Implementation approach
- Considerations
- Process definition and tool development
- Implementation lessons and successes
- Tool demo
- Tool walkthrough
- Case study – How a project improved its II nd estimates
- Building your own tool
Learning Objectives:
- Adopting Best practice based on lessons learned from real life challenges in software estimation
- Applying a parametric complexity model in both new product development and maintenance projects
- Demonstration of a MS Excel based tool that has been successfully used in several IT projects
- Applying measurement, calibration and improvement of estimation process in your organizations
- How to evolve the actual data collected from projects to build an organization estimation model
Biography:
Manoj has 14 years of experience in development, testing, project management and quality evaluation of software systems. He has been involved extensively in CMM based SPI initiatives with several organizations in US and Japan, and led quality programs from CMM level 2 to level 5. During last three years Manoj has helped several SPI programs at JP Morgan Chase, New York. He is an authorized CMM Lead Assessor, and is currently a consultant with MetLife, New York. Manoj has been extensively involved in development of estimation methods and tools and facilitating estimation in several software projects. His areas of expertise are CMM/I, ISO 9000, RUP, Six Sigma, PMI methodology, and Information Risk Management. Manoj is a member of IEEE, New York City SPIN and ASQ.
Shanmukha is a member of Process Consulting group at Cognizant Technology Solutions. He worked with organizations at various levels of Process maturity to improve quality and effectiveness of their information systems, by making innovative improvements, and benchmarking practices for estimation processes. Over 10 years of experience in diverse process models, including ISO 9001, CMM, CMMI, BS 7799, ITIL and Six Sigma, puts him in good perspective of the Process Improvement agenda. His current work involves integrating IPPD and TSP to existing process improvement projects. He is a trained Six Sigma Black-belt, CSQA from QAI'USA; certified ISO-14000 Lead Auditor, and Member of PMI.

Lessons Learned from Deploying an Automated Organizational Standard Process System
Kim Genberg & Tim Taylor
Associates
Booz Allen Hamilton
Introduction:
Efficient organizational processes can be established and deployed utilizing an automated process management tool. This presentation will provide the attendees with the lessons learned from a deployment of an Organizational Standard Process (OSP) using an automated process management tool. We will focus on the benefits and challenges when creating and deploying an automated OSP and how this method expedited Process Improvement across our organization.
Lessons Learned include:
- How the selected tool's features can impact process content
- Understanding the complexity of automated tailoring
- Allowing sufficient time to peer review processes before piloting
- Planning for a surge in change requests for the OSP.
Benefits include:
- Central repository for current processes, templates, etc.
- Automated tailoring to help create project specific processes
- Automated creation of a Work Breakdown Structure
- Processes can be mapped to multiple process improvement models such as CMMI, ISO, SSE CMM, which enables the organization to achieve multiple process improvement goals
Challenges include:
- Creating process notation standards that can effectively map to the selected tool
- Managing releases of the OSP and the tool either concurrently or separately
- Engineering the automated tailoring feature so it is not too complex, but is accurate and easily understood
- Ensuring the tool can operate in various environments to include: behind the organization firewall, behind client firewalls, and in classified environments
- Ensuring there is adequate training of staff in tool installation, use of the wizards, tool deployment, and creation of project defined processes
Outline:
- Initial deployment
- Challenge: process architecture – have to determine how to organize content, what content to include and how to put it into the system. There is a need to know how the system functions before developing your processes and this must include:
- Ability to have model blending (i.e., map to multiple models, e.g., CMMI, ISO 9001, etc., or have separate lifecycles that comply to different models, or use tailoring options for different models).
- Model compliance (i.e., map to models).
- Challenge: Once deployed, how to handle the potential surge in the number of change requests that may be generated.
- Benefit: A centrally located easily accessible Organizational Standard Process (OSP).
- Training
- Challenge: time, resources and developing course materials for system training and process training.
- Benefit: Easy transition from project to project and process access at your fingertips.
- Process Management
- Challenge: Culture change to include:
- Implementing best practices (capture, deploy, evaluate).
- Feedback mechanism for submitting Process Improvement Proposals (PIP) using the system.
- Benefit: Central repository where the organization's processes are established and maintained.
- New releases of OSP
- Challenge: typical challenges of deployment (baseline, testing, timing, etc).
- Challenge: How to keep the system and OSP current, and managing releases.
- Benefit: Existing Projects can review and decide to whether to use or not use new process(es).
- Benefit: Virtually eliminates risk of a new project using an old process.
- Diverse Environments
- Challenge: Deployment of multiple OSPs, how to deploy and maintain multiple instances of the OSP (e.g., classified projects require separate repositories, maintaining repositories behind and outside the corporate firewall, how to keep all the repositories synchronized).
- Benefit: Maintains the need for security protection as well as deploying a single OSP.
- Product Standardization
- Challenge: review/approve/control of the library contents.
- Benefit: Common, central library of good/real accessible work products (e.g., Templates and Instructions, Examples, Working Instructions, References, Techniques, Methodologies) that are always up to date.
- Process tailoring
- Automatic tailoring (Using Boolean Logic):
- Challenge: Complexity of choices, making sure not too few and not too many options.
- Challenge: Clarity – how does the user know which one to choose?
- Benefits: Project can easily create a detailed and tailored Project Defined Process (PDP).
- Manual Tailoring of PDP by project:
- Challenge: Project could abuse flexibility, requires the need to monitor (e.g., approval authority can track changes).
- Benefit: Flexibility – Ability for project to modify based on needs of project.
- Reporting
- Challenge: Continual needs for a new report, i.e., the need to continually update the reporting capability.
- Benefits:
- OSP Review reporting – Identifying missing sections, ensures completeness, etc.
- Ensure model compliance.
- Conclusion: Deploying an automated system enabled us to deploy standard processes across our organization that are easily tailored by projects and have enabled them to execute more efficiently. It has provided our staff with the knowledge to help them easily transition into new projects when necessary and has provided them with the capability to easily get involved with our organization's Process Improvement. In addition, it has provided us with the additional benefit of achieving our process improvement goals ahead of schedule.
Learning Objectives:
- How the features of an automated tool may impact the architecture used to define the organization's processes
- How an automated tool can deploy updated versions of processes, templates and working instructions across a diverse organization
- How a project team can effectively access and use the organization's process assets in the automated tool when performing project tasks
- How an automated tool facilitates staff participation in providing Process Improvement suggestions
- How an automated tool's reporting capabilities can ensure project compliance with the organization's processes
Biography:
Ms. Genberg is an Associate of the Worldwide Technology Business of Booz Allen Hamilton. She has 17 years of software development experience including design, development, testing, quality assurance (QA), configuration and release management. She has been a key resource in Booz Allen's migration from CMM Level 3 to CMMI Level 3, which included the documentation and deployment of the QA and Engineering process areas. She is an adjunct instructor for Booz Allen's Center of Performance Excellence , for the Basic and Advanced courses of their process management tool. She is a candidate SCAMPI B/C Lead Appraiser, authorized through the SEI.
Mr. Taylor is an Associate of the Worldwide Technology Business of Booz Allen Hamilton. He has over 7 years of software development experience including project management, requirements, design, test, configuration and release management. He has been a key resource in Booz Allen's migration from CMM Level 3 to CMMI Level 3, which included creating and documenting the Engineering process areas and architecting, deploying and maintaining Booz Allen's Organizational Standard Process. He is an adjunct instructor for Booz Allen's Center of Performance Excellence , instructing the Basic and Advanced courses of their process management system and the Process Immersion course. He has been a member of two SCAMPI B and one SCAMPI A assessment teams.


“Getting What You Look For: Typical Drivers for Process Improvement, and Typical Corresponding Results”
Shawn Presson
Director of Organizational Practice
Apogen Services, LLC
Introduction:
The drivers behind a process improvement effort will have a direct impact upon the approach taken, and will ripple through every project that participates. When that approach is in harmony with business drivers, the resulting outcomes will reflect the day-to-day needs and activities of the business. If not, the resulting practices tend to require significant adjustment to use, and therefore can cause disruption. This can be aggravated when pressure to pass an assessment is the primary driver, which also may influence the choice of assessment method, the preparations for the assessment, and the organization's response to the (possibly unexpected) results.
Outline:
- Examples of Problems in Industry [eye-witness accounts by presenter; organizations will not be identified]
- Common Pain Points in Process Improvement
- Sources of Pain
- Manifestations of Pain
- Remedies
- Background and Purpose of Models
- Model Interpretation
- Assessment Methods and Purposes
- Assessment disasters [eye-witness accounts by presenter]
- Successful Process Improvement Approaches
- Successful re-directs
- Meeting Business Needs
- Tying it all together
Learning Objectives:
After attending this presentation, the participants will:
- Have been exposed to the variety of drivers that cause organizations to undertake process improvement and assessments
- Understand how business motives for process improvements directly influence outcomes of process definition efforts in terms of usability, relevance, and completeness.
- Be aware of different methods of assessment, and their purposes
- Have been exposed to common misunderstandings of assessments, and the value of correcting them
- Understand the basic commonalities among projects even among very disparate application domains and markets, and how models are intended to capture those commonalities
- Be aware of possible roadblocks to process improvement, and how viewpoint analysis may mitigate the risk of encountering them and negotiating more successful approaches within an organization
Biography:
Shawn Presson's background encompasses project management, process improvement consulting, and internal process improvement. He has performed training and hands-on process improvement within organizations from a wide variety of industries, including avionics engineering, pharmaceuticals, transportation systems, manufacturing, document imaging, government contracting, Department of Defense, and commercial software consulting. His active participation in numerous appraisals using the Software Engineering Institute's (SEI) Software Capability Evaluation (SCE) and SEI Capability Appraisal Method for Process Improvement (SCAMPI) methodologies has given him clear insight into how companies attempt the implementation of models such as CMMI and SW-CMM. As an authorized Instructor of the SEI's Introduction to CMM Integrated (CMMI) course, he has a strong appreciation for the challenges in communicating model-based process improvement concepts. As a delivery consultant for shrink-wrapped Process Asset Library environments, he has had extensive experience in seeing how the approach of companies directly impacts their development and communication of process descriptions and assets. Having served as chair of a corporate SEPG, he fully understands the real-world challenges in mapping process improvement efforts to corporate needs.

Importance of Inspections in Outsourced Programming
Jeffrey McArthur
President
JSM Software
Introduction:
Outsourcing software development to India is attractive. Our goal was to develop a method to test the capabilities of a subcontractor to see if they can deliver a system that meets our specifications, requirements, standards, and schedule. I created a qualification test project to assess the capabilities of potential subcontractors. The qualification testing pointed out potential problems. Management approved the subcontractor prior to completion of the qualification testing and awarded the subcontractor two projects. This paper analyzes the reasons why the two projects were disasters.
Outline:
- Overview of the problem
- Needed expansion of our software development capacity
- Outsourcing to India looked promising
- Needed method to evaluate potential subcontractors
- Ability to deliver working system
- Does system meet specifications
- Does system meet our standards
- Was system delivered on time
- Secondary reasons of checking specifications and standards
- Are they complete
- Are they unambiguous
- Are they understandable
- Are they usable
- Is this process compatible with CMMI level 3?
- Selection methodology
- Non-compete and non-disclosure agreements
- Watts S. Humphrey (1989) defined four important steps
- Start with a very precise statement of what was wanted.
- Insist on rigid standards and detailed documentation of every process step.
- Require completion and approval of each step before the next step initiated.
- Demand a firm commitment at the outset.
- Metrics: lines of code
- Not perfect but easy to measure
- Metrics from current systems
- Amount of documentation
- Comparison of code density
- Limitations of the study
- Small sample set
- Failure may not be an option
- Qualification testing
- Redevelopment of existing system
- Not a real project
- Results of testing
- Portions of the specification were incomplete or ambiguous
- Coding standards were not followed
- Metrics show major deviations
- Delivered system not fully functional
- Major subsystem missing
- Major subsystem malfunctioning
- Premature acceptance
- Management focused on look and feel and not quality of coding
- Management insisted on success
- Management ignored problems
- Management wanted to move to a real project
- Subcontracted accepted and awarded project
- Transferred from software director to project manager
- Project manager had no experience with this programming language
- Project manager was indifferent to coding standards
- Focused on look and feel
- Did not understand why errors continued to return
- Results of acceptance and awarding project to subcontractor
- Delivered system not fully functional
- Major subsystem missing
- Major subsystem malfunctioning
- Coding standards completely ignored
- Project delivered late
- Peer review code review said code was “junk” and needed to be thrown away
- Management response
- Subcontract blamed
- Termination of contract with subcontractor
- Lessons to be learned
- It is impossible to create complete and unambiguous specifications without review from outside agent
- Coding standards are very important
- Project management experience alone is not sufficient
- Verification of coding standards is important
- Metrics help verify coding standards
Learning Objectives:
- Details are important in programming
- The output or user interface does not define the quality of the programming
- Good project management requires understanding the software tools used
Biography:
In March of 2004 I established JSM Software with the goal of providing business intelligence solution using a total quality management approach. Prior to establishing JSM Software I managed a software development group of ATLIS Systems for eight years. During that time we have developed numerous software systems for our clients. My goal was to advance the software development group from CMMI level 2 to level 3.

Choose Your Measures Wisely: A Case Study Using GQ(I)M
Feno Monaco & Teresita Ignacio
Estimation & Metrics Team Leaders
Allstate Insurance Company
Introduction:
Each measurement has a cost associated with it. These costs affect the
- Project Team
- E&M Team
- Project Management
- Senior Management
These costs are realized in collection, analysis and reporting of the measures. They must be considered during the inception of a measurement program. Lower maturity organizations are often tempted to identify a large number of initial measures, often damaging the measurement initiative. This can be avoided by injecting some structure, such as Goal Question Indicator Measure (GQIM), into your metrics program. The initial measure identified should be well defined, and collectable. The program will lose credibility if measurements are collected and not used, or if measures are constantly dropped.
Outline:
- Measurement program fundamentals
- GQ(I)M approach
- Architecture of a measurement plan
- Types of measures
- Reporting
- Case study – building the measures
- Pitfalls of measurement
Learning Objectives:
- Learn the basics of measurement and approaches to defining measures
- Learn the basics of a measurement plan
- Gain insights on reporting the value of a measurement program
- Gain insights on the challenges faced by a measurement program
Biography:
Feno M. Monaco, PMP, is the manager for the Estimation & Metrics (E&M) team at Allstate Insurance. Additionally, Feno has nearly 10 years global consulting experience, where he spent 5 of those years managing a global E&M team. Mr. Monaco has taken several E&M teams from idea to full operational capability. Those E&M teams have been integral in supporting external assessments of CMM L3 maturity in multiple geographies. Along with his PMP certification, Mr. Monaco is trained as a SW-CMM assessor and CMMI SCAMPI team member. Mr. Monaco has served as chairperson for a metrics conference and has presented on estimation and metrics topics at multiple conferences.
Teresita Ignacio is an Estimation & Metrics Consultant at Allstate Insurance Company, working on estimation of large projects, development and implementation of estimation tools and processes. She has over 20 years experience at Allstate on software development, process improvement, quality improvement, measurement and analysis. Ms. Ignacio is experienced in presenting on the topic of estimation and measurement.

A Software Development Process to Successfully Implement COTS (Commercial Off The Shelf) Enhancements
Charles Schiano
Manager Systems Development
Introduction:
The paper and presentation will discuss the System Development Life Cycle and PM approach to successfully manage 3rd party software vendors in adapting their COTS solution to your unique business requirements.
Outline:
- The Technical Statement of Work, what should be included
- The Request for Proposal (RFP), what should be included
- Defining Functional Requirements, integrating the vendors software into your requirements
- Testing to requirements
- Change Management
- Acceptance
- Staff Training
- Support
- Project Management
Learning Objectives:
- Keeping the vendor on schedule
- Off-site vendor development
- Keeping the End User involved
- Change Management Control
- Testing to your environment with your data
Biography:
Mr. Charles Schiano has over 35 years of experience developing large-scale software systems for various governmental agencies. He was a Senior Program Manager at Grumman Data Systems, a defense contractor and systems integrator, from 1965 to 1995, leaving after the acquisition by Northrop. Since leaving Northrop Grumman in 1995 he has applied his IT development and implementation knowledge to the “non Federal” systems marketplace, first to Police and Fire Departments and now at a NYS governmental agency modifying systems based upon 3 rd party COTS that assist in the day to day operations of the business.
Mr. Charles Schiano has authored over 15 technical papers concerning software systems and how they were utilized to increase worker productivity. He has been a member and officer of several professional IT organizations. He has chaired technical sessions at conferences and has participated in many panel discussions. He has BS in Mathematics from Adelphi University and a MS in Industrial Management from New York Polytechnic Institute.


What Goes on Behind Closed Doors - How to get the Appraisal Team to Say Yes
Tim Davis & Tom Lienhard
Senior Engineer Manager/Senior Principle Engineer
Raytheon Missile Systems
Introduction:
Have you ever wondered what the appraisal team discusses behind those closed doors as you wait for the final briefing? Wished you knew what you could do to help stack the odds in your favor? Wouldn't it be nice if you had insight into what influenced their decisions? What would you give to know what you could do to make the appraisal team give you a thumbs up? This presentation will give you that insight and detail what an organization can do to get the appraisal team to vote yes. Hear from actual appraisal team members who have participated on multiple Class C, B and A appraisals as to what an organization can do to help the appraisal team vote thumbs up.
Outline:
- Treat CMMI deployment like a program
- Be prepared
- Form the mindset from the beginning
- Have a consistent story
- Enable the appraisal team to do their job
- Make it hard for the appraisal team to say no
- Don't surprise the appraisal team during the SCAMPI
Learning Objectives:
- Key items for success from an appraiser's point of view
- How to leverage the appraisal team to your benefit
- Make the appraisal team part of the success
- Be prepared
- Quality not quantity
Biography:
Tim Davis is currently a senior engineer manager at Raytheon Missile's Tucson facility and heads a systems engineering department which supports the Air-to-Air and Land Combat product lines. His thirty one year career with the company has been split almost evenly between embedded tactical software development and systems engineering activities.
His tour of duties as a lead software developer have included numerous CMM assessments up to and including CMM level 4. This legacy followed Tim to the systems engineering environment, where he has been providing active support for achieving the Corporate CMMI goals. During 2003, Tim was an Appraisal Team Member for two SCAMPI “B” level appraisals and the SCAMPI “A” SW/SE level 3 appraisal of the Raytheon SAS Business Unit. Currently, he is assigned as an Appraisal Team Member for the Missile Systems CMMI level 3 initiative as well as an ATM for the Raytheon SAS CMMI level 4 efforts.
Tom Lienhard joined Raytheon Missile Systems in 2001working in the Software Engineering Process Group (SEPG). He has over 15 years experience developing, overseeing, and improving software development processes. He was part of the SEPG core team that enabled Raytheon Missile Systems achieve CMM Level 5 in 2001. Prior to joining Raytheon, Tom worked for Honeywell, AlliedSignal and Hughes Aircraft Company. He is a CMM and CMMI appraiser having done over 35 appraisals worldwide as well as a certified Six Sigma BlackBelt. He has presented at a variety of software engineering and SEPG conferences throughout America and Europe and taught Software Six Sigma across both continents. He was awarded the Quest for Excellence Award in 1999, Excellence in Technology Award in 2001, and the Best Presentation Award at the 2002 Systems and Software Engineering Symposium.

Software Estimation Process Deployment – Journey from “Gut Estimate” to Using Formal Models
Ashish Saxena & Rajesh Rajendran
SPI Consultants
TCSL
Introduction:
Description of Estimation Lead responsibilities in deploying formal estimation process and mentoring, challenges and success factors.
Outline:
To provide an overview of the challenges and success factors in deploying estimation model in a large organization.
- As is process – “Gut Estimate” - How it impacted the organization
- Need for a formal process
- Management Expectations
- Benefits to the organizations
- CMM certification journey
- Choice of Models – to select industry standard models or develop a model
- Challenges in deployment – initial strategy adopted
- Development of a new estimation model to best suit in-house process
- Process Feedback
- Change in deployment strategy
- Validation of model accuracy
- Collection of project data
- Validation of estimates
- Next steps – use of a common tool across the organization
Learning Objectives:
- Importance of Estimation for an organization / project – “If you cannot measure it, you cannot manage it”
- Deploying formal estimation process in a large organization – strategy, lessons learned and success factors
- Data based validation of estimation models
- Estimation as one of the primary inputs for project planning – top down vs. bottoms up
- Challenges in tracking actual effort figures vs. the estimates
- Fine tuning the estimation model
Biography:
Ashish Saxena has 3.5 years of experience in deploying software estimation models at Client location as Estimation Lead and Estimation Mentor. Overall 6.5 years experience in using various estimation models, reviewing and formally approving the project estimates.

|