1 / 4

Fiscal Year 2003 Survey of Acquisition Project Managers

The survey conducted in FY 2003 focused on identifying major acquisition problem areas for Army project managers, shedding light on areas for improvement, and pinpointing the toughest challenges faced. Findings revealed root causes that require corrective actions in RM tools, training, process documentation, external factors, and policy guidance.

kiara
Download Presentation

Fiscal Year 2003 Survey of Acquisition Project Managers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Fiscal Year 2003 Survey of Acquisition Project Managers Army Strategic Software Improvement Program (ASSIP) AAG Meeting Nov. 5, 2003 Mark Kasunic Software Engineering Measurement and Analysis [SEMA] Software Engineering Institutemkasunic@sei.cmu.edu

  2. Purposes of Survey There were two primary purposes for this data-collection effort. Provide preliminary insight into the major acquisition-related problem areas (as perceived by Army PMs) so that improvement opportunities can be prioritized 1 Assist development of future data collection activities by shedding light on the problem space, thereby allowing more detailed data-gathering in identified focus areas 2

  3. Two Most Difficult Problems Facing Acquisition Managers - 1 63 Requirements Management 22 Project Management 22 Contractor processes 21 Unstable Funding 16 Required Skills 12 Interoperability 9 Integration Response Categories 8 Testing 8 Mandates 6 Technology Change 4 Policy 8 Other 18 No Response 8 N/A 0 10 20 30 40 50 60 70 Frequency 225 Responses

  4. RM Root Causes Finding the Root Causes of Symptoms • It’s important to distinguish causes from the symptoms. We shouldn’t assume we know the solution for a symptom. We need to understand the root causes … and focus corrective actions there! People People Process Process Lack easy-to-use RM tools Lack of appropriate training RM process undocumented Technology Technology External factors External factors Lack of policyguidance

More Related