Previous Lecture

lect16

Next Lecture

lect16, Tue 05/25

UX Evaluation, 3rd Retro

Announcements

• In the interest of bundling all your energy on the final product deliverables, we will not have an 8th homework.
• This week’s lab will be taken up by the group peer-evaluation lab08, so make sure to finish all points for ongoing labs 06 and 07 before Section starts.
• Code Freeze for your projects will be a week later, Friday, June 4th!
• All documentation and the presentation video will be due at the end of Tuesday, June 8th.
• Project presentations will take place, as long announced and planned, during the final exam slot, June 10th, 4-7pm.

Here, again, is the now agreed-upon point percentage breakdown for grading that the teaching team plans to use for the “Final Product” 40% of the course grade:

• 15% Presentation
• 5% Idea, and Idea Refinement
• 25% Functionality, Quality (Reliability & Polish)
  • judged by review of demonstration, user manual, peer review, teaching team testing
• 10% Technical Difficulty Implemented
  • judged by review of code/scope taking into account team background/experience etc.
• 20% Implementation
  • judged by review of Github code, PRs, etc.
  • use the README.md to make clear the repository structure and guide through implementation effort!
• 15% Design Process
  • judged by Design Document, Kanban Board, Meeting Logs, Github TEAM information, etc. Design Document should steer through the process.
• 10% Manual

End User Evaluation

You will likely not have time to conduct your own independent end user evaluation (prove us wrong if you do!), but this week’s peer group evaluation will be a step in that direction

• Slides on User Evaluation

Today (or at your schedule): Third and Last Retrospective

This is your last major opportunity to inspect and adapt on your path toward the goal line! This week’s lab there will be our peer evaluation where another team tests your deployment instructions and current state product, and then there is one more week of development until code freeze!

You already know the goal and procedure for Retrospectives from your previous retros. This Retrospective allows you to discuss things that are important to get to the best team productivity in this critical final final stretch to product deployment, documentation, and presentation.

• In your team’s repo, under team/retrospectives directory, add a file RETRO_03.md capturing the following:

  # Retro #3 <date>
  
  * Led by: name-goes-here
  * Present: name1, name2, ... , nameN
  * Absent: name1, name2, ...
  
  ## Action item
  
  * a goal: identify something the team wants to get better at
  * a change: identify one thing that the team will change about how it works together
  * a measurement: identify at least one way to measure whether the change helped the team acheive the goal, or move closer to it.
  
  ## Optional
  
  * Record anything else you think the team might want to remember from this retro
  
  

• After the Retro

  All Team members: Fill out peer eval survey (on email from CATME.org)

  Retro leader: add the following Section to RETRO_03.md:

  ## Retro Assessment
  
  * A brief description of what retro outline or process you used.
  * A brief assessment of how it went.
  * A brief statement on how much any of the Retros changed the way you worked as a team (no correct answer here. 
    Teams could be happy with the way they started operating from the get-go and Retrospectives would just be quick 
    confirmations then, or teams could have tried a lot of different things based on their retro reviews. We just would like to know!)