This session is sponsored by the Federal Acquisition Institute

1. This session is sponsored by the Federal Acquisition Institute The primary organization providing knowledge and support to the federal civilian acquisition workforce. For more information about FAI, please visit our website at www.fai.gov

2. Procurement Project and Program Alignment GSA Training Conference and Expo 2010 Michael Bevis Competency and Certification Manager Federal Acquisition Institute

3. Transparency Alignment Line of Sight What’s the Point?

4. Acquisition as Sub-Project • The definition of a Project • The timing of acquisition planning • Project Planning • Rolling wave planning • Make/Buy analysis • Role of Acquisition Professionals • Stakeholder Analysis

5. Who are Acquisition Sub-Project Stakeholders? • Who gets the output from the project? • Who provides project input? • Who has oversight? • Who has additional project responsibilities? • Who benefits from the project? • Who may be adversely impacted by project outcome?

6. Acquisition Sub-Project Stakeholders include: Project Manager - individual responsible for managing the project. Customer/User - individual or organization that will use the product (or service) from the project. Performing Organizations - organizations whose individuals are doing work on the project Team Members – individuals that will be completing project work tasks Project Team – The team members directly involved in project activities Portfolio Review Board – Reviews projects at governance level for ROI and value to the organization. Sponsor - individual or group who provides the funding (financial resources) for the project. Influencers – those who can positively or negatively influence project outcomes PMO – The PMO has direct or indirect responsibility for project components

7. Preexisting Sources of Information (PM Inputs): • Project Charter • Provides high-level mission/project requirements • Provides high-level product description • Stakeholder Register • Identifies stakeholders that can provide detailed project and product requirements information

8. Stakeholder Involvement Tools: • Directly talking with stakeholders • Formal/Informal • Prepared Questions/Spontaneous question

9. Stakeholder Involvement Tools: Focus Groups • Prequalified stakeholders and subject matter experts • Interactive discussion lead by trained moderator • More conversational

10. Stakeholder Involvement Tools: Facilitated Workshops • Focused sessions to define cross functional requirements • Promote trust, improve communication, increase consensus

11. Stakeholder Involvement Tools: • Group Creativity • Brainstorming • Nominal Group • Delphi • Idea/Mind Mapping • Affinity Diagram

12. Stakeholder Involvement Tools: • Questionnaires and Surveys • Quickly accumulates information from wide # of respondents • For broad audiences, quick turnaround need, & statistical analysis • Observations • Direct way of viewing individuals in their environment • When stakeholders are reluctant to articulate requirements • Prototypes • Early feedback on requirements from working model of product • Supports progressive elaboration

13. The Results of Stakeholder Input: • Acquisition Requirements Documentation • Describes how individual requirements meet the business/mission need • May start high level and become more detailed as more is known • Acquisition Requirements Management Plan • Describes how requirements will be analyzed • Describes how requirements will be documented • Describes how requirements will be managed • Acquisition Requirements Traceability Matrix • Links and tracks requirements to their origin • Ensures approved requirements are delivered

14. Acquisition requirements documentation includes: • Business Rules • Organizational Impacts • Other Entity Impacts • Training/Support Requirements • Requirements Assumptions • Requirements Constraints • Mission/Business Need • Project Objectives • Functional Requirements • Non-functional Requirements • Quality Requirements • Acceptance criteria

15. Acquisition Traceability Matrix should trace the following: • Requirements to project/mission needs, opportunities, goals, and objectives • Requirements to project objectives • Requirements and ultimately Contract Work Breakdown Structure to project scope/WBS deliverables

16. Acquisition Traceability Matrix should trace the following: • Requirements to product design • Requirements to product development • Requirements to test strategy and test scenarios • High-level requirements to more detailed requirements

17. Transparency Alignment Line of Sight What’s the Point?

18. Thank You For your Commitment, For your Professionalism, For your Presence, For your CHOICE Service.

19. Procurement Project and Program Alignment GSA Training Conference and Expo 2010 Michael Bevis Competency and Certification Manager Federal Acquisition Institute

20. This session is sponsored by the Federal Acquisition Institute The primary organization providing knowledge and support to the federal civilian acquisition workforce. For more information about FAI, please visit our website at www.fai.gov