Project Inventory: Food Oasis

[Olivia-Chiong]

Overview

We need to make an inventory for this project so we understand what assistance this project needs and what examples of effective processes or practices this team might have.

Action Items

• Check the project for the items on the check list below
• Mark off the items when you find it and include the links where available
• Provide comments on what you find in the issue and also highlight when they have a great example so we can use it for the organization

Product

• Readme This needs to be updated
• Wiki
• Google Drive Google Drive
• GitHub Repository Food Oasis v2
  • Project Board Launch v2
  • Issue TemplatesList of New Issue Templates
• Slack Channel #fola
• 1Password
• Project Email
  • [email protected]
  • [email protected] (You will need this for setting up some applications like MIro that use rate limiting. Do not send emails using this address)
• Team Roster Roster
• Product One Sheet Issue for One Sheet
• Recruitment Form
• OKRs and WBS
• Roadmap Issue for Roadmap
• Storypoints - Issue Labels
• Meeting Minutes Template

Marketing

• Marketing Objectives
  • Create new issue using this template: Define Marketing Objectives for Food Oasis
  • Copy the link for the issue into the parentheses above
• Collect Marketing Assets
  • Create new issue using this template: Collect Marketing Assets for Food Oasis
  • Copy the link for the issue into the parentheses above

UI/UX

• Figma
• Miro
• Presentation Deck
• Competitive Analysis
• User Persona/Journeys
• Communication Style Guide (including documents, spreadsheets and forms)
• User Research Guide/Template
• Wireframes Template
• Website analytics software setup

Resources/Instructions

REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here.

[ktjnyc]

Linked Github, Github project board and slack channel.

[ktjnyc]

Progress: Updated links for Figma, Google Drive, Team Roster
Blocks: So many documents to sift through!
Availability: variable
ETA: Can make some additional progress by next meeting

[ktjnyc]

Progress: Linked in user stories and updated project email
Blocks: So many documents to sift through!
Availability: variable
ETA: Can make some additional progress by next meeting

[ktjnyc]

Progress: Linked in issues for marketing assets and objectives, roadmap and one sheet. Story point labels set up but many conflicting so we need to clean up and simplify.
Blocks: So many documents to sift through!
Availability: variable
ETA: Can make some additional progress by next meeting

[ktjnyc]

Progress: Created an issue on the Food Oasis to have the UX/IU team identify the assets. We are working on the One Sheet and some of the others are in progress too so we don't have current versions yet.
Blocks: So many documents to sift through!
Availability: variable
ETA: Can make some additional progress by next meeting

[wanderingspoon]

I have a question about the term "user stories" as applied and linked above.

They currently read more like user roles than discrete units of functions/features for dev team's work.

Or perhaps I'm looking at the wrong document? Could someone please clarify? Thanks!

Otherwise, I recommend that a separate issue is required for creating user stories based on issues-in-progress and prioritized backlog. I could help with those. Which can then go through the Fibonacci process.

[ktjnyc]

@wanderingspoon that should have been unlinked - John mentioned that he had just written that and posted it so we had something. I've searched the rest of the Google drive and haven't found anything else. We have an issue on the Food Oasis repo to review and update the personas . We can create a separate one for user stories as well.

[gigicobos]

@Olivia-Chiong we'll discuss this tonight with the FOLA team to continue with this issue. We've added a link to our board as a reference.