Market Money Feedback Session (Eval)

Back to Market Money Home

Presentation

For the project evaluation, each project team should prepare a 10 minute video presentation. Presentations longer than 10 minutes will not be reviewed and sent back for revision. Your presentation should cover the following points:

• Demonstration of functionality via Postman suites
• Technical quality and organization of the code, identifying code that should be refactored and how it would be refactored
• Running your application’s test suite and a discussion of test coverage (happy/sad paths and any edge cases)
• Identifying the area(s) of code of which you are most proud, and an area where you would like specific feedback

All team members are expected to participate equally in the presentation. Students should focus on practicing technical communication that is succinct and utilizes appropriate technical vocabulary.

Slides are not required, but encouraged as a way to facilitate the presentation along with sharing specific code examples.

Instructors will review the video presentation and do a brief code review (so please make sure you identify an area you’d like feedback in your video, so we can focus where you’d like it most). Scores and final comments will be sent to teams via Slack.

Rubric

Your project will be evaluated based on the following rubric:

Feature Delivery

• Exceeds Expectations: Project completes all requirements and at least two extensions.
• Meets Expectations: Project completes all requirements
• Below Expectations: Project fails to complete 1 - 2 required endpoints
• Well Below Expectations: Project fails to complete more than 3 or more endpoints

Test Driven Development

• Exceeds Expectations: Project achieves 100% test coverage at the unit and integration levels. The tests include sad path and edge case testing.
• Meets Expectations: Project achieves greater than 90% test coverage
• Below Expectations: Project achieves greater than 80% test coverage
• Well Below Expectations: Project does not have 80% test coverage.

Technical Quality

• Exceeds Expectations: Project demonstrates exceptionally well factored code.
• Meets Expectations: Project demonstrates solid code quality, MVC principles, and uses a serializer for formatting JSON responses.
• Below Expectations: Project demonstrates some gaps in code quality and/or application of MVC principles.
• Well Below Expectations: Project demonstrates poor factoring and/or understanding of MVC.