CS 471 Fall 2024 > Mini-Project Presentation #1 (First Progress Report)
CS 471 Fall 2024
Mini-Project Presentation #1 (First Progress Report)
For general information about the mini-project, see Mini-Project Presentation #0; everything in the General section still applies.
This document covers Mini-Project Presentation #1.
Presentation #1 Requirements
Mini-Project Presentation #1 will be made in class on Monday, September 30, or on the following class meeting day if we run out of time. Now that you know what your assigned project is, your team can start to work on it. In Presentation #1, you will discuss the progress made so far on your team’s mini-project.
Your presentation must cover each of the following, with slides and possibly other things, as appropriate, displayed on the classroom projector. Boldfaced items are discussed in more detail below.
- Title slide at the start of your slide deck.
- General project description, including deliverables.
- Brief description of your MVP.
- Summary of what has been done and challenges encountered.
- Project Kanban board.
- Project repository.
- Demo/mock-up/drawing of your project.
The above items do not need to be covered in the order shown.
Your title slide must include your project name and the names of all team members. So your project needs to have a name. Please keep it concise, clean, and wholesome.
Your Kanban board must be created and managed using some online Kanban tool. It must be properly put together according to the standards we have covered, with a backlog (prioritized!), steps (split appropriately!), done rules, and WIP limits. All team members must have both read and write access to the board. You must be able to display the board on the classroom projector.
It is okay if your done rules and/or WIP limits cannot be handled by the online tool. But these must be stored somewhere, and you must be able to display them on the classroom projector.
The idea is to use the Kanban board when doing the project. So your board must show signs of having been used, and it must be up to date.
Concerning the demo/mock-up/drawing: demonstrate the project, if it has reached a stage where this is possible. If not, then show a mock-up or prototype, if you can. Otherwise, you must show a drawing or something similar indicating what your project looks like and/or how it is intended to work. If your project has no visual elements—for example, if it is a library wrapper—then show something that indicates how your project works or is used, perhaps a diagram of some kind and/or sample code that uses your project.
In Presentation #1 you are not required to display an architecture diagram or a testing plan. However, you may display these, if you wish. For this project, a testing plan is not a formal document; simply indicate how you plan to test your work.
Grading & Feedback
Grading and feedback for this presentation will be handled as for Mini-Project Presentation #0. That is, each student will receive full credit if their team gives an organized presentation covering everything required, they are present for the entire presentation and do a substantial portion of the speaking, and they appear to be making a good-faith effort to follow announced standards and take previous feedback into account.
Some feedback on speaking style, slides, etc. will be given live, at the time of the presentation.
Thoughts
Once again:
- Do not use more slides than are needed.
- You are not there to read your slides, but to explain and elaborate on them. List key points on the slides, then discuss them in whatever detail is necessary.
- Speak up, speak clearly, make eye contact with your audience, be reasonably animated, be organized.
- Plan the logistics of your presentation in advance. Who is going to start things out? What will each team member speak about? Who runs the computer?
- Be prepared for questions and discussion. When you are done with your slides, you are not done.