Standardized Grading documentation

SCOPE: This ticket applies to all workroles and specializations

Requirement 1: A non-private rubric shall be developed for all graded events.

Requirement 2: A Private set of guidance to evaluators (e.g. eval notes, etc.) on how to apply specifics shall be developed to assist in proper grading across diverse evaluators.

Requirement 3: Both the non-private and private files should be kept as part of a standardized file hierarchy

Requirement 4: Their location, intent and purposes trained as part of SEE training.

Z-0205TM_Banana_Split_Pudding_Part_III.xlsx

In the above example the table in the upper left is the non-private rubric while the notes below and on the right side are the private notes on grading directions.

Additional Guidance: These document formats should be shared with the 39IOS (and other formal trainers/authorities) to identify opportunities for sharing, coordination, plagarization of process. No sense in doing things different.

Generalized Rubric to be built on

Grammer/formatting (minor deductions)
- forgot semicolon
- mispelled variable
- wrong variant (printf vs echo)

Coding quality/Practices (medium deductions)
## Grows over time as these are introduced throughout the lesson(s)
- Sanitizing/checking inputs
- Impelemented error detection/handling
- Commented their code and/or include psuedo

Implementation issues (Major deductions)
## Student unable to accomplish the KSAT's matched to the scenario
- Could not identify appropriate method to solve problem
- Unable to develop logical flow to achieve result