Milestone 3 Deliverable 0 - The Garage Experience

Syllabus Spring » Class Sessions » Milestone 3 Deliverable 0

In this meeting the conversation goes like this: This milestone comes at the end of a solid month of work. What do we have to show for it? Can we put an MVP in front of our advisor? What does it point us to in terms of what we should be trying to accomplish before the end of the semester? What is our week by week plan for getting there?


OBJECTIVE		Description	Meets Expectations	Falls Short of Expectations
Deliverable 0		A first prototype? An MVP? Something.	{$c3}	TBA
Result			Measurement/Evaluation
R1	Artifact		TBA
R2	Presentation		TBA

OBJECTIVE		Description	Meets Expectations	Falls Short of Expectations
Mentor updates		TBA	TBA	TBA
Result			Measurement/Evaluation
R1	Initial contact		Done/Not done
R2	Followup as needed		Done/Not done

OBJECTIVE		Description	Meets Expectations	Falls Short of Expectations
Money/Time/Resource Budget		An initial sketch of what it is going to take to make the project a reality over the next several months. Persuade us that this is feasible.	Yes	No
Result			Measurement/Evaluation
R1	Meet to discuss OKRs		yes/no
R2	Revised OKRs recorded		yes/no

OBJECTIVE		Description	Meets Expectations	Falls Short of Expectations
Team formulated objective		TBA	{$c3}	TBA
Result			Measurement/Evaluation
R1	Measurable/Observable Result		TBA
R2	Measurable/Observable Result		TBA
R3	Measurable/Observable Result		TBA

OBJECTIVE		Description	Meets Expectations	Falls Short of Expectations
Team formulated objective		TBA	{$c3}	TBA
Result			Measurement/Evaluation
R1	Measurable/Observable Result		TBA
R2	Measurable/Observable Result		TBA
R3	Measurable/Observable Result		TBA

OBJECTIVE		Description	Meets Expectations	Falls Short of Expectations
Milestone 4 OKRs		self explanatory	Yes	No
Result			Measurement/Evaluation
R1	Meet to discuss OKRs		yes/no
R2	Revised OKRs recorded		yes/no

What are we looking for?

As the board of our creative firm, we are anxious at this point in the semester to see that your project has promise of actually happening. At the last milestone, the challenge was to convince us you had hit upon a problem worth solving. At this milestone, we are looking to be be persuaded that the direction you have chosen is (1) do-able (2) by you (and your collaborators). We are looking to see how you have moved from idea to thing, from problem to solution, from divergent research to convergent making.

We expect (mutatis mutandis) to see some tangible expression of the idea you are working on and we expect to see where this fits in the trajectory of your project. One element of this is to make sure we understand what the functional purpose of the prototyping is (see the References tab for a list of "why we prototype") and what this prototyping has yielded for you (that is, what have you learned from it, how will this inform your next steps?).

The purpose of the presentation is to report on (1) the status of your project, (2) communicate what you prototyped, why, and what you learned from it, (3) to elicit iteration-forwarding feedback from the audience.

The status report should be brief. The prototype demonstration and contextualization should be the main "show." You can promote iteration-forward feedback by anticipating and pre-answering obvious and easy to anticipate questions.

Draft Evaluation Rubric

Criterion	Needs to be Better	OK	Especially Noteworthy
Project status update	Too much time spent on rear view mirror. Pivoting without conveying why/how. Assuming audience knows what it doesn't	We understand how the project is unfolding and where it is. Coherent and brief reminder of what we are doing, why, what's previously accomplished so that we can hit the ground running and get the most out of what's new in this presentation.	Complete home run. Touchdown. Hat trick.
Prototype	Non-existent and no mutatis mutandis explanation of what we are seeing instead. Insufficient. One imagines a more substantial prototyping would have been possible. Or a series of prototypes rather than just one. Motivation unclear. We don't understand the WHY of this prototype. Prototyping activity does not seem to fit the project's trajectory.	Prototype is motivated, fits in the project trajectory, elicits learning that moves the project forward. Overall provides evidence that the solution direction is workable and doable and promising.	Wow.
Eliciting iteration-forwarding feedback	Team talks at, not with, audience. Presentation too long to permit feedback. Team gives no sense of what questions it has for audience. Response to feedback is too defensive. Response to feedback is too long-winded.	Presenters contextualize material in a manner that helps the audience know what to look for and how to apply its experience and know-how in a manner that's useful to the team.	Wow.
Other: judge's discretion.

Schedule this as spring class 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | Extra
Unschedule this as spring class 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | Extra | EDIT

Create this as class 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | Extra
Cancel this as class 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | Extra | EDIT

Create this as class A 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | Extra
Cancel this as class A 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | Extra | EDIT