Professional Documents
Culture Documents
Portfolio Planning
Portfolio Planning
For your final project grade, you will turn in a portfolio of your teams work throughout the
semester. Your portfolio should contain as much information about the design process as
possible, including all of the assignments with commentary and documentation of the various
prototypes that your group developed and refined that were not part of class assignments. In
general, your portfolio should serve as a sort of scrapbook of all of your project activities
throughout the semester. As such, it is much easier to collect this information during the
process than it is to try to re-construct after the fact. Make sure to take as many photos, notes,
videos, etc. of your project work during the process so that you can compile it into your portfolio
as the culmination of your work. More detail will be provided throughout the semester.
Criteria
Noob (75%)
Important aspects are
neglected or
unfinished
Ding!
(85%) Adequate;
Most aspects of the
task have been
fulfilled
Woot! (100%)
Outstanding; meets
all requirements
Portfolio provides
minimal
demonstration of
brainstorms
Documents a range
of ideas (10-20)
Provides
documentation of a
large variety of ideas
(more than 20)
Provides minimal
description of a few
prototypes (3-4)
Provides description
of prototypes,
presented in class
as well as other
prototypes
completed out of
class
Provides thorough
descriptions of each
prototype with
explanation of
design decisions for
each revision
Distinguishes
individual and team
contributions for
some items
Distinguishes
individual and team
contributions for all
items- meeting
agenda- ex.
practicing pitch,
playtesting
Provides a game
design that is difficult
to understand
Provides substantial
documentation but
does not fully
articulate all aspects
of design
Provides complete
game design
documentation that
could be built by
someone outside
the team
Provides pitch
presented in class
Minimal reflection
included in the
portfolio
Reflection included
along a few of the
learning objectives
with some
explanation
Thorough reflection
of each learning
objective
Assignments
Shelby: Tumblr integration (by class Tuesday - unless havent received all feedback yet)
Grace: Organize Drive (Saturday), Individual/Team contributions ( Sunday)
When reviewing Tumblr: check to see if we have any extra documents we created that are not
currently in the portfolio (e.g. Logic Model)
Can someone explain how detailed the design documentation should be.. I feel that my part and
mary ellens part overlaps a little? I might be wrong -celina