MEETING RECORDING:

tl;dv - app

⚠️ ACTION ITEMS:

• Team, while Project Managers work towards finalizing our Project Charter — we could use your input and assistance to refine the sections on the template (in FigJam) so it best reflects what we learned from the client discussions. (targeting by next leads meeting)
• Strategy Team — you have the greenlight to define what a MVP looks like and Evan's trust in the team's expertise; you also have a team eager to lean-in, be a SME (subject matter expert), and support! (target goal: ?)
• Address any other project updates the team would like to further discuss (including any points we didn't hit on from today's leads meeting)
• Get well versed with resources and links client shared with us and communicate these resources with apprentices as well to bring them along
• Once we have everyone’s scheduled meetings, we will have an idea when we will be facilitating demos/retro sprints.
• Proposing official project start date: Oct 16, 2023
• Proposing project end date: Dec 1, 2023 (Dec 8, 2023 extension if needed)

PROJECT UPDATES:

NOTES OF OCT 12, 2023 LEADS MEET:

• How are we feeling?

  • Marc Brackett, PhD, Mood Meter [team-building activity]

  The Colors of Our Emotions

  • Food Distro → Everyone has a story behind the food waste.
    • Globally, 1.4 billion, tons of food are waste. Let alone, America wastes more than that.
      • 219 lbs of waste per person in the America.
    • Evan wants to model the platform after 412 Food Rescue.
      • “How do we take something so localized and take it nationalized?”
        • Empathy is throughout the project because this is personal.

• Project Charter → click link

  • Serves as a reference-outline for project planning.
  • Food for thought
    • Budget → At every hour and resource we spend, we want to allocate time accordingly to differentiate tasks and accomplish it.
    • Project Risk
      • Leads were onboard on August. Apprentices were interviewed on September. We had a new client. And now the project scope has changed. So is everyone’s commitments. What will our project scope look like for the rest of this fall. Because of all, we have to be transparent with Evan.
      • Potential burnout. Commitment will still be there, but quality wouldn’t be the same
    • Stakeholders → Government (?)
    • Project Timeline
      • Research heavy
      • Uncertainty if prototyping and testing will be made on time due to building research and user flow.
    • MVP
      • It can be a bare bone version, but with lower scope
    • Design
      • Wireframing & Prototyping can be done quickly, however, we need to know who are users are and how impactful the product will be.

• Follow up (look above for project items and below for action items)

  • Jennifer’s food for thought: in the past, having weekly demos & retros were beneficial
    • When will we get together as whole team vs individual.
    • Liaisons → do we want have same liaisons for whole 8 weeks, or have them rotate each week.
  • Lynn’s food for thought: if we do bi-weekly demos/retro plannings, we need to consistently communicate.
  • Jennifer’s food for thought: shadowers
    • Shadowers can join, however, they can keep questions till the end of the meeting, because Internal members go first
  • All leads food for thought:
    • Leads Meeting for leads at this time.
    • Use Slack Phase 2 Team Channel for team communication (all leads + apprentices)