SUPPORT THE WARFIGHTER MPE Reference Architecture Development Kick-off Meeting Deputy Director Architecture & Interoperability Office of the DoD CIO Thomas Lam

SUPPORT THE WARFIGHTER Meeting Agenda Expected Outcome of the Kickoff Review MPE RA/BP Review the Agile Approach o Roles & Responsibilities o Identify Team Members & SMEs Discuss content for the proposed Baseline Work Package Review and Commitments Discuss Timeline to achieve Baseline 2

SUPPORT THE WARFIGHTER Expected Outcome of Kickoff Meeting A clear understanding of MPE RA purpose, scope, value and proposed timeline A commitment to participate in the development of the MPE RA 3

SUPPORT THE WARFIGHTER MPE RA Roadmap 4 Today (As-Is) Future (To-Be) Time Phased Transition Capabilities Roadmaps Systems Roadmaps MPE Time Phased Transition Plan Programs of Record That provide Capabilities Identified MPE Capabilities from Sprints FYDP Delivered Capability Planned Capability

SUPPORT THE WARFIGHTER Overview of MPE RA Purpose o A high-level overview of the current (as-is) MPE, o A blueprint for the target (to-be) MPE, and o A high-level roadmap for transforming from the current state to the target state. Scope Objectives Questions to be answered Assumptions Constraints Final Products - Baseline 5

SUPPORT THE WARFIGHTER Agile Approach to Architecture Development 6 Sprint Team Reports: -What they did yesterday -What they are doing today - Any blocks in their way Kanban Board Stakeholder Customer (User) Product Owner Tea m Sprint TEAM -2-5 People -Cross-Functional -Individuals Can be Shared -Use multiple team on MPE Tasks working in parallel -Include SA architects -Requirements list created by Product Owner -Ranked by importance -Product Owner can change Requirements between sprints - Release Plan is built-in Scrum Master Daily 10-minute “Stand-up” Meeting -At Least: Functionally that requirement can be demonstrated and tested -Finally: Implementable For Each Iteration (Sprint) -Team selects, starting from top of list -Team then breaks down into tasks -4-6 hours of work per person per day -Team member Commitment is fixed for the duration of the Sprint -No items are added until next Sprint Stakeholder Review 1-4 Week “Sprints” Of work Providers Work Package Sprint Output Review Scrum Master Product Owner

SUPPORT THE WARFIGHTER Discussion on the Baseline Content “As-IS” Capability o The ability to execute a specified course of action. A capability may or may not be accompanied by an intention. DoD Instruction , May 21, 2014 o The potential ability of somebody or something to do something. Encarta Dictionary o What is the name and description of the Capability?, Who/what system is providing the Capability?, When is the capability available?, What organization sponsors the Capability? Data Model – Meta Data o A conceptual and logical description about information being shared between two or more individuals. o Information about a ”conversation” among mission partners. o What data is being shared?, What is the flow of data (conversation)?, What is the source of the data?, How is it used?, Where is it stored?, Who can the data be shared with? Connectivity o The ability to communicate (exchange information) with another system or piece of hardware or software, or with an Internet site. Encarta Dictionary o What are the Connections? What are the standards/protocols/profiles?, What are the networks? 7 Types of questions that a Sprint team will answer. The MPE RA/BP will contain this content and use it to answer other questions asked of the architecture and roadmap.

SUPPORT THE WARFIGHTER FMN Concept of Operations Requirements to Sprint Interval Focus FMN ICD Mission Partner Environment Tier 1 Goal 1 Improve Mission Effectiveness & Operational Flexibility Goal 1 Improve Mission Effectiveness & Operational Flexibility Goal 2 Enable Federated Cyber Security & Defense Goal 2 Enable Federated Cyber Security & Defense Goal 3 Efficiently Deliver Joint Information Services Goal 3 Efficiently Deliver Joint Information Services Objective 1 Implement Open Architecture Concepts That Promote Effective and Dynamic Information Exchange Among Mission Partners Objective 1 Implement Open Architecture Concepts That Promote Effective and Dynamic Information Exchange Among Mission Partners Objective 2 Optimize MPE Service Provisioning Processes to Enable Access To Information Objective 2 Optimize MPE Service Provisioning Processes to Enable Access To Information Objective 3 Enable an Interconnected and Agile Mission Network to Support Mission-Specific Needs Objective 3 Enable an Interconnected and Agile Mission Network to Support Mission-Specific Needs Work Item 1 Capability Review Work Item 1 Capability Review Work Item 2 Data Model Review Work Item 2 Data Model Review Work Item 3 Connectivity Work Item 3 Connectivity Exit Criteria 1 Identified POCs of Capability Lists Exit Criteria 1 Identified POCs of Capability Lists Exit Criteria 2 Identified supporting organization Exit Criteria 2 Identified supporting organization Exit Criteria 3 Identified redundant Capabilities Exit Criteria 3 Identified redundant Capabilities Sprint 1 3 Weeks Duration Focus on Work Item 1 Sprint 1 3 Weeks Duration Focus on Work Item 1 Value Add Identified Possible Cost Savings Value Add Identified Possible Cost Savings

SUPPORT THE WARFIGHTER Example 9 Stakeholders – Assignment: 1.Review add/modify Work Items, objectives, criteria, and questions 2.Set Priorities on the Work Items 3.Identify SMEs to participate in the Sprint Teams and work the Work Items 4.Identify Reviewers for each Sprint Team 5. ?What else do we want to get accomplished?

SUPPORT THE WARFIGHTER MPE RA Proposed Timeline UNCLASSIFIED/FOUO POST-SPRINT Dec 2014 Jan 2015Feb 2015 Mar 2015 Complete In Progress / On Track Behind / other problems Kick Off Meeting Set up “Sprints” – Publish Start-up Information Launch MPE RA with Stakeholders Sprint 1 – Capabilities Review Publish “As-Is” MPE RA Stakeholder Review Compile the MPE Architecture Sprint 4 – Initial Roadmap Sprint 3 - Connectivity Sprint 2 – Meta Data – Data Model Stakeholder Review AGILE BUILD-SPRINTS Simple Kanban Board Stakeholder Review