A9: Results Team submission
In this assignment, we use Google Analytics to run online A/B testing that you planned out in previous assignments. We statistically analyze our data. We interpret our results and use our interpretation to guide final changes to our prototypes. We reflect on the validity of our experiment. We settle on our prototype's branding, and finalize our aesthetics to reflect the essence of our design. We continue to update our dev plan, identifying new stretch goals that we might not have time for.
The following rubric items are independently assessed. In general, evaluation works such that if the student/team meets, for instance, 9 out of 10 rubric items, then they have earned a grade of 90%. The assignment will not be graded unless it is submitted on a single, well-formatted, and easily readable PDF.
Note: if you are a rare group of 2: pursue a dev plan that meets the rubric with a reasonable workload. If you are unable, you may propose an accommodation to this on Piazza; include a link to your dev plan.
Note: for this week's studio, also draft a 30 second elevator pitch, describing your point of view, user needs, and prototype
- Compile and Analyze
- Include screenshots of your Google Analytics page as evidence the experiment was conducted with at least 10 users per test condition/variant
- Write a few detailed sentences explaining your recruitment process, justifying a good faith effort in obtaining your target demographic
- Present your data in a clear way, tables of both your observed and expected values are best, identifying the assignment of users to conditions and the results of user behavior in each condition
- Show the correct inputs to your chi-squared or other statistical test, your calculations, the correct resulting chi-squared value or test statistic, and resultant p value. Use 3 significant digits for all numbers. See another video for help
- Summarize all formal and informal, quantitative or qualitative, feedback you received from online testing
- Interpret and Implement
- Write a few detailed sentences interpreting the results of your analysis, speculating why the results are as they are
- Write a few detailed sentences describing the internal and external validity of the experiment
- Write a short paragraph delineating changes you have made, will make, or would like to make to your prototype, and mark them as such, and justify these changes based on your results (it is very rare for a test not to suggest changes)
- Write a few detailed sentences discussing what you learned from A/B testing and any other data generated from using Google Analytics
- Implement feasible changes you identified as a result of testing
- No usability bugs or console errors when reviewing the prototype. Prototype is polished as a result of online testing
- Accomplishing a goal in the app does not require unnecessary steps or processes
- Branding and Aesthetics
- Clearly identify your prototype's final brand name and point of view to be used during your final pitch
- Prototype's final brand name reflects its functionality and final point of view. You are allowed to continue to tweak your app.
- Prototype's visual design choices about color, typography, and layout reflect user needs and final point of view
- Prototype is visually compelling and mobile-optimized. Visual design is consistent within and across pages
- Prototype has a clean look and is easy to read (i.e. no white text on light background or vice versa) on all pages; words/buttons are not cluttered and information is not presented in such large chunks that they can be overwhelming to a user
- Development Plan
- A clickable or easily typed link, or a readable, properly oriented, and complete snapshot of your dev plan. Make sure the grader has access by the deadline. All tasks are actionable, prioritized, assigned an owner*, and given a time estimate. In your comments column, identify tasks that were newly added or removed/updated, and those derived from A/B testing. Includes a sum of the expected and actual number of hours for each teammate. Outliers should be justified
- Add new stretch goals for your prototype and identify them in the comments column
*every member of the team was assigned and completed at least one programming task
- Submit a clickable or easily typed link to your final prototype of the form “a9-projectname.herokuapp.com”. If your prototype is changed before grading is completed, you will receive no credit for the assignment
- Submit a clickable or easily typed link to your A design prototype of the form “a9-projectname.herokuapp.com/path/to/page_A” and B design prototype of the form “a9-projectname.herokuapp.com/path/to/page_B”
- Submit a clickable or easily typed link to your project repository on GitHub. Make sure the grader has access by the deadline
- Make email@example.com a collaborator for your Heroku app so that we can verify the commit that has been deployed
- Above and Beyond
- (Optional) This point is reserved for teams with prototypes that met 90% of the rubric items and went outside the box in their performance
Here are some examples from prior years. Note assignments change from year to year, so use these examples as a reference, see where they succeed/breakdown, and make sure your final submissions adhere to the rubric for this year.
User Testing and A/B Prep:
User Testing Plans:
App Demos (not required for this assignment):