eGovernment Program Proof of Concept Model Approach May 2003

1. eGovernment Program Proof of Concept Model Approach May 2003

2. Agenda I. Overview II. Approach III. Team

3. Overview • A proof of concept prototype will visually illustrate how eGovernment can be implemented at USDA to change the way we do business. • Showcases the vision set forth in the eGovernment strategic plan and its respective initiatives • Articulates how net-centric technology will be used to enhance program and service delivery and enhance internal operations • Fosters discussion about changing business processes and the positive impacts of those changes • Helps program managers understand how technology can enhance their business • Serves as a marketing and communication tool • Employees see the Department making progress and begin to develop a new mindset about the current operational paradigm • A consistent message can be delivered to business partners about how USDA plans to change • Executive leadership can use as a consistent message to constituents about the strategic direction of the Department

4. Goals of Proof of Concept • The proof of concept will be comprised of three main user portals that stem from the main usda.gov portal. • USDA.gov Portal • A new vision of usda.gov showing the site as a front-door to all USDA programs, services, and information • Agricultural Producer Portal • A personalized information and customer services portal where farmers will have one-stop access to appropriate services (service center customer statements), relevant information (latest research, and news such as livestock commodity pricing), and agency applications (eLDP, conservation tools, etc.). • Partner Portal • A personalized information and services portal that provides USDA business partners access to various services. • Employee Portal • Department-wide Intranet portal pointing to internal resources and integrating advanced information retrieval, collaboration, etc.

5. Business Scenarios

6. Business Scenarios

7. High Level Prototype Site Map

8. Agenda I. Overview II. Approach III. Team

9. USDA eGovernment Prototype Detail Planning April 2003 May 2003 June 2003 Project Management • Testing • Create System Test plan • Create System Test Scripts • Execute System Test • Business Scenario Development • Identify and Confirm Scenario Leads • Conduct Requirements Working Sessions • Create Site Map, Content, Paper-based Storyboards • Create Demo Scripts • User Interface Standard • Create Common Look and Feel Templates • Create Custom Graphical Images • Create Style Guide • Technical Architecture • Plan for Production Environment • Define Content Management Plan • Create Operations Plan • Create Coding Guidelines • Development • Establish Development Environment • Build HTML/ASP pages • Perform Unit Testing

10. Timeline • The estimated timeline for completing the Prototype is 11 weeks

11. Agenda I. Overview II. Approach III. Team

12. Team Roles and Responsibilities • The prototype implementation team includes project management, a technical implementation team, existing contractors to develop or augment existing data management projects, and business subject matter experts from agencies Recommended Implementation Team Team Roles • The implementation team would be managed by the eGovernment Program Management Office • The implementation team is responsible for designing templates, coding HTML and scripts, and setting up the necessary technical architecture • Existing contractors are responsible for developing scenarios based on projects they are already working on • The Business SMEs, USDA SMEs, and Industry SMEs are responsible for working to define scenarios, define process flows, write content, and confirm final output meets the scenario’s specifications eGovernment PMO ImplementationTeam Existingcontractors forcertain scenarios Business SME Lead UI Designer USDA SMEs Graphic Artist Industry SMEs HTML/Script Developers