Peer Stakeholder PO Lookup

DS3 studio assignments for Spring 2026

Author

Affiliation

Lucas P. Cordova, Ph.D.

Willamette University

Published

May 25, 2026

Abstract

Each DATA 510 capstone project is assigned to one of three weekly Studio Sessions (1, 2, or 3) and is supported by two or three domain-matched individual Peer Stakeholder Product Owners. Every individual student is an owner on exactly one project and a peer PO on exactly two other projects, with their two stakeholder assignments placed in the two sessions other than their own project’s session. The result is a conflict-free in-person schedule with no rotation. Use this page to look up your studio: find your project by name to see the Studio Session it is in and who your peer POs are, or scan the stakeholder columns to find the projects you are a peer PO on.

How to read this page

Each row defines one studio in the DS3 framework:

Project. The owner team for the studio. They are accountable for the Iteration Review each week.
Studio Session. Which of the three 40-minute sessions inside the 120-minute class block this project runs in. See the Studio Session page for the schedule.
Stakeholder 1, 2, and 3. The individual peer POs assigned to this project. Most projects have three stakeholders; one has two. Each stakeholder files a written Studio Brief before class and a written Studio Critique the following class, and attends the project’s Studio Session in person.
Shared theme. A one-sentence summary of the domain or methodology overlap that links the project to its stakeholders (where possible).

If you appear in the Project column you are an Owner; if you appear in any Stakeholder column you are a peer PO on that row’s project. Every student appears in both contexts somewhere on this page (the Dual-Role Studio Membership rule of DS3).

The table below is sortable and searchable; type a name, session number, or theme keyword into the filter box to find your studio.

Studio assignments

matches = FileAttachment("stakeholder-matches-by-team.csv").csv({typed: true})

viewof query = Inputs.search(matches, {placeholder: "Filter by name, session, or theme..."})

Inputs.table(query, {
  columns: ["Project", "Studio Session", "Stakeholder 1", "Stakeholder 2", "Stakeholder 3", "Shared Theme"],
  header: {
    "Project": "Project (Owner Team)",
    "Studio Session": "Session",
    "Stakeholder 1": "Stakeholder 1",
    "Stakeholder 2": "Stakeholder 2",
    "Stakeholder 3": "Stakeholder 3",
    "Shared Theme": "Shared theme"
  },
  rows: 25,
  layout: "auto",
  format: {
    "Project": (d) => htl.html`<strong>${d}</strong>`,
    "Studio Session": (d) => htl.html`<strong>${d}</strong>`
  }
})

How the matches were made

Assignments were chosen to satisfy two hard constraints and then optimize for domain alignment:

No scheduling conflicts. Each individual is a stakeholder on exactly two projects, one in each Studio Session other than their own project’s session, so they can attend both in person every week.
At least two stakeholders per project. Most projects (20 of 21) get three stakeholders; one project has two, where the third-best match would be weak.

Pairs are not symmetric in every case (you may be a peer PO on a project whose owners are not peer POs on yours), because the goal was the best fit for each owner given the session-conflict constraint, not a uniform graph.

If you believe your match is wrong, email me. Matches were optimized for domain overlap inside the conflict-free schedule, but you may know about a tighter connection or a conflict that was missed.

How to use your studio

If a project is yours (Owner)

Reach out to your peer POs in week 3. Share your draft research question, data sources, and a one-paragraph success picture from the Studio Charter.
Treat their Studio Briefs as real customer requirements. You do not have to adopt every item, but you must log every item as adopted, deferred, or declined with a reason in your Iteration Review.
Make your work visible. Your repo, board, and Iteration Review are how peer POs can write meaningful Studio Critiques. If they cannot see what you did, the critique will be useless and that is on you.

If you are a Peer Stakeholder PO

You owe each project you support a Studio Brief and a Studio Critique every week (see the templates on the Studio Session page). The in-person discussion happens during that project’s Studio Session; the written artifact is always required.
You are not expected to be a content expert. You are expected to be an informed, curious, and honest neighbor in the same domain.
Substantive feedback is specific, kind, and actionable. “Your stakeholder section is vague” is less useful than “Your stakeholder section names three roles but does not say what each one would do with your results.”

Operating mechanics

Schedule. Your two stakeholder projects are placed in the two Studio Sessions other than your own project’s session. You attend both in person every class. Details on the Studio Session page.
Conflicts. If your owner team and a peer PO disagree on priority, log it in the Iteration Review and bring it to the Instructor Sync slot during the next Studio Session. I arbitrate as Process Expert.
Grading hook. Peer Stakeholder PO duties are graded as their own top-level component worth 15% of the final course grade, with a published rubric and a participation floor (missing 4 or more Briefs or Critiques caps this component at 50%). See the syllabus for the rubric and the project methodology page for context.