general dynamics communication systems “process maturity: things that work” boston spin panel...
TRANSCRIPT
GENERAL DYNAMICS
Communication Systems
“Process Maturity: Things that Work”
Boston SPIN PanelApril 18, 2000
Presenter: Carol Pilch
April 18, 2000 2GENERAL DYNAMICS
Communication Systems
Background - 1
General Dynamics Communication Systems Systems Integrator 2000 employees 230 software engineers in Needham/Taunton Project size: 1-40 software engineers 8 Million lines of developed code Commercial-off-the-shelf based systems
April 18, 2000 3GENERAL DYNAMICS
Communication Systems
Background - 2
Products/Services Network Management Network Integration Tactical Communication Systems Encryption Training/Distance Learning
April 18, 2000 4GENERAL DYNAMICS
Communication Systems
Background - 3
15 years of Software Process Improvement Corporate Software Steering Committee - 1985 Corporate Software Development Process - 1985 CMM v1.1 - 1994 CMM Level 3
April 18, 2000 5GENERAL DYNAMICS
Communication Systems
Process Improvements
1994-1999Organizational software process definitionStandard software toolsetTailorable metrics definitionProcess, tools, and methods trainingRework reduction initiative
2000+ Improve systems and hardware processesTrain/institutionalize Level 4/5 practices
April 18, 2000 6GENERAL DYNAMICS
Communication Systems
Enablers
Demonstrated senior management commitment Full-time SEPG Monthly Software Status Reviews Early use of metrics Process tailoring guidelines Software Project Management Course Assessments and Improvement Plans Software Quality Assurance
April 18, 2000 7GENERAL DYNAMICS
Communication Systems
Some Results
Standard process recognized as the way we do business
Measured improvement in productivity and quality
Training valued by management Personnel move easily among projects
Value added -“Not process for process sake”
April 18, 2000 8GENERAL DYNAMICS
Communication Systems
Project Factors
Tailoring guidelines are key: one size does not fit all large project vs. small project development vs. maintenance custom development vs. off-the-shelf external customer vs. internal customer deliverable product vs. proof-of-concept
April 18, 2000 9GENERAL DYNAMICS
Communication Systems
How long did it take? CS Software Process History Timeline
CBA IPI Assessments
1985-1989 1990-1994 1995 1996 1997 1998 1999 2000
Corporate Software Steering Committee Corporate Software Development Methodology (“Brown Book”)Affiliated with SEI, in 1986 - Resident Affiliate at SEI 1986-1997Participation in collective Software Best Practices & original questionnaireMarch 1988 - SEI-assisted Assessment (W. Humphrey)
Member of CMM Advisory BoardSector SEPG/SEG establishedSEPG at Division LevelCS Process Documents
Rework Reduction
Project Mgmt TrainingMetrics Refinement
Mini Assessment
CMM Level 4 PilotIntegrated Eng. Process
CMM Level 3
April 18, 2000 10GENERAL DYNAMICS
Communication Systems
Recommendations
CMM used as a roadmap CMM training for all levels of management Periodic software status reviewed by senior
management Dedicated SEPG staffed by experienced software
engineers/managers Independent Software Quality Assurance Standard software toolset with dedicated support Early measurement - size, progress, quality In-house training provided by subject matter experts