Mr. Dennis E. Wisnosky is the Chief Architect and Chief Technical Officer (CTO) of the Department of Defense (DOD) Business Mission Area within the office of the Deputy Under Secretary of Defense for Business Transformation. As Chief Architect and CTO, Mr. Wisnosky is responsible for providing expert guidance and oversight in the design, development, and modification of the federated architectures supporting the Department's Business Mission Area.

1. Welcome! Transformation and Innovation October 30, 2007 Breakfast Briefing “ Agile Adaptive Architectures”

9. Enterprise Business Transformation Dennis E. Wisnosky BMA – CTO, Chief Architect Overcoming Momentum! “ Agile Adaptive Architectures”

10. Reach of the Business Mission Area This includes Iraq! "The Secretary of Defense is responsible for a half-trillion dollar enterprise that is roughly an order of magnitude larger than any commercial corporation that has ever existed. DoD estimates that business support activities—the Defense Agencies and the business support operations within the Military Departments—comprise 53% of the DoD enterprise.”

12. The Business Mission Area (BMA) Within the BMA Paul A. Brinkley Deputy Under Secretary of Defense for Business Transformation DoD Mission Areas - Top Down View War Fighting Mission Area Business Mission Area Intelligence Mission Area Enterprise Information Environment Mission Area

13. “ We are focused on change and driven by our responsibility and accountability to the men and women of our Armed Forces who protect this great nation.” DEPUTY SECRETARY OF DEFENSE GORDON R. ENGLAND SEPTEMBER 16, 2005 The BTA is the primary change agent for the BMA

14. How the BTA Works - Goals to Capabilities Enterprise Architecture Process Architecture (OVs) Information Architecture (SVs) Solution Architecture ( Tiered Accountability/ Federation) Technical Architecture (TVs) Goals, Objectives, and Priorities Enterprise Transition Plan Business Mission Area OSD Goals Component Goals IRB DBSMC Capabilities Delivered to the Warfighter BTA/DBSAE builds and delivers OSD Systems DISA provides Infrastructure BTA builds architecture and transition plan the Business Transformation Agency (BTA)

16. Federated Architectures Not Integrated Architectures Capabilities and Systems Program System Functions { } Federated Enterprise Architecture We are Underway! Component EAs Program Architectures Typical Mission Area Enterprise Architecture Content Enterprise Info. Exchange Reqs Enterprise Operational Activities Enterprise Business Rules Enterprise Processes Enterprise Structural Business Rules Enterprise Data (Objects, Entities and Attributes) Enterprise System Functions Enterprise Initiatives Enterprise Level Governance Operational View Federation Implemented Capabilities and Systems Army Operational Activities Navy Operational Activities Air Force Operational Activities Other Component Operational Activities Army Enterprise Processes Navy Enterprise Processes Air Force Enterprise Processes Other Component Enterprise Processes Army Logical Data Structure Navy Logical Data Structure Air Force Logical Data Structure Other Component Logical Data Structure Army Initiatives and System Functions Navy Initiatives and System Functions Air Force Initiatives and System Functions Other Component Initiatives and System Functions Program Operational Activities E I E S e r v i c e s f o r R e g i s t e r i n g , D i s c o v e r i n g & U t i l i z i n g A r c h i t e c t u r e D a t a E I E S e r v i c e s f o r R e g i s t e r i n g , D i s c o v e r i n g & U t i l i z i n g A r c h i t e c t u r e D a t a { } Implemented Capabilities and Systems Program Processes { } Implemented Capabilities and Systems Program Data { } Implemented Systems View Federation Systems View Federation

19. Software Project Success Depends Upon Its Size Source: Capers Jones 8% 7% 6% 3% 1% 89% 80% 60% 23% 15% 2% 8% 17% 35% 36% 1% 5% 17% 39% 48% 10 100 1,000 10,000 100,000 Projects Completed Early Project Completed On Time Projects Completed Late Projects Cancelled Project Function Points

21. Agile Adaptive Architectures Adapted from: Rouse, W.B. (2003). Engineering complex systems: Implications for research in systems engineering. IEEE Transactions on Systems, Man, and Cybernetics – Part C , 33 (2), 154-156. Self Organization Organizational Design Design Heterarchy Hierarchy Network Personal Commitments Contracts Relationships Agility Efficiency Focus Capability Outcomes Processes Measurement Incentives & Inhibitions Command & Control Methods Leadership Management Roles Agile Adaptive Architectures Enforce: Traditional Architectures Enforce:

22. “ Services Delivering Capabilities, not Systems Named by Marketing Departments” Nope! Yep! This is Happening Now!

25. Back in My Home Town F

26. Questions???