Technical Presentation Critique

Each member of the reviewing team should take notes on the presentation, and combine/collate their notes afterward so that each team submits one or more review(s) of other presentations.  (Your instructor will clarify how many presentations each team must critique to meet this deliverable.)

Keep in mind the following as you take notes, and feel free to use the suggested rubric below when compiling your final report:

  • Did the presentation feel like it had been rehearsed? For example, did the speaker(s) make eye contact with the audience, or just read off a page?
  • Were the technical ideas clearly presented? Did the content of the slides complement what was being said, or were the slides mostly paragraphs of text pasted into PowerPoint?
  • Identify at least one positive point about the presentation, and one point that could use improvement. Be specific: your comments should be phrased such that if you received that comment, you would be able to take specific action in response to it.
  • Identify one idea you might adopt for your own future projects as a result of something you saw in the presentation.

Reviews should be candid, but they are not anonymous, so treat the presenting team the way you would like them to treat you when delivering negative feedback:

  • Poor example of negative feedback: "Speaker X's presentation style sucked."
  • Better example: "Speaker X appeared to be reading from a script and didn't engage the audience. It would have been more effective if she/he had rehearsed their presentation a bit more."

Possible rubric for organizing your critique of the presentation

Aspect Exceeds Expectations Meets Expectations Somewhat below expectations Not acceptable
Preparation Very obvious that presentation was rehearsed thoroughly. Students came prepared with few hiccups Presentation is mostly fluid, with the exception of maybe 1 or 2 underprepared people Sloppy presentation, no clear direction or disorganized It was really, really bad. I could have presented about their app better than them, impromptu
Description of Customer Need included brief statement of customer problem and scope of project Not clear what the customer really wanted or what problem the group is trying to solve No discussion of customer needs
Technical Discussion Clearly conveyed some technical details of the app. Discussed a technical challenge in an understandable way Attempted to talk about technical aspects of app, mostly successfully, but did not mention technical challenge; or, not able to clearly convey technical topics Little technical coverage of their app; hard to discern implementation or challenges No technical discussion
Customer Interaction Clearly describe relationship with customer. Talk about goods, bads, and what was learned Talked about customer interaction to some extent. Shared what they learned from the experience Mentioned customer interaction, but no details about the experience No discussion of customer interactions
Development Practices Explained clearly their implementation of agile in their iterations. Reflect on what went well and what did not. Had a method to taking on iterations. Briefly explain development practices. Give an idea of approaches they took to iterations/Agile, but don’t reflect on their effectiveness Minimally talk about development lifecycles and iterations; suggests they didn’t take them seriously and had no concrete implementation of agile principles No discussion of iterations or approach to handling them
Comments