1 / 9

ITSPB RETREAT March 17, 2009

ITSPB RETREAT March 17, 2009. Enterprise Architecture (EA). EA Team Members. EA Program Management Office Team: Rachel Felver Lisa Jenkins – Acting Chief Architect Kevin Kirby – Data Architect Jos é Labiosa David Prompovitch – Team Lead Eric Roberts Larry Watkins

dawson
Télécharger la présentation

ITSPB RETREAT March 17, 2009

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. ITSPB RETREAT March 17, 2009 Enterprise Architecture (EA)

  2. EA Team Members EA Program Management Office Team: • Rachel Felver • Lisa Jenkins – Acting Chief Architect • Kevin Kirby – Data Architect • José Labiosa • David Prompovitch – Team Lead • Eric Roberts • Larry Watkins The EA PMO Team also draws upon the resources of these EA Team members: • David Michals • Brand Niemann • Rahsaan Tabb • Jody Zeugner “Don’t forget me!”

  3. 2009 EA Implementation Logic Model 4 1 EA Development & Compliance 2 Outreach to Stakeholders & Governing Bodies 6 OMB Submittals Support Environmental/ Investment Decisions 5 Performance & Value Measurement 3 Other Ad hoc Efforts

  4. Team Lead Dave’s Responsibilities • EA Program Management • Maintain EA PMO budget • Tool implementation and application development for new Troux tool • Develop ART “road show” • Identify business questions and answers • EA Governance

  5. Rachel’s Responsibilities • Main point of contact for OMB EA Self-Assessment • Populating self-assessment matrix • Generating correspondence • Tracking progress • EA/CPIC Liaison • Segment Architecture • Administrative • MISD File Structure • Milestone Tracking • Restructure of I Drive

  6. Eric’s Responsibilities • EA Training Development • Case study based training on architecture methods. Uses Federal Segment Architecture Methodology and EPA business problems. June 2009, modular, two weeks. • EA Policy and Governance Procedure Revision • These documents are three years old. What is the future of EA governance at EPA? • Monthly Enterprise Architecture Working Group (EAWG) meeting preparation, follow-up • Segment/Solution Architecture Support • Maintain EA Intranet Site. Implement EA collaboration site. • Troux eaGov User Representative

  7. José’s Responsibilities • Address OMB requirement for performance milestones • Value measurement and performance assessment • Segment/Business Layer Development and Support • Integration of EPA Businesses and OTOP Strategic Planning Processes (As Needed) • EA Success Stories • Alternate COTR for Application Architecture Task Order

  8. Larry’s Responsibilities • COTR for EA Task Order • MISD Budget • Business Layer Development/Support • System Administrator for new Troux tool • Includes hosting • Risk Management Specialist

  9. EA Calendar – Upcoming Activities and Deliverables • March 31, 2009 • EA Success Story • May 29, 2009 • Segment Template Update • EA Self Assessment Completion Artifacts due to OMB • Transition Strategy and Sequencing Plan • Target Architecture • Segment Prioritization process • June 2009 • EA Training • EA Success Story • August 29, 2009 • Segment Template Update • EA Self Assessment Use Artifacts due to OMB • EA Governance Plan • EA Communications Plan

More Related