Partner project
Your team will spend the semester working as interns for a Buffalo-area company: the company brings a real problem, and your team delivers working software that addresses it. The project ends with a handoff to your client, and a public presentation in May to clients, families, and the Buffalo tech community.
The brief
- Note: Placeholder. Each team's partner company problem goes here once projects are selected (see
pilot/partner-project-intake.md). Sections follow the intake form. If there are two teams with different partners, this can become one page per project. Do not include confidential details; this site is public.
The organization
[Organization name, what it does, and who it serves.]
The problem
[The specific problem, the users affected, and the recurring task or workflow. One recent example of how people handle it now and what is difficult.]
What success looks like
[The smallest useful result worth testing, and one or two observable signs of success.]
Scope
[One to three essential capabilities. What is optional or out of scope. Deadlines, accessibility needs, existing systems, and dependencies.]
Data
[Inputs and outputs. Which public, synthetic, or de-identified examples the team will use.]
Working with the client
[Client contact and role (no email on the public site), check-in cadence, and who approves scope and the final result.]
Requirements
Process
| Week | Phase | Deliverable |
|---|---|---|
| 2 | Orientation | Summary of the company, its users, and the project brief |
| 3 | Requirements | Requirements and sprint plan, confirmed with the client |
| 4โ7 | Development sprints | Sprint release with demo and client feedback (one per week) |
| 8 | Stabilization | Usability, accessibility, and security review; tests; documentation |
| 9 | Handoff | Handoff package; client acceptance |
| May | Presentation | Pitch, demo, and poster; final report; individual reflection |
Orientation and requirements
๐ป Learn about your client: what the organization does, who its users are,
and how the problem shows up in their work. Use the interviewing practices from
Needfinding with your client and, where
possible, with the people who will use your software. Write brief.md summarizing what you
learned.
๐ป Write requirements.md: what the software must do, with acceptance
criteria for each requirement, and a plan for which requirements go in which sprint.
Confirm it with your client.
Development sprints
๐ป Each sprint, build, test with users, and release. Use the practices from
Team workflow: branches, pull requests,
review, and your team's CLAUDE.md and NORMS.md.
$ git tag v0.2
$ git push --tags
๐ป Demo each release to your client, and send a status update after each check-in, as in Professional communication.
Stabilization and handoff
๐ป Review your software for usability, accessibility, and security. Add tests for the core tasks, and write the documentation your client needs.
๐ป Hand off the software to your client, and get their sign-off.
Presentation
The public presentation is in May. Each team gives its pitch and demo, then stands with its poster to talk with visitors.
Final report and reflection
๐ป As a team, write report.md. For each major decision (the requirements
you prioritized, design changes after testing, what you left out), describe the decision and
the evidence behind it, linking to files in your repository.
๐ป On your own, write reflection.md:
- What did you learn this semester that you're most proud of?
- How has the way you use AI changed since the start of the studio? Point to your skills and their revisions.
- Choose one of the readings we discussed about AI and society. How does it connect to your own work in the studio?
- What would you do differently on your next project?
- Note: Merged the former final project into this page, so the partner project is the final deliverable. The design labs (Needfinding, Concept iteration, Prototyping) still assume each team has a project of its own; if there is no design-cycle project, they should be re-aimed at the partner project.
- Note: This page has no
repo_url, so themwcmanifest doesn't list it. Teams would work in a shared repository set up per partner.