Military Handbook 881 Work Breakdown Structure Update



Similar documents
WORK BREAKDOWN STRUCTURES FOR DEFENCE MATERIEL PROJECTS

THE WORK BREAKDOWN STRUCTURE IN AN ACQUISITION REFORM ENVIRONMENT. Prepared For: COST SCHEDULE PERFORMANCE MANAGEMENT CONFERENCE

Developing Work Breakdown Structures

Cost and Software Data Reporting Training

DEPARTMENT OF DEFENSE HANDBOOK

Update: OSD Systems Engineering Revitalization Efforts

ROYAL REHAB COLLEGE AND THE ENTOURAGE EDUCATION GROUP. UPDATED SCHEDULE OF VET UNITS OF STUDY AND VET TUITION FEES Course Aug 1/2015

Using Parametric Software Estimates During Program Support Reviews

Cost and Software Data Reporting (CSDR) Manual

Earned Value Management Systems Application Guide

Government Contracting and Earned Value Management (EVM)

System Security Engineering

WORK BREAKDOWN STRUCTURE HANDBOOK

DEPARTMENT OF DEFENSE STANDARD PRACTICE

How To Write Ansi/Eia Evm System Acceptanceance Guide

Earned Value Management Systems Application Guide

Space and Naval Warfare Systems Center Atlantic

AT&T Global Network Client for Windows Product Support Matrix January 29, 2015

BY ORDER OF THE COMMANDER USTRANSCOM INSTRUCTION UNITED STATES TRANSPORTATION COMMAND 22 JUNE 2015

CYBERSECURITY CHALLENGES FOR DOD ACQUISITION PROGRAMS. Steve Mills Professor of Information Technology

Systems Thinking in DoD Program Management

WBS Development: Rules, Aberrations, and MIL-STD-881C Implementation Challenges

How To Manage The Navy Marine Corps Intranet

Program Management vs Systems Engineering

Appendix B: Work Breakdown Structure (WBS)

CPM -100: Principles of Project Management

Department of Defense MANUAL

How To Become A Senior Contracting Official

NICE and Framework Overview

Best Practices for the Acquisition of COTS-Based Software Systems (CBSS): Experiences from the Space Systems Domain

Space Systems Engineering Professional Development & Certification

WORKFORCE COMPOSITION CPR. Verification and Validation Summit 2010

U.S. Dept. of Defense Systems Engineering & Implications for SE Implementation in Other Domains

COMPARISON OF FIXED & VARIABLE RATES (25 YEARS) CHARTERED BANK ADMINISTERED INTEREST RATES - PRIME BUSINESS*

COMPARISON OF FIXED & VARIABLE RATES (25 YEARS) CHARTERED BANK ADMINISTERED INTEREST RATES - PRIME BUSINESS*

RISK MANAGEMENT GUIDE FOR DOD ACQUISITION

SYSTEMS SECURITY ENGINEERING

PROGRAM MANAGEMENT IN DEFENSE SYSTEMS

Certified Associate in Project Management (CAPM) Examination Content Outline

Computing & Telecommunications Services Monthly Report March 2015

REQUEST FOR PROPOSALS (RFP) FOR RETAIL NATURAL GAS SUPPLY SERVICE

Modelling the Management of Systems Engineering Projects

Cost Management. How Much Will This Project Cost?

Using Earned Value Management Concepts to Improve Commercial Project Performance

Headquarters U.S. Air Force. Building CERs & SERs for Enterprise Resource Planning (ERP)

DoD Software Assurance Initiative. Mitchell Komaroff, OASD (NII)/DCIO

GOVERNING BODY MEETING held in public 29 July 2015 Agenda Item 4.4

DOCUMENTING THE SOFTWARE DEVELOPMENT PROCESS. June S. Hopkins and Jean M. Jeroow. Litton Data Systems 8000 Woodley Ave. Van Nuys, CA 91406

DEPARTMENT OF DEFENSE HANDBOOK PARTS MANAGEMENT. This handbook is for guidance only. Do not cite this document as a requirement.

FOREWORD. Page 2 of 88

Earned Value Management and the Government Program Office. Blair Alan Knapp Jr. MSPM PMP

LABOR CATEGORIES: Minimum Requirements

The Department of Defense (DoD) has reached

3.1 Overview of Software Development and Integration Activities

Program Lifecycle Methodology Version 1.7

An Application of an Iterative Approach to DoD Software Migration Planning

How To Implement Itil V3

FACT SHEET. General Information About the Defense Contract Management Agency

DEFENSE BUSINESS PRACTICE IMPLEMENTATION BOARD

ACA Online Training September 2014 Intake

Evolving DoD Policy Life Cycle Management and Product Support

RISK MANAGEMENT GUIDE FOR DOD ACQUISITION

SEBoK: a guide to the systems engineering body of knowledge

Risk Management in DoD Programs

Assessment of NCTD Program Management Framework for Positive Train Control Program

ISO 9001:2000 Its Impact on Software

Department of Defense DIRECTIVE

GAO COST ASSESSMENT GUIDE. Best Practices for Estimating and Managing Program Costs. Exposure Draft. Applied Research and Methods

Using EVMS with COTS-Based Systems

Project Management Professional Training

AC : ASSOCIATE SYSTEMS ENGINEERING PROFESSIONAL (ASEP) CERTIFICATION: A CREDENTIAL TAILORED FOR STUDENTS AND JUNIOR ENGINEERS

Introduction to the CMMI Acquisition Module (CMMI-AM)

CYBERSECURITY CHALLENGES FOR DOD ACQUISITION PROGRAMS. Steve Mills DAU-South

PROJECT MANAGEMENT PLAN <PROJECT NAME>

Introducing Competency-Based Employee Performance Management for Public Health Nurses: A Toolkit and Piloting Strategy

Case 2:08-cv ABC-E Document 1-4 Filed 04/15/2008 Page 1 of 138. Exhibit 8

National Defense Industrial Association Systems Engineering Division Task Group Report Top Five Systems Engineering Issues

An introduction to Earned Value Analysis

DICK BRODKORB FAX ( ) 3 THEN CHECK THE LOCATION YOU LL BE ATTENDING.

LOCKHEED MARTIN CORPORATION PRIME SUPPLEMENTAL FLOWDOWN DOCUMENT (PSFD) ADDITIONAL TERMS AND CONDITIONS FOR SUBCONTRACTS/PURCHASE ORDERS UNDER

Using CMMI Effectively for Small Business Panel

Department of Administration Portfolio Management System 1.3 June 30, 2010

Project Management Standards: A Review of Certifications/Certificates

A COMPARISON OF PRINCE2 AGAINST PMBOK

International Acquisition Career Path

Transcription:

Military Handbook 881 Work Breakdown Structure Update Presented By: Neil Albert 25 August 2004 MCR, LLC 2000 Corporate Ridge, Suite 400 McLean, VA 22102

Update to incorporate DoD changes in Acquisition Policy and Guidance Task 1: Update for DoD 5000 changes Task 2: Identify how the WBS can support each acquisition phases and the actions necessary to enter and exit successfully Task 3: Reflect changes to new and improved approaches to product development (i.e., IPTs) Task 4: Show how WBS is developed and maintained throughout the life cycle to meet program management goals as well as cost, schedule and technical objectives Task 5: Show how the WBS is the common link which will unify the planning, scheduling, estimating, budgeting, configuration management and performance reporting disciplines

Schedule Task July Aug Sept Oct Nov Dec 1. Update to Include DoD Policy and Guidance 2. Add/Improve on WBS Definitions 3. Used with newer terms and policies 8-Jul 8-Jul Draft WBS Def Final Review 4. Characterized as an Acquisition tool 5. Support Budget, Cost, Schedule, Technical, Contractual, and Program Management 6. Integration with Program Management, Systems Engineering, Contractual and Cost Estiamting Documents 7. Ensure Industry Participation 8. Format for Web Access 8-Jul Monthly Progress Reports Government Review Mid Term Review Final Review

Expectations Integrating with current AT&L and DCARC activities New procedures and requirements being considered that affect the use of the WBS in both CPR and CSDR Become involved with working groups already making changes to CPR and CSDR processes that affect the WBS Ensure Handbook becomes a comprehensive guide for Industry and Government Outreach support Work with major DoD organizations to get the inputs needed to make the Handbook a government and industry wide document Use participation in all major professional associations Leverage relationships to gain insight, lessons learned and new innovations and ideas for better execution

Task 1: Add/Improve upon WBS definitions Update definitions to reflect advancement of technology in design, development and manufacturing Heavier reliance on software Commercial-off-the-shelf items (Status: Working groups formed to address issues working with other contractor representatives) Establish a Working Group consisting of Government and Industry to review at least the following appendices and provide comments and potential revisions Aircraft specifically UAVs Space Multiple definitions NASA, NRO, DoD, etc. Ships Waived for CSDR no longer (Status: Working groups formed, initial response due 10 Sept. Meetings to be held week of 20 Sept)

Task 2: Clarify how WBS is used with newer terms and processes System of Systems/Family of Systems Clarify terminology and highlight examples of how the WBS is created given the requirement for system interaction and interoperability Show example of System of Systems WBS Spiral/Evolutionary Development (Hardware/Software) Each spiral provides new functionality which could be considered product oriented, but better definition is required Will define terminology and provide examples of how the WBS is created given an evolutionary requirement. (Process is already defined in the software WBS description --- most software engineers used spiral development to create software in the early 1990 s) Risk Analysis Description of risk analysis use with WBS System Engineering use to trade cost, schedule and technical risk of the system to meet end-item requirements (Status: Collecting information for inclusion in document)

Task 3: Ensure the WBS is characterized as an Acquisition tool To decrease the use of multiple WBSs used by different functional areas, define the WBS for all practical uses: Cost Estimating EVM Database Scheduling Requirements planning, etc. Establish group of system engineers, cost analysts, logisticians, earned value management technicians, program managers and contracts personnel to agree and commit to one approach defining and using the WBS for program support Maintain a product oriented WBS reporting at level 3 (except for high cost, high risk or technology driving elements) Communicate result by follow on training (Status: Starting to contact appropriate associations)

Task 4: Support Budget, Cost, Schedule, Technical, Contractual and Performance Management Identify DoD 5000 has mandated certain reporting functions that rely on the WBS Contract Funds Status Report Contractor Cost Data Reporting Earned Value Management Use example (e.g., Joint Strike Fighter) Demonstrate how acquisition reports will track to each other if a single WBS is used Show relationship to CLIN SOW Requirements IMP/IMS (Status: Not started)

Task 5: Integrates with PM and SE Documents, Contracts and Cost Estimating Re-enforce the use of the WBS via example Show that without the WBS, the IMP/IMS relationship to other acquisition artifacts would not be possible (Status: Not started)

Ensure Industry Participation Involve those who are affected by the changes by having them participate in making those changes Embrace as many joint industry/government associations as possible to get buy-in and feedback Task 1&2: Working groups comprised of functional experts to re-examine WBS definitions proposed for review Task 3: Use Govt and industry representatives to ensure all aspects of WBS application and usage are considered and reflect real life situations Program Management: Project Management Institute (PMI) System Engineering: International Council on Systems Engineering (INCOSE) and National Defense Industrial Assoc (NDIA) Cost Estimating: Society of Cost Estimating and Analysis; Cost and Software Data Reporting (CSDR) Focus Group and Space Systems Cost Analysis Group (SSCAG) Earned Value Management: PMI s College of Performance Management and NDIA s Program Management Subsystems Committee Logistics: Society of Logistics Engineers (SOLE) Contract Management: National Contract Management Association (NCMA) Tasks 4&5: Use DAU to ensure changes reflect understanding and communication of the revisions to DoD 5000 processes and terminology affecting the WBS