U.S. IOOS® Requirements Marketplace? March 8, 2013

Transcript:U.S. IOOS® Requirements Marketplace? March 8, 2013:
U.S. IOOS® Requirements Marketplace? March 8, 2013 Carl Gouldman, Debra Hernandez 1 Problem? We need to collect and manage IOOS enterprise-wide requirements across the regions, federal agencies and the IOOS program office? Requirements = needs identified through user surveys, stakeholder assessments, interviews, etc. IOOS Summit Recommendation for engagement, coordination, integration, telling the story, & fighting for $s …and how do this without creating a tedious, cumbersome, churning, & cost-prohibitive process? 2 What? Why? How? Questions of the Day Regions exchange best practices & lessons learned from regions’ requirements processes? Discussion: Is this a mutual need we should pursue? Do we want to work together to develop a requirements marketplace? Next Steps? 3 From U.S. IOOS Summit “The job of the U.S. IOOS Program Office, the Regional Associations, and [the IOOS Association] is to focus on a viable process for collecting, prioritizing, and assessing progress against regional user requirements and integrate them with national and global requirements” 4 Create a “match.com” for IOOS Requirements… = ID / Collect / Sort / Prioritize needs = ID / Find / Connect … to Solutions to meet those needs Vision Smartphone with App for entering IOOS needs and receiving IOOS solutions Requirements In IOOS Solutions ID’d Solutions Realized Platform to collect, analyze, and allocate requirements Submission of requirements Allocation of identified requirements for development PLATFORM REQUIREMENTS PERSONNEL/ANALYSIS Developing Concepts Proposal In the short term, develop a mechanism for collecting requirements from any stakeholder Note: Collecting requirements from stakeholders for the U.S. IOOS enterprise is a huge undertaking Variety and number of provider organizations Variety and number of users Dynamic nature of needs Differing priorities among users and provider organizations Expectation Management is a must! 7 Assumptions for a short-term solution to requirements collection Open forum for all stakeholders to submit requirements Low bar for entry so submission process is not an obstacle to participation Requirements are stored until needed for development or analytic efforts Design must accommodate collection of all information needed to process a requirement Design must accommodate the different types of requirements Design must allow data mining by both Regions and IOOS program office 8 What would this ‘Requirements Marketplace’ look like? Notional Information Requested from Stakeholders during Collections Phase (not complete) Description of Requirement First Name Last Name E-mail Address Phone Number Organization Name Organization Type: (have user check all applicable categories. Examples below) Program Office IOOS Association Data collector Data