Skip to content

Latest commit

 

History

History
58 lines (47 loc) · 3.94 KB

process_research_improvement_proposal.md

File metadata and controls

58 lines (47 loc) · 3.94 KB
Raw

SCRF: Process - Research Improvement Proposal

Introduction

SCRF's culture is based on the open-source software community. Anyone can suggest an improvement or a new process, but it has to fit in the existing framework. Project Proposals are the first step of our Research Improvement Proposal (RIP) process. This is how we decide whether a suggested improvement provides a benefit, whether that benefit is worth the resources spent, and whether or not it makes sense given other projects already in process.

Before you start a new project plan, check the Research Team board to determine whether something similar doesn't already exist. If you find something close, contact the author or add a comment to the ticket to see if there's a way to merge your ideas into one project.

When you're ready, create a new ticket, and create a new Project Plan from the template below and paste a link to it into the ticket.

Reach out to one of the SCRF team members on the chat and try to arrange some time to discuss the idea during our weekly calls.

Here's a link to the Project Plan Template.

Method

Create a copy of the Project Plan Template, fill out the relevant fields and then move it to the Project Proposals directory. Create an issue in GitHub describing the proposal and link to your google doc.

  1. Fill out the form
  2. Talk about with Ops
  3. Update the plan based on feedback
  4. Be prepared to create Proof of Concept (POC) if the project is creating a specific deliverable. If the proposal outlines a new type of work then a workflow document will be required.
  5. Include plans to present the Proposal to the greater team

Workflow for a New Proposal

  1. Pitch to the Team
    1. Create an 'elevator pitch' - a quick distillation of your idea.
    2. Give a member of the Ops team your elevator pitch
      1. They'll determine whether the project aligns with SCRF goals and scope
    3. Check in the Research Team pipeline to determine whether or not a pre-existing project already encompasses your suggestion
      1. If an existing project could encompass the suggestion, reach out to the creator in chat, to see if you could incorporate your ideas into theirs.
      2. If an existing project does not encompass the suggestion, create a new issue with a link to your project plan (adapted from the Project Plan Template and a brief description of the project in the issue.
  2. Create a Proposal
    1. Fill in a Project Plan Template
      1. Consider resources needed, potential scope, etc.
    2. Document should describe how many people, what resources, and how much time in detail. Consider the scope of the project when deciding how much detail to add.
    3. Develop goals and analytics.
      1. How does this project define success?
      2. How is that success tracked?
    4. Develop a timeline.
      1. Broken down by weeks
        1. Week 1:
        2. Week 2:
        3. Etc.
    5. Outline how the project would be tracked in Github
    6. (If External, then create a budget)
    7. Flag Ops for a conversation about the project.
  3. Create a proof of concept/workflow document
    1. Discuss with Ops team
    2. Incorporate feedback
  4. Create Project Presentation for the group.
    1. Create a 10-minute presentation
      1. This should detail the project and outline the steps and resources needed to implement it.
    2. Schedule a time during SCRF's weekly Wednesday meetings to present your project.
    3. Present the project.
      1. Tally suggestions and concerns raised by the group.
    4. Schedule a follow-up meeting with SCRF Ops team