1. Introductory Remarks

2. Beth McInerny, LLC Background Project Coordination Skills Similar Projects Contact Information Agenda: Remarks

3. Project Management Agenda: Remarks

4. Project Assumptions and Risk Assumptions The Task Force members will conduct User Acceptance Testing prior to rolling application to pilot offices. Pilot counties will include those with the strongest technology fit to the new application allowing for shorter implementation times Project Plan tasks and milestone will change depending on service commitment of consultants and application vendor Risks Technology requirements may be a significant expense to some counties vs. others. Countywide standards may cause hardship on counties that currently differ dramatically from those standards. Considering the scope and size of this project, this project is scheduled very aggressively. With a fixed time line, the project’s specifications and budget will need to be closely monitored. Specifications could include, the duration of pilot testing-- currently set to six months, functionality developed for the pilot, the number of application vendors that are reviewed, etc. Budget may need to be modified to include additional resources to complete the initiative on time. This project will be managed on an aggressive implementation timetable. This may cause functionality or pilot times to be reduced. This could result in issues such as: bugs not identified because of a reduced pilot timeframe, reduced functionality in the application to be tested. Agenda: Project Time Line

5. Time Line Details Agenda: Project Time Line

6. RFP’s Project Time Line with LOE and Costs Agenda: RFP for Next Level

7. RFP for Next Level Scenario One = Two RFPs First RFP sent out immediately covering: –Survey of counties and recommendations Both technical and business analysis skills If successfully completed, then move to Second RFP technical architecture work for pilot locations (design) This frees you from the time commitment of going through another RFP round. Gives you better traction because this team knows what is expected already. Design should come from a party that is not going to fit MN into the format of their last project Second RFP sent out when standards are in place or give confidence –Vendor Applications Provides a second, independent eye to initial technology / design work. Performs application customization and installation of pilots Provide mentoring and best practice learnings Legal investigation and recommendations are also needed. This can be served best using an internal team. Agenda: RFP for Next Level

8. RFP Scenario Two = Three RFPs First RFP sent out immediately covering: Survey of counties and recommendations Both technical and business analysis skills Second RFP sent out immediately covering: In depth technical knowledge to do architecture and infrastructure design Build database, security, accessibility,,, Provide on-going technical support for pilot Third RFP sent out when standards are in place or are close enough to give confidence that application vendor can be looked at. Provides a second, independent eye to initial technology / design work. Performs application customization and installation of pilots Provide mentoring and best practice learnings Agenda: RFP for Next Level

9. RFP RFP Detail

10. Expense Form New form for expenses billed to ERER On web site early next week Agenda: Expense Forms / Payment

11. Interns Eileen Roberts looking at skills to see if there is interest in her group Agenda: Opportunity for Interns

12. Pilot Counties Discussion Format Pilot Choice Criteria Agenda: Consideration of Parameters for Pilot

13. Task Force Meeting Schedule Agenda: Review Current Schedule