Total mark: 65 / 80
Component | Mark | Out of |
---|---|---|
Logical flow of the demo | 6 | 6 |
Using good slides, diagrams and/or any other visual aids | 4 | 4 |
Answering questions clearly | 4 | 4 |
Overall quality of presentation | 6 | 6 |
Total | 20 | 20 |
- Would have been nice to start with a quick intro (1-3 sentences).
- Many good features: Subscription (with UI indication), email notification, sending an email digest (to avoid spam), tagging topics (to allow convenient search), responsive design.
- Good description of the process, and answer to the question about limiting work in progress (I am glad to hear that you did use something that didn't work well for you team).
- Great description of the choice of tools (Django and Bootstrap), and a clear high-level explanation of what these tools are.
This was important, since your application's architecture was pretty much determined by the tools that you chose. - Overall, great job!
Component | Mark | Out of |
---|---|---|
Product quality | 7 | 7 |
Supporting arguments for decisions, and clear explanations | 2 | 8 |
Overall presentation | 5 | 5 |
Total | 14 | 20 |
Component | Mark | Out of |
---|---|---|
Mentioning things that worked well | 2 | 2 |
Mentioning things that didn't work well | 2 | 2 |
Describing the team's ideal process | 5 | 5 |
Supporting arguments for decisions, and clear explanations | 7 | 7 |
Overall presentation | 3 | 4 |
Total | 19 | 20 |
Component | Mark | Out of |
---|---|---|
Clear high level description | 6 | 8 |
Describing significant decision(s) | 2 | 6 |
Overall presentation | 4 | 6 |
Total | 12 | 20 |
Comments Product
- No supporting arguments for choosing features you decided to work on. (-6)
Process
- Missing some links to issues or interesting statistics. (-1)
Architecture
- No reason for choosing Django. (-2)
- Almost no descriptions on significant decisions you have made. (-4)
- Missing diagram or any visual aid. (-2)