Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Each team member will conduct two interviews of people outside of class to understand their perspective on your chosen topic and on trivia games. You will want to investigate the depth of each person's knowledge and passion about your topic. You will also want to gather their likes and dislikes with trivia games and mobile gaming in general. As a team, review your interview responses and use this information to develop personas, one for each team member, that describe the context, needs, and frustrations of stakeholders, revealing opportunities to support meaningful experience with your topic. Each team member can also create a short storyboard that describes a "before, during, and after" story of how your solution provide an improved outcome. Here are templates: Persona Template & Storyboard Template
❏ Deliverable Collect your team's personas and storyboards into a single document or slide set.
Each team member will conduct background research on likely topics for your trivia app. Begin to be subject matter experts in any topic you choose and consider the knowledge your target audience may or may not have. You want your treatment of the topic to be accurate and appropriate for the context of your concept. For example, if your team were focusing on a health issue as the topic, see the instructions below on how you could do research.
Example Research Perspective for Health Topics: Each team member will conduct background research on at least one health issue to understand the scope of each problem (like trends, statistics, and causal relationships) and the opportunities to affect public awareness. It is important to look at each health issue through the lens of public awareness, since your trivia game can address that, rather than brainstorming cures or new treatment plans etc. How knowledgeable is the general public on the topic right now? How much could the community benefit from learning some key information through a trivia game? What is the potential for generating some social movement? Will you have access to the communities greatly affected by the health issue for further research and testing your trivia app? As a team, discuss all the research and determine which health issue will be your focus. If your team is still undecided, you may use the interviews in the next task to help you finalize your decision.
❏ Deliverable Collect your team's background research into a single document or slide set. Include the team's decision on which topic(s) your trivia game will address, or provide the team's plan to investigate a bit further before making that decision.
As a team, simply map out ideas for your trivia game based on your team's interest and the potential value (or impact) the idea may have with your target audience. There are no strict rules on how to do this. You simply want to entertain all the ideas and begin to evaluate which ideas have the most promise. Idea Map Template
Each team member will create a unique interaction storyboard concept based on your understanding about the stakeholders, the trivia code, and a health topic. Each concept (interaction storyboard sketch) should contain four screen sketches that represent the welcome screen, question screen, correct answer feedback, and incorrect answer feedback.
Your goal is to have several unique design concepts (even though they address the same trivia topic) to consider as you move forward. You will be able to get some feedback during your proposals on these different ideas.
On why to sketch: Etch A Sketch: How to Use Sketching in User Experience Design Check out the first part of this video. This video provides some nice sketching techniques too.
❏ Deliverables Create a team idea map and collect your team's storyboard sketches into a single document or slide set.
Refine your previous work as needed to be included in your proposal presentation. Ensure that each slide contributes to an explanation of a cohesive story that supports your initial concept and value proposition.
7 TIPS FOR PROPOSALS, PITCHES AND PRESENTATIONS
❏ Deliverable Your team's proposal as a collection of slides containing...
a title slide
your value proposition
summary slides (or exemplars) of your team's work - likely not everything though.
competitive analyses
stakeholder personas
storyboard sketches.
Each team member will complete to develop a firm understanding of the technical opportunities and constraints your team will have with your design. Also, complete the steps needed to .
==> (9 STEPS)
As a team review, you can map out the potential features of a trivia app according to the level of impact a feature might have on a user and the level of difficulty in implementing the feature with code. This should help you with the decisions you will make later about your solution. you could use to complete a map.
❏ Deliverable Demonstrate that you have completed the build tutorial, created a question database and can discuss how the code works. Optionally, share your team's mapping of potential features.
❏ Advanced Deliverable Demonstrate that you have made modifications to the trivia app in the following ways.
Make at least three noticeable style changes to the game, likely done by changing the stylesheet CSS. to consider.
Choose and incorporate at least one Javascript code modification from .
In this phase you well begin to frame the goals of your team's design by learning about these important aspects.
stakeholders in your community
technology available to you and features of existing trivia designs
context of health issues in your community.
After conducting research, you will develop initial design ideas and compose a clear value proposition that defines what your team will create, for whom, and the value it will bring. Finally, you will present a proposal to your class and the community for feedback, helping you refine your design direction moving into the next project phase.
Each team member will contribute one competitive analysis of an existing trivia game that is either available on the Web or as an app. Even though you are not investigating direct competition, you will find the analyses valuable in discovering good ideas that you may incorporate into your team's solution. Keep the context of your game in mind, because this may influence what features are appropriate for a game focused on a particular topic.
❏ Deliverable Collect your team's competitive analyses into a single document or slide set.
Value propositions clearly define key aspects of your design that demonstrate it is a valuable and worthwhile product or service. It provides focus for the design of many types of services or products. Here is a template to get you started.
For [describe target users] who [describe problem or need], [name of product/service] is a [describe type of product/service] that [describe benefit or value].
As a team, review all of your work and discuss several possible design directions before settling in on one single value proposition. You will want this statement to be clear, concise, and compelling. It should be supported by your research and analysis up to this point. Begin to map out the features of your solution. This will likely be updated as you go, but start to think about each feature (also could be called user stories) that your solution will provide. will give you a good introduction to the concept and you can use to get started with the map. Again, this is just a draft of your intended features to provide users and will be adapted later.
❏ Deliverable A document or slide with your team's value proposition and a draft features map.
See feature map example in .
✓- Below Standard
✓ At Standard
✓+ Above Standard
Stakeholder personas are provided but lack clarity and offer limited value in understanding the stakeholders.
Stakeholder personas provide thoughtful descriptions of people that will guide the design of a valuable solution.
Stakeholder personas are vivid descriptions that will bring exceptional focus to the team's development work.
Storyboards lacked a clear narrative or provide little description.
Storyboards outlined the before, during, and after narrative with clarity.
Storyboards demonstrated a careful and insightful perspective on potential narratives.
✓- Below Standard
✓ At Standard
✓+ Above Standard
Background research is provided but reveals limited insight on the topic.
Background research provides valuable data and context on the topic and will contribute to framing the team's solution.
Background research demonstrates especially diligent work, mapping a clear understanding of the context and available knowledge.
✓- Below Standard
✓ At Standard
✓+ Above Standard
Storyboard sketches were completed but only brought a vague understanding of the team's initial ideas.
Storyboard sketches were clear and presented concepts that will positively influence upcoming design work.
Storyboard sketches represented exceptionally clear and detailed concepts, that provide continuity with the research and provide great launching points into upcoming design work.
Idea map demonstrated some effort in thinking about potential directions, but lacked rigor or did not demonstrate a collaborative mindset.
Idea map demonstrated creative thinking and a collaborative mindset coupled with a simple analysis of each idea.
Idea map demonstrated creative thinking and the team demonstrated a thoughtfully open process in their generating diverse ideas without judgement followed by a agreeable method of analyzing each idea's potential.
✓- Below Standard
✓ At Standard
✓+ Above Standard
Information presented in a way that is not always clear, concise, and logical. The presentation style and selection of material is not fully appropriate for the context.
Information presented in a clear, concise, and logical manner. The selection of material and style is appropriate and effective.
Exceptionally curated information that is delivered in an interesting, coherent and memorable way.
Delivery: Eye contact, poise, and appropriate voice-level often lacking.
Vocal clarity, eye-contact, and physical composure maintained throughout.
An exceptionally engaging delivery of content lacking unnecessary distractions from the content.
✓- Below Standard | ✓ At Standard | ✓+ Above Standard |
The code tutorial was partially completed or evidence of understanding was limited. | The core functions of the technology and code are understood and modifications could be implemented to customize the result. | The code and technology was thoroughly investigated and creative methods were used to test the capabilities of the supplied code template. |
Task | Estimated Time |
Problem Definition & Importance | 1 hour |
Technology Experimentation (Trivia Code Tutorial) | 4 hours |
Competitive Analysis | 2 hours |
Stakeholder Profiles & Narratives | 2 hours |
Initial Ideas & Evaluation | 2 hours |
Value Proposition | 1 hour |
Team Proposal | 1 hour |
✓- Below Standard | ✓ At Standard | ✓+ Above Standard |
Competitive analyses are provided but they reveal limited valuable insight on existing work. | Competitive analyses provide valuable observations about existing work and will contribute to refining the team's solution. | Competitive analyses demonstrate especially keen insight, recognizing gaps in existing work that the team could offer in their solution. |
✓- Below Standard | ✓ At Standard | ✓+ Above Standard |
Value proposition is provided but is not clear or does not offer a compelling need for the proposed solution. | Value proposition is clear and supported by the team's research. | Value proposition is especially convincing and generates anticipation to see the rest of the project. The value to stakeholders is compelling. |
Features map demonstrated little thought in breaking down a solution into needed parts. | Features map demonstrated a thoughtful attempt to define needed features. | Features map demonstrated a particularly careful consideration of a the priority of features to the solution. |