Stand up Records - Anujithaaa/DECO3500-Team25-NutriCart GitHub Wiki

Stand-up Records

Internal team stand-ups and meetings. Each entry records state, outcomes and next steps.

How this page was made. We did not post records weekly during Weeks 3–10. On 13 October 2026 we backfilled them from studio notes, our OneDrive files and team chat. Backfilled entries are marked (backfilled). Where a detail could not be confirmed it says [confirm]. Entries from Week 11 onwards are written on the day.

Usual meeting: Mondays 9:30 [confirm], plus straight after studio when needed.

Week 3 (10–14 Aug) (backfilled)

  • State: Team formed. Studio review of possible domains: healthy habits, fitness, food, travel, language.
  • Outcomes: Chose food and grocery choices for students as the domain.
  • Next: Domain research and a first domain statement on Miro.

Week 4 (17–21 Aug) (backfilled)

  • State: Domain statement v1 on Miro: enhancing healthy food choices for younger university students when grocery shopping in person, with social and/or contextual computing. Interview questions drafted.
  • Outcomes: Ben's Miro comment (20 Aug) pushed us towards asking for specific stories rather than opinions.
  • Next: Round 1 interviews; literature search.

Week 5 (24–28 Aug) (backfilled)

  • State: A fifth member left the team; we continued as four and redistributed the Technical/Dev role to Anujitha. Round 1 interviews under way. Design Proposal presented: three concepts (Social Shopping Companion, Recipe-to-Cart Bridge, Housemate Meal Coordination).
  • Outcomes: Proposal feedback: what does "healthy" mean for everyone; consider non-app options; dietary, cultural and religious needs; social contexts versus social features. Studio: try not to make an app; use the double diamond; plan in more depth.
  • Next: Finish Round 1; build a quick probe to react to.

Week 6 (31 Aug–4 Sep) (backfilled)

  • State: Round 1 complete (7 interviews). Sessions with the app prototype under way [confirm].
  • Outcomes: Studio (Thu): consider people who don't see shopping as social; move documents to GitHub; strip away the app interface and interpret the underlying feedback.
  • Next: More app-prototype sessions; start synthesis.

Week 7 (7–11 Sep) (backfilled)

  • State: Prototype interviews with the v1 app probe (friend recommendations, group goals, recipes, checklist) continued (Aman ×5) [confirm week].
  • Outcomes: Strong signals for price, lists and trusted recommendations; group goals divisive; another app unwanted by some.
  • Next: Thematic synthesis; divergent non-app ideas.

Week 8 (14–18 Sep) (backfilled)

  • State: Synthesis done; concepts combined into NutriCart Hub (Home Dock + Cart Unit). Cardboard and HTML v2 tested (Kenan ×2). Shadowing attempted [confirm week].
  • Outcomes: Studio (Tue): use excerpts and stats; explain how the thematic analysis shaped the design; lean on physical prototypes; decide which functions reach the functional prototype.
  • Next: Week 9 stand-up.

Week 9 (21–25 Sep) (backfilled)

  • State: Stand-up delivered. See Week 9 Stand-up.
  • Outcomes: The social aspect is weak; design something a group uses; test with the physical prototype.
  • Next: Redesign around group moments; plan v3.

Mid-semester break (28 Sep–2 Oct) (backfilled)

  • State: Post-stand-up direction document written (3 Oct): feedback table, G1–G6 group moments, v3 scope, evaluation plan, data fixes.
  • Next: Team meeting to agree the domain statement, G1–G6 and v3 scope.

Week 10 (5–9 Oct) (backfilled)

  • State: Individual Annotated Portfolios due Wed 7 Oct (main focus for everyone). James built the v0.1 and v0.2 backend + Expo Cart Unit (files dated 8 Oct).
  • Next: Share the code; GitHub setup.

Week 11

Tue 13 Oct

  • State: Kenan uploaded our OneDrive research files to the repo and rewrote the README. James shared v0.1/v0.2. Code review found a strong base (live sync, scanning) but a thin social layer. v0.3 adds G1–G6 on top of James's code. README, WIKI drafts and the GitHub issue list prepared.
  • Outcomes: [record decisions from today's call: final domain statement, G1–G6 must-haves, hosting choice, session schedule, owners]
  • Next: [owners + dates]

Wed 14 Oct

  • State: Review found that full interview transcripts and two records with participants' names had been published in the public repo. That broke what participants were told (recordings and transcripts not shared outside the team).
  • Outcomes: Repo made private; the files removed from the whole history; every session re-published as a de-identified record with a participant code (R1, AP, HP, SH, ST); peer names blurred in feedback screenshots; real session counts confirmed from the records (7 Round 1 interviews, 10 app-probe sessions, 3 Hub sessions, 1 shadowing session). Prototype v0.2 and v0.3 committed under prototype/.
  • Next: Everyone re-clones; repo public again; WIKI published; task board created.

[date]

  • State:
  • Outcomes:
  • Next:

Template (copy for each meeting)

### Day DD Mon
- **Present:** 
- **State:** what's done since last time, with links to issues
- **Outcomes:** decisions made, and why
- **Blockers:** 
- **Next:** who does what, by when (link the issue)