There seems to be a growing impression among the serious game design community that Assessment and Evaluation are interchangeable terms. They are not.
Assessment applies to learners/players. Before or as a learner is introduced to an intervention (in our case, a serious game), s/he should be given an opportunity to determine whether s/he is really "ready" to move ahead. By "ready," we mean that s/he has the skills and/or knowledge necessary to proceed successfully. Designing the activities that offer this pre-assessment ("pre-" because it occurs prior to beginning the game) is an important part of the serious game designer's job; the activities themselves should, in form and format, reflect the game itself, and should offer appropriate feedback and remediation to the player who needs additional instruction or assistance.
At the conclusion of the game experience, learners/players are given another opportunity to demonstrate skills and/or knowledge, this time focusing on the intended outcome of the game. We call this "post-assessment" for obvious reasons.
Evaluation, on the other hand, looks at the overall effectiveness of the intervention. During the evaluation phase, we ask ourselves questions like: Does the game achieve its goals? Are learners learning what they're supposed to? Are they motivated by their experience? Are the actual costs of development in line with projections? Was the project completed on time?
As with assessment, evaluation is not just a post-project implementation activity. Evaluation is a critical alpha and beta activity as well, allowing designers to tweak and improve game design and other program implementation elements prior to full deployment.
In the most stark terms possible, then, assessment measures the progress and achievement of learners (them). Evaluation measures the effectiveness of the design and its implementation - in other words, us.
I'm serious,
Anne