Program Design
- Phase 1 - Planning
- Phase 2 - Outreach and Review
- Phase 3 - Execution
- Phase 4 - Evaluation
- Suggested Timeline
Phase 1 - Planning
The planning phase lays the groundwork for a successful project. During this phase, OSPO staff should establish the focus and goals of the program, determine success metrics, create a communications and outreach plan, and ensure all stakeholders are informed and prepared.
Financial planning
Determine the overall budget for the program, including awards, OSPO staff time, travel (e.g. conference presentations), technology, event planning, and overhead. Determine the total amount available for FOSSProF awards and the financial structure of the program. Answer questions such as: What is the maximum amount of funding available to each applicant? What are the limitations on what will be funded (e.g. no tuition reimbursement)?
Program focus
What is the focus or theme of this iteration of FOSSProF? What is in and out of scope? Potential themes include: OS roles: creators, maintainers, contributors OS themes: security, sustainability, documentation, diversity, reproducibility, etc. Career stage: Early career students or postdocs vs senior researchers and teaching faculty
Goals and objectives (specific, measurable, achievable, relevant, and time-bound)
Identify the specific end goals of this iteration of FOSSProF. Consider: How will this funding help OS projects on campus? How will funded projects be able to define, increase, and measure the impact of FOSSProF funding; for example, by increasing adoption, building community, citation growth, etc. How will this iteration of FOSSProF advance the mission of the OSPO, the OSPO's broader organizational unit, the University, etc. How will the OSPO define and measure success? What questions will FOSSProF allow the OSPO to answer? What is the definition of success for the FOSSProF initiative?
Schedule planning
Review playbook to identify key milestones and dependencies. Meet with departments whose work intersects with FOSSProF (e.g. finance, HR) to share project activities that require their input or resources and determine reasonable time estimates. Map out approval process and timelines for senior leadership. Build a draft schedule based on playbook activities and partner department estimates. A suggested timeline based on a 24-month cycle is provided below. Share timeline with stakeholders for feedback and revise as necessary.
Outreach and communications
Identify the target audience for outreach. Contacts can be gathered from: Individuals, departments, lists, groups. Previous grantees. Data mining shared research platforms such as code repositories and research information datasets. University colleagues in the library (subject experts), technology transfer, and research administration. List or catalog of campus open source projects. Share schedule and plan with senior leadership, finance, and external affairs (grants). Identify and invite reviewers. Mix of division colleagues, subject matter experts, and/or previous grantees. Provide enough detail about time commitment and timeline so invitees can make an informed decision.
Documentation Write or review existing
Create or update the following program documentation: Funding announcement \- web, email, shareable PDF. Proposal guidelines. Application webform. Review invitation and rubric. Review webform. Award letter, Terms and conditions, financial information. Final report template. Note: in this and the following phases, documents for which a template is provided are bolded.
Phase 2 - Outreach and Review
The Outreach and Review phase includes all activities from the initial funding announcement to the final award decisions. The core goals of this phase are to effectively promote the opportunity, facilitate a fair and thorough review process, and select projects that align with the program’s goals.
Announcement distribution & applicant communication
Post proposal guidelines and application form. Distribute funding announcement. Email distribution channels. Social media. OSPO website, Broader organizational unit website/blog. Schedule and hold open houses for Q\&A. Schedule 1:1 meetings as requested.
Proposal intake & review preparation
Add all proposals to shared folder. Naming format: Date Submitted\_PI Name\_Proposal Short Name. Create a proposal register with Contact/PI name, title/summary/link to full proposal, budget request, assistance requested (e.g. staff, travel, hardware), notes, and checklist for next steps. Check proposal for completeness, return to contact/PI with any questions, clarifications, or requested revisions. OSPO Staff perform initial review, hold back from reviewers any proposals that do not fit the funding call. Determine final list of proposals to share with reviewers.
Reviewer guidance
Create reviewer instructions/rubric based on the elements in the program proposal and overall program goals and objectives. For example: Proposal element \- Problem Statement: Please provide a clear and concise description of the problem or need that your project is addressing or the research topic you are considering. Review rubric \- Is the problem well-defined and relevant to the open source community at Hopkins? To keep the review process simple, use a mix of Likert scale answers (1-5, strongly agree-strongly disagree) and free text.
Review process
Create PDF versions of all proposals. Depending on the number of proposals, assign whole group or batches to reviewers. Hold reviewer kickoff meeting, share instructions/rubric and review web form. Collect and compile reviewer feedback and scores. Meet with reviewers for feedback session, ask for any clarifications, additional thoughts.
Decision making
Analyze review committee recommendations. Think about total budget available, schools/divisions/departments represented, project relevance to FOSSProF goals. Make funding recommendation to senior leadership. Finalize funding decisions.
Notification
Share with successful applicants Award letter \- requesting acceptance of award. Terms & conditions. Final report template. Share with finance. Awardee list with PI and total amount awarded. Budget breakdown for each project with expenses by general line item (e.g. postdocs, faculty, hardware). Share with unsuccessful applicants.
Outreach and communications
Share list of funded projects with: OSPO website, Broader organizational unit website/blog. Social media. Suggest for University PR, newsletters, etc. OSPO Advisors. Organizational unit announcement lists.
Financial planning
Finance to create billing codes for all projects. Share financial information with projects: Approved budget with line items. Cost center / billing code. Process for requesting budget reallocations. If projects are student-led, confirm ability to hire, submit reimbursements, etc.
Phase 3 - Execution
The Execution phase focuses on managing project grantees throughout their project lifecycle, including funding disbursements, tracking project progress, documenting project outcomes and impact, and holding a summative event to showcase awardees’ work.
Outreach and communications
Create new Slack, Teams, or other real-time chat channel for FOSSProF iteration. Create email list with all contacts and PIs.
Project kickoff
Meet with all awardees to go through award letters, answer any questions, confirm reporting schedule, establish communication standards (e.g. Slack for chit chat, email for official communications). Presentation from finance, especially for new PIs \- what the codes are, how to use them, who to contact for help.
Reporting
Request bi-monthly updates from each project, include schedule in award letter. Send email reminders for regular status reports. Share status reports with program leadership via shared space such as a wiki or shared Team or Drive folder. Share final report template. Send email reminders for final reports. Reminder 60 and 30 days out to submit final reports. Collect final reports.
Financial planning
Review and approve (or not) budget reallocation requests. Review request. Confirm approval with Program Director. Respond to PI. Update budget worksheet. End of project budget reminders. Reminder 60 and 30 days out to submit final budget requests. Collect final budget reports.
Summative Event
Determine format of event \- in person, online, or hybrid? Schedule event. Develop event program, including a mix of: Presentations from grantees. Talks or conversations with senior leadership, open-source advocates, and/or invited outside guests. Ample time for community building, networking, and information conversations among attendees. Develop and execute outreach campaign for event. Invitation template. Manage event logistics: Identify and book space or online platform. If in person, identify and book catering. If in person, identify and book technical support. Determine collateral needs, e.g. printed agendas, information about funded projects, or promotional materials for OSPO services. Hold event.
Phase 4 - Evaluation
The purpose of the evaluation phase is to assess the overall success of the program against the metrics established in Phase 1. During this phase, the program team should gather feedback from program participants, analyze program impact, and document lessons learned.
Metrics
Retrospectives. Create/review feedback questions for awardees. Hold "exit interviews" for each project to discuss final reports, ask feedback questions, etc. Hold retrospective meeting with finance and external affairs. Hold retrospective meeting with OSPO staff and FOSSProF team. Collate metrics, analyze, and assess. Suggested metrics/questions to answer: Types of activities proposed in all submitted projects. Were resource gaps centered around specific activities? Did certain types of activities result in improved sustainability or additional impact? Funding amounts requested across all submitted projects. What was the range of funding requested? Where did most proposals fall across this range? Was there a connection between funding requested and resulting impact? Success rate of funded projects. To what extent did each project achieve the goals laid out in their proposals? Did the most "successful" projects have any common characteristics? What might it look like to target projects with these characteristics in a second funding round? Common roadblocks or challenges. Were similar obstacles encountered across projects? How did different projects overcome obstacles? What can we learn from their experiences? Impact of FOSSProF funding on community engagement. For projects that wanted to use FOSSProF funding to improve engagement, what results did they see and how are they measuring/identifying that improvement? Long-term sustainability of projects and/or FOSSProF-funded activities. Do projects feel FOSSProF funding improved their project's prospects for long-term sustainability? If so, how are they measuring that sentiment? Are there specific activities they would like to continue? What could the OSPO do to continue to support projects after the funding period? Identify insights, conclusions.
Reporting
Receive and review final reports from awardees. Create final report for FOSSProF iteration (internal or external if outside funding).
Outreach and Communications
Share final results of project with: OSPO website, Broader organizational unit website/blog. Social media. Suggest for University PR, newsletters, etc. OSPO Advisors. Organizational unit announcement lists.
Suggested Timeline
From initial planning through final evaluation, the full FOSSProF cycle fits well into a 24 month period, but can be condensed if needed. To ease student hiring, it is recommended to align the timeline with the academic calendar. It is important to allow sufficient time for each phase; a rushed process may not allow projects time to complete their goals and objectives or recover from unexpected roadblocks.
Sample Schedule - one iteration aligned to the academic calendar
Year 1 Fall | Year 1 Spring | Year 1 Summer | Year 2 Fall | Year 2 Spring | Year 2 Summer |
---|---|---|---|---|---|
Phase 1 Planning | Phase 2 Outreach and Review | Phase 3 Execution | Phase 3 Execution | Phase 3 Execution | Phase 4 Evaluation |
Sample Schedule - successive iterations aligned to the academic calendar
Year 1 Fall | Year 1 Spring | Year 1 Summer | Year 2 Fall | Year 2 Spring | Year 2 Summer | Year 3 Fall | Year 3 Spring |
---|---|---|---|---|---|---|---|
Round 1 Phase 1 Planning | Round 1 Phase 2 Outreach and Review | Round 1 Phase 3 Execution | Round 1 Phase 3 Execution | Round 1 Phase 3 Execution | Round 1 Phase 4 Evaluation | ||
Round 2 Phase 1 Planning | Round 2 Phase 2 Outreach and Review | Round 2 Phase 3 Execution | Round 2 Phase 3 Execution | Round 2 Phase 3 Execution | |||
Round 3 Phase 1 Planning | Round 3 Phase 4 Outreach and Review |