Project Workshop

Final Presentation Overview

Together, your mission is to construct an engaging and convincing argument demonstrating the value of your interactive solution

To achieve this, you’ll need to work together, each team member speaking with confidence and authority about a component of your team’s solution.

The whole of your solution should come off as greater than the sum of it’s parts – this will happen when each team member presents as the authority on their component, separate, but in harmony with the other team members

Together, your are an ensemble, a band, an orchestra – The Weather Report, The Rolling Stones, the London Symphony Orchestra

Exercise

Take a few minutes to pick a patron ensemble, band or orchestra for your team.

Final Presentation Elements

What? What problem is your solution addressing?

Who? Who are the stakeholders?

How? How does your solution address the problem?

Why? Why did you take this approach?

When? When could your partner begin using your solution?

Exercise

Together with your team, review your team pages & the project deliverables you’ve generated over the course of the semester. Organize your deliverables against each of the elements listed above (i.e. User Personas & User Stories might map to the Who, the Usability Reports could map to the Why, etc).

Assignment

Together with your team continue organizing your deliverables from the semester against the elements listed above

As a team, agree amongst yourselves who will be responsible for presenting which elements

Individually, begin organizing how you would like to present your section

Make a list of specific things your team would like to observe about how your test users use your prototype

Paper Prototype Usability Testing Roles

Tester – The one who was going to test the other teams’ prototypes. This person will be asked to “think aloud” while testing the prototypes, to give observers context.

Computer/Device – This person should remain silent and react to the tester’s commands using the paper prototype components. For example, when the tester texts a response to an SMS prompt, the “Device” should swap in the next prompt (tip: be sure to include error messages)

Assistant-computer – In times of need, an “assistant-computer” to give the “computer/device” some extra processing power! (i.e., on-the-fly cutting and pasting of missing GUI elements, SMS prompts or messages).

Observer – This person writes down everything the testers say and do, but especially what they don’t/can’t do or have difficulty with.

User Testing Exercise

Organize your team into the usability testing roles listed above

We’ll cycle around the room 3 or 4 times, rotating roles each time

Between each cycle, make revisions to your paper prototype bsed on the observations of the previous cycle

We want everyone to play each role, and each team should end up with 3 or 4 sets of usability testing observations to use as inputs for refining your prototypes

Did your paper prototype improve with each subsequent cycle?

Assignment

2nd Usability Reports

Together with your team, create a new Google Document and title it “Usability Report v2”

Identify your team and the date on the report

Create a heading called Methodologyand write a description of how you conducted your usability tests, including how many rounds of testers were tested. Also include descriptions of the roles team members performed during testing (see the roles listed above)

Create another heading called Objectives and list the specific things your team was looking to validate through the testing

Create another heading called Observations and combine the three or four sets of observations into one master list. Be sure to de-duplicate repeated observations

Team Page

Add a link to your 2nd Usability Report under your Usability Testing heading, include the date in the link text

Announcements

Team Breakfast Mafia, I have a Trenton middle school nurse contact for you

Project Status

Let’s take a few minutes to review the status of each of your projects. Let’s review each of your Usability Reports.

Exercise

With your group, make sure your team pages are up to date. I’ll come around and review each your team pages.

Minimally, you should have links to:

Document Concept

User Personas

User Stories and/or Jobs

Flow diagrams

Paper Prototypes

Usability Reports

Documentation

Please make sure your Team Page presents well, you should be using this to get feedback from your partners and will use it as the starting place for your final presentations.

Documentation

Why document your projects?

What kinds of things should you document?

Equipment requirements

Architectural requirements

Software requirements

Accounts

Maintenance procedures

Update procedures

Expenses and estimated budgets

Others?

Exercise

Project Documentation List

For each member on your team, take turns role playing that you are your client partner. As the client partner, imagine what you would need to know if you were to actually try to implement your team’s project. Start a list with the first role player, adding to it with each additional role player.

Draft Project Implementation Documentation

Create a new Google Drive document and title it Project Implementation Documentation

Scour over your list, looking for common themes

For each theme, create a heading in your document; for example, if your project requires usernames and passwords to be able to use it, include a section on user names and passwords

Project Workshop

Continue iterating on your projects with your team. If you need to feedback on any of your refinements, ask another team to help test using the usability testing procedures we worked through last week.

Make a list of specific things your team would like to observe about how your test users use your prototype

Paper Prototype Usability Testing Roles

Tester – The one who was going to test the other teams’ prototypes. This person will be asked to “think aloud” while testing the prototypes, to give observers context.

Computer/Device – This person should remain silent and react to the tester’s commands using the paper prototype components. For example, when the tester texts a response to an SMS prompt, the “Device” should swap in the next prompt (tip: be sure to include error messages)

Assistant-computer – In times of need, an “assistant-computer” to give the “computer/device” some extra processing power! (i.e., on-the-fly cutting and pasting of missing GUI elements, SMS prompts or messages).

Observer – This person writes down everything the testers say and do, but especially what they don’t/can’t do or have difficulty with.

Exercise

Organize your team into the usability testing roles listed above

We’ll cycle around the room 3 or 4 times, rotating roles each time

Between each cycle, make revisions to your paper prototype bsed on the observations of the previous cycle

We want everyone to play each role, and each team should end up with 3 or 4 sets of usability testing observations to use as inputs for refining your prototypes

Did your paper prototype improve with each subsequent cycle?

Assignment

Usability Reports

Together with your team, create a new Google Document and title it “Usability Report”

Identify your team and the date on the report

Create a heading called Methodologyand write a description of how you conducted your usability tests, including how many rounds of testers were tested. Also include descriptions of the roles team members performed during testing (see the roles listed above)

Create another heading called Objectives and list the specific things your team was looking to validate through the testing

Create another heading called Observations and combine the three or four sets of observations into one master list. Be sure to de-duplicate repeated observations

Team Page

Create a new heading called “Usability Testing” on your team page on the blog

Add a link to your Usability Report under this heading, include the date in the link text

Make sure all of the links on your team pages are actual links and not just urls in text. Proper links should be hyperlinked text that describes what is being linked to.

Design Notebooks

Individually, create a new slide in your Design Notebook and title it “Usability Testing”

Write a brief paragraph highlighting what you learned about your prototype’s usability from the tests

Did anything surprise you?

Make a list of refinements you’d recommend your team make to your prototype based on the observations from the testing exercises

Include a link to your team’s Usability Report on your slide

*Submit the link to your Design Notebook to Canvas before we meet again next week

Make a list of specific things your team would like to observe about how your test users use your prototype

Paper Prototype Usability Testing Roles

Tester – The one who was going to test the other teams’ prototypes. This person will be asked to “think aloud” while testing the prototypes, to give observers context.

Computer/Device – This person should remain silent and react to the tester’s commands using the paper prototype components. For example, when the tester texts a response to an SMS prompt, the “Device” should swap in the next prompt (tip: be sure to include error messages)

Assistant-computer – In times of need, an “assistant-computer” to give the “computer/device” some extra processing power! (i.e., on-the-fly cutting and pasting of missing GUI elements, SMS prompts or messages).

Observer – This person writes down everything the testers say and do, but especially what they don’t/can’t do or have difficulty with.

Exercise

Organize your team into the usability testing roles listed above

We’ll cycle around the room 3 or 4 times, rotating roles each time

Between each cycle, make revisions to your paper prototype bsed on the observations of the previous cycle

We want everyone to play each role, and each team should end up with 3 or 4 sets of usability testing observations to use as inputs for refining your prototypes

Did your paper prototype improve with each subsequent cycle?

Assignment

Usability Reports

Together with your team, create a new Google Document and title it “Usability Report”

Identify your team and the date on the report

Create a heading called Methodologyand write a description of how you conducted your usability tests, including how many rounds of testers were tested. Also include descriptions of the roles team members performed during testing (see the roles listed above)

Create another heading called Objectives and list the specific things your team was looking to validate through the testing

Create another heading called Observations and combine the three or four sets of observations into one master list. Be sure to de-duplicate repeated observations

Team Page

Create a new heading called “Usability Testing” on your team page on the blog

Add a link to your Usability Report under this heading, include the date in the link text

Design Notebooks

Individually, create a new slide in your Design Notebook and title it “Usability Testing”

Write a brief paragraph highlighting what you learned about your prototype’s usability from the tests

Did anything surprise you?

Make a list of refinements you’d recommend your team make to your prototype based on the observations from the testing exercises

Include a link to your team’s Usability Report on your slide

*Submit the link to your Design Notebook to Canvas before we meet again next week

Assignment

Midterm Papers

Reading

Paper Prototypes

Meet with your team and continue developing your paper prototypes

Based on the reading, and using your User Personas, User Stories and/or Jobs, pick two additional example users (for three total, including the one you developed in class) and identify specific tasks they need to be able to accomplish for your solution

Create flows for each by writing lists of steps they’ll need to take to complete the tasks – be sure to include entry points and goals

Create a set of drawings on paper that represent their interactions; these could be screens, or text messages, or voice menus, etc

Be sure to include descriptions of the specific content that will need to be present (just a description at the moment, you’ll need to develop the actual content later)

Design Notebooks

Create a new slide in your Design Notebooks and title it “Flows & Paper Prototypes”

Write a paragraph defining what flows are and why you should use them to describe what your system needs to do.

Include links to the flows and paper prototype images your team created for your project

*Submit the link to your Design Notebook to Canvas before we meet again next week

User Research Document (as a team)

Create User Personas for each of the user types you’ve identified for your project

Review the Trenton 250 web site, the Food Assets report and your notes from the partner presentations and look for any references to demographics and user types that are relevant to your team’s project

Identify what information you WEREN’T able to determine about each of your user types from the above resources

Make a list of these open questions to ask your partner organization

Contact your partner and make arrangements to visit them and/or their organization in order to observe and/or interview as many of these user types as possible to gain a better understanding of the “jobs” they need to fill and how they go about filling them now

Based on these interviews/observations, create a list of personas & user stories or job stories, depending on your circumstances

*Submit the link to your Design Notebook to Canvas before we meet again next week