spmn.com
Software Program Managers Network - About SPMN
http://www.spmn.com/www2/aboutus.html
The SPMN was established in 1992 by the Assistant Secretary of the Navy to i. Dentify proven industry and government software best practices and convey these practices to managers of large-scale DoD system acquisition programs. The SPMN 16 Critical Software Practices. Specifically address underlying cost and schedule drivers that have caused many software intensive systems to be delivered over budget, behind schedule and with significant performance shortfalls. Independent Verification and Validation.
spmn.com
Software Program Managers Network - "16 Critical Software Practices TM"
http://www.spmn.com/www2/16CSP.html
The SPMN was established in 1992 by the Assistant Secretary of the Navy to identify proven industry and government software best practices and convey these practices to managers of large-scale DoD system acquisition programs. The SPMN 16 Critical Software Practices. Specifically address underlying cost and schedule drivers that have caused many software intensive systems to be delivered over budget, behind schedule and with significant performance shortfalls. 16 CRITICAL SOFTWARE PRACTICES. That serve as...
spmn.com
Software Program Managers Network - "SOFTWARE DEVELOPMENT BULLETIN"
http://www.spmn.com/www2/lessons.html
SPMN Focus Team Lessons Learned. 2 Safety and Security. 3 Continuous Risk Management. 5 Planning and Tracking. 6 Products Required for Delivery. 15 Retaining Technical Staff. 16 Approach to Achieving Higher SEI Rating. 17 Integrated Product Teams. 21 Cost of Maintenance. 22 Software Development Environment/Tool Utility. 24 Commercial-off-the-Shelf (COTS) Products. Systems Engineering on Embedded Weapon System Programs. No or very inadequate trade-off studies are conducted to reduce the risk of high-risk ...
spmn.com
Tri-Service Software Program Managers Network
http://www.spmn.com/index.html
The SPMN was established in 1992 by the Assistant Secretary of the Navy to identify proven industry and government software best practices and convey these practices to managers of large-scale DoD system acquisition programs. These 16 Critical Software Practices. Specifically address underlying cost and schedule drivers that have caused many software intensive systems to be delivered over budget, behind schedule and with significant performance shortfalls. Although the SPMN funding was cancelled in 2001,.
spmn.com
Software Program Managers Network - Web Links
http://www.spmn.com/www2/links.html
Reducing Total Ownership Cost (TOC); career development and training opportunities; library; links. Air Force Materiel Command (AFMC) Contracting Laboratory's Federal Acquisition Regulation (FAR). FAR search tool; Commerce Business Daily Announcements (CBDNet); Federal Register; Electronic Forms Library. Air Force Operational Test and Evaluation Center. The Program Managerï s WorkStation ( PMWS. To make informed decisions through all phases of product development, production, and beyond. Structure and mi...
spmn.com
Software Program Managers Network - Comments
http://www.spmn.com/www2/comments.html
Comments About the Program Manager's Guide to Software Acquisition Best Practices (version 2.0). Program Manager, U.S. Army. Once again, thank you for your superb support. Most of the material in this report hits the mark squarely and should be strongly supported.". Space-Based Early Warning Systems (EWS) Program Office. This document provides a list of Best Practices which is an extensive, interesting, and helpful inventory of ideas, conventions and techniques for improving software acquisition.". This ...
SOCIAL ENGAGEMENT