SE361 R1 Project Presentation

Team / Instructor
Date / Identification R1

Presentation

Category / 1 / 2 / 3 / 4 / 5 / Rating
General Mechanics / Team completely unprepared. Several topics not covered. / Team unprepared, unable to set-up in a timely manner. Some topics missed. / Some lack of flow. Team fumbles at start. Evidence of poor preparation. / Presentation flows reasonably well, each team member prepared. / Presentation flows very well, evidence that team rehearsed ahead of time.
Delivery / Presenter simply reads the slides, or is completely incomprehensible / Presenters mumbles, incorrectly pronounces terms, and speaks too quietly for those in the back to hear. / Presenters incorrectly pronounce terms. Audience has difficulty hearing presentation. / Presenters speak clearly & loudly enough. Most words are pronounced correctly. / Presenters used clear voice and correct, precise pronunciation of terms.
Participation / Several team members missing. Conflicts within team visible. / One speaker did all the talking, no introductions. One or more team members missing. / Some attempt to have more than one person speak, team introduced. / All team members introduced and participated. / Well-planned allocation of presentation al l team members.
Organization / No organized presentation. Instructor needs to elicit the needed information with questions. / Audience cannot understand presentation because there is no sequence of information. / Audience has difficulty following presentation because it jumps around (disjoint) / Information presented in logical sequence which audience can follow. / Information presented in a logical, interesting sequence which audience can follow.

Demonstration/Project Artifacts

Area

/ 1 / 2 / 3 / 4 / 5 /

Rating

Design Knowledge / Team does not have grasp of information; cannot answer questions about the design. / Team is uncomfortable with information and can only answer basic questions. / Some team members lacking knowledge of parts of the design. / Team is at ease with design, but fails to elaborate. / Team demonstrates full knowledge with explanations and elaboration.
Prototype
Demonstration / No prototype ready to demonstrate. / Prototype fails repeatedly or in several distinct ways. Difficult to work around. / Prototype has minor glitches that can be worked around / Prototype demonstration without failure / Prototype demonstration without failure & team uses test plan to drive demo.
Functionality / Product does not have any significant functionality implemented. / Functionality has no relationship to planned features for this release. / Functionality differs (>2 features) from release plan, includes features not planned for / Functionality matches planned releases with one or two unplanned or unfulfilled functions. / Functionality matches release plan exactly
Design Document / Design document missing or completely useless. / Haphazardly completed, missing or incomplete sections. / Minimal effort at completing document, all sections addressed. / All sections completed, design accurately reflects release contents / All sections completed, design accurately reflects release contents. Design notes thoughtfully completed.
Configuration Management / Inconsistent project structure; lack of configuration management / Project has significant configuration management problems. / Minimal attempt to maintain orderly project structure. / Projects follow configuration management guidelines, proper versioning techniques. / Clean project structure, documents, product code and test code thoughtfully organized.
Source Code / Lack of adherence to coding standards, poor documentation. / Minimal use of coding standards, some attempt at documentation. / Some gaps in adherence to coding standards, poor documentation. / Consistent use of coding standards, reasonable documentation. / Consistent use of coding standards, could easily generate Javadoc documentation.
Testing Artifacts / Product apparently not tested at all. / Test plan not complete, lack of unit tests. / Minimal effort at writing and executing test plans; minimal unit tests. / Test plan complete and results documented, unit tests for most components. / Thorough effort at writing and executing acceptance and unit tests. JUnit set up to support regression testing as required.