PMs -- Present your work to staff and other teams. Demonstrate and reflect on progress so far. Solicit input and ideas from class. Practice oral presentation skills. Other PMs, developers -- Learn about technologies and strategies from other teams. Provide feedback. When the first Tuesday after each phase (all 5 PMs / day). Check the calendar for the exact date. Presentation focus at a glance
Motivation, problem statement Users and their roles Plans of approach for rest of semester Design review for MVP
Design review, progress reports, obstacles, and risks Focus on your app architecture. Discuss the responsibilities of each component (e.g., at the level of a UML diagram) and how these components work together to deliver functionality. New features, current architecture components, and rationale for design choices
Provide an overview of your functionality since Phase II. Discuss new features, how they work, what the different types of users can accomplish. Phase IV Project recap, design / feature highlights Future work: If you had one more phase, what would you work on? Challenges (and solutions), but please keep it professional (e.g., no rants)
This phase’s presentation should introduce and motivate the project.
- Find an engaging start to the presentation: asking the audience a question, adding an anecdote or an illustrative example. Be creative while also being respectful!
- Include a compelling motivation for your project. If possible, show existing alternatives and explain the client’s dissatisfaction with those solutions.
- Explain any technical terms, acronyms or helpful relevant information. List potential users (and their roles).
- Provide an overview and description of the features of the MVP.
- Display informative/relevant visualizations
- Note that clip art is seen as less professional than high-quality images.)
- Illustrate the functionality/app flow using clean, simple, informative diagrams / mockups / wireframes -- visuals can be more informative and explicitly show connections between components
- You can create an effective functionality/diagram walk-through using step-by-step animations (they can guide audience’s attention to the appropriate section of the slide)
- Include a section on current progress.
- It’s great to include a smoothly-executed live demo (or record a video of a walk-through)!
- Alternatively, use screenshots of the implemented features (make sure they are professional/relevant)! Outline high-level plans for each phase (breakdown of features). You can use a table or bullet-points, listing goals for each phase.
This phase’s presentation should “look under the hood” and describe the underlying run-time components, e.g., technologies/gems/scripts that are driving the project. The focus should be less on the functionality of the app, and more on the decisions behind the various architectural elements, what they accomplish, and how they interact with each other. Don’t focus too much on what the user actions should be, but instead, tell us what each run-time component is contributing to the project, and what components it connects to.
- Provide a project overview/client’s vision to remind the audience of your “mission”
- Give an overview of Architecture and the components that it is comprised of (e.g., data storage, pre-processing modules)
- Explain the reasoning behind team’s decisions to adopt selected technologies
- mention the limitations and challenges as well as the solutions, workarounds, and “take-away”s.
- Provide team’s MVP progress (what was finished, what’s in progress).
- Outline the plan for the upcoming phases (what features will be addressed next?)
This phase’s presentation should tell us a story of a user’s journey through the app.
- Provide a project overview/client’s vision to remind the audience of your “mission”
- Give an overview of different users and their roles
Use the presentation focus from above along with the instructions for the Phase 1 presentations as a guideline. Use the lessons and feedback from previous PMs to improve your presentation.
Use the presentation focus from above along with the instructions for the Phase 1 presentations as a guideline. Use the lessons and feedback from previous PMs to improve your presentation.
Added on 4/23: Your goal is to provide an overview of the project and the process that the team went through to arrive to the current prototype.
-
Find an engaging start to the presentation; Include a compelling motivation for your project to remind the audience of your “mission” (challenge yourself to come up with a new motivation, instead of reusing one from previous presentation(s)). If possible, show existing alternatives, explain the client’s dissatisfaction with those solutions, and explain how your work addresses the client’s vision.
-
Recap your project. Focus on what the team has achieved: what was your MVP, and how did you extend it? You don't necessarily need to talk more specifically about what the team accomplished in each phase, but you can show how your work evolved over the phases, highlighting specific features.
-
Outline and explain the reasoning behind team’s decisions to adopt selected technologies. What were the limitations and challenges as well as the solutions, workarounds, and “take-away”s?
-
If you had one more phase, what would you work on? What still needs to be fixed?
All team members should contribute material / diagrams / text. The PM is responsible for integrating the material into a coherent presentation. I encourage the PMs to to a rehearsal of the presentation in front of their team and use their feedback to improve the flow and the overall quality of the presentation. Submit slides on Canvas. Make sure that when you upload the slides, Canvas shows the formatting correctly (presentations made using Google Slides are known to cause issues, so check your submission carefully). You will likely be presenting from the instructor's laptop -- if you need additional accommodations, send a notification in advance.
Guideline: 8-10 min presentation + 4 min Q+A.
While not required, you are encouraged to dress professionally (no need to wear a full suit, business casual style is enough (here's a Wikipedia page for reference: https://en.wikipedia.org/wiki/Business_casual (Links to an external site.)Links to an external site.)).
Additional and ever-evolving collection of tips for presentations: https://docs.google.com/document/d/1jHD6l4yyVgpO0qVwG0jB-6x9XqB1aSZ6CMmIHJUShyw/edit (Links to an external site.)Links to an external site. Also, take a look at the sample pages of Trees, maps, and theorems: "Most slides just include too much text" (http://www.treesmapsandtheorems.com/X0105.php (Links to an external site.)Links to an external site.) and "Designing the presentation: template and checklist" (http://www.treesmapsandtheorems.com/X0303.php (Links to an external site.)Links to an external site.).
Presentation Content (10 pts)
- Did you provide an overview/motivation?
- Do you present the requested project components?
- Did you explain any technical terms, acronyms or helpful relevant information?
- Is your content well-organized, easy-to-understand, readable, and clear?
- Do you have an informative last slide?
Presentation Style (10 pts)
- Did you include informative/relevant visuals?
- Is it easy for the audience to see/read the content of all figures?
- Did you spell-check your slides?
Presentation Delivery (10 pts)
- Are you on time for your presentation?
- Do you speak loudly and clearly?
- Are you prepared to present your intended information? (e.g., did you rehearse your talk)
Responses to questions (5 pts)
- Did you repeat each question before answering?
- Have you understood the question before answering?
- Did the answer address the question?
Student Feedback (5 pt) Part of your score will be decided by your classmates in their feedback forms
- Did your answers to your peers' questions demonstrate understanding of the project?
- Did your peers find your presentation clear, helpful, and informative?