Skip to content

Food Oasis Documentation Assessment #1361

Open
@staceyrebekahscott

Description

@staceyrebekahscott

Overview

Update: 10/18/22

Changing this into a Documentation Epic issue.

Other tasks for Documentation:

  • FAQ- to answer questions on process/ procedure
  • Role Descriptions (generally)
  • Role Descriptions (specific- what tasks do you do that you would need to train someone on if you left the project)
  • Transition plan- general checklist for what to train someone on if you were leaving the project.
  • Github pages- as a replacement for References/ Wiki and a go to for an overview of the project (maybe a replacement for the Projects page on the HfLA website)
  • Create a Bio page for new team members to add a brief bio of themselves. (Maybe something we can add to the main FOLA website at some point.
  • List of all software licensing and domain registration used for FOLA. This will be needed for the transition from Code for America to Civic Tech Structure.

Issue on Project Management Board Project Inventory: Food Oasis

#1155 Issue Audit- Folding the scope of this issue into Role Descriptions.

Original Issue Overview/ Scope:
Message from Mark Frischmuth at Democracy Lab: The team at DemocracyLab is performing a documentation review for all of the Impact Sprints projects. As part of this process, we'll prepare a user journey map for each project to help identify opportunities for documentation improvement.

We know that many projects are recruiting new volunteers through DemocracyLab. We'd like to know what other entry points volunteers have to participating in your projects (e.g. Meetup, social media, etc.) and where those volunteers are directed to learn more. This will help us make sound recommendations that are relevant to your project.

Documentation Review Plan

  • We'll start with a cursory documentation review of each project to identify patterns of documentation structure.
  • In parallel, we'll then:
    • Recommend a model structure for Impact Sprints projects
    • Perform a project-specific gap analysis
  • We'll then present to each project recommendations for documentation improvement and additions
  • We might then consider following up with:
    • Conduct 30 minute interviews with a series of volunteers, project managers, and future project owners (people who will take ownership once the PMs transition off)
    • Analyze and document themes and insights from interviews
    • Present recommendations for next steps

Action Items

Metadata

Metadata

Assignees

No one assigned

    Labels

    DocumentationImprovements or additions to documentationEpicIssue that defines a sub-project and has other smaller issues as dependencies.Feature: Design SystemStandards, documentation and guide of design assets and componentsImpact Sprints 2022Issues to be addressed as part of the Code for America Impact Sprints initiative- Summer 2022Interface: nonePM: OperationsRole: Product Managementsize: 3ptThe lift to complete this user story 4-8hrs

    Type

    No type

    Projects

    Status

    New Issue Approval

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions