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

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

WeekPhaseDeliverable
2OrientationSummary of the company, its users, and the project brief
3RequirementsRequirements and sprint plan, confirmed with the client
4โ€“7Development sprintsSprint release with demo and client feedback (one per week)
8StabilizationUsability, accessibility, and security review; tests; documentation
9HandoffHandoff package; client acceptance
MayPresentationPitch, 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:

  1. What did you learn this semester that you're most proud of?
  2. How has the way you use AI changed since the start of the studio? Point to your skills and their revisions.
  3. Choose one of the readings we discussed about AI and society. How does it connect to your own work in the studio?
  4. What would you do differently on your next project?