Assessment Framework

From CIRCA

Jump to: navigation, search
VTracker
Content deleted. (132 Occurances)
Content stucture deleted. (55 Occurances)
Content inserted. (47 Occurances)
Content structure inserted. (41 Occurances)
Content structure deleted. (10 Occurances)
Content changed. (13 Occurances)
Content moved. (29 Occurances)
Content NEED DESCRIPTION. (11 Occurances)
Content NEED DESCRIPTION. (13 Occurances)
Content structure moved. (3 Occurances)
Content NEED DESCRIPTION. (2 Occurances)
Content of a table reordered. (1 Occurances)
Content style of a font changed. (26 Occurances)

The GRAND Assessment Framework';this.style.color = '#ff0000';" onMouseOut = "this.innerHTML = 'GRAND Assessment Framework';this.style.color = '#000000';">GRAND Assessment Framework is an iterative assessment framework designed by the University of Alberta GRAND group. The framework starts with the assumption that the group research project involves practical game design, and continues by attempting to ask the most significant over-arching questions.

Use these question categories in the process of answering your own questions relevant to a specific project.Fill in category sub-questions as best you can, add your own or skip questions as needed.The framework is intended to help game designers and researchers articulate their points (and what those points are in the first place), create a foundation for further work, and to suggest a set of possible methods for that may be of use during that particular part of the design process. Fill in category sub-questions as best you can, and add your own or skip questions as needed.

Contents

*

**

*1.61.0 Stakeholders and Expectations

  • *

*

Stakeholders defined*
  • 1.1 What's the point of the project?
    • *
    • *
    • *
    • *
    • *
  • 1.2 Who are the interested parties in this project?
    • *
    • *
    • *
    • *
  • *
  • 1.3 What does each stakeholder get out of the project?
  • 1.4 How will you prioritize the needs of stakeholders?
    • *
    • *
  • *
  • *
    • *
    • *
    • *
    • *
    • *
    • *
    • *
    • *
    • *
    • *
    • *
    • *
    • *
    • *
    • *
    • *
    • *
    • *

2.12.0 returning group membersRequirements

  • *
  • *
  • *
  • *
    • 2.1 What is the primary purpose of the project?
  • *
    • *2.2 What evidence would indicate success? How will you know it is over?
    • 2.3 How will interested parties discuss the project as itevolves?
      • *
    • *
    • 2.4 Is there a project charter agreed among stakeholders that makes clear what is expected of everyone?

    3.0 Resources

    • *What technology or tools are required to build, maintain, and play the game?3.1 What resources are required to do the project?
    • *
      • *
      3.2 How will you get the required resources?
    • 3.3 How will you account to stakeholders for the resources they have provided?
    • *
        How will you rank or sort stakeholders? 3.4 How will you deal with the loss of resources?

      4.0 Planning

      • *4.1 Is there a project plan? Does it include the level of detail needed?
      • *Is there a deadline? Or can this project be delayed?4.2 Is there a method for tracking progress regularly?
      • *4.3 How will the plan be adapted if you fall behind or lose resources?

      5.0 Design

      • 5.1 What design process will work best for this project?
      • *5.2 How can you assess the design process?

      *

      • *
        • *
          • *
        • *
      • 5.3 Which resources are needed to develop the game?
      • 5.4 Does the game meet your goals? Are there unexpectedproblems?
      • *
      • *
      • 5.5 Are there ways to improve the game or the platform based onthe results of this attempt?
      • *
        • *

        6.0 Delivery

        *
        • 6.1 How will you deliver the product to your audience?
        • *
          • *
      • *
      • *
        • *Who did the game work for (or not work for)? 6.2 How will they become aware of your project?
      • *
      • *
        • *How quickly will the target audience be able to learn the game?6.3 How will you train the audience to understand and play the game?

        *

        *7.0 Feedback

        *

        *

        100*
        • *7.1 What feedback do you and your stakeholders want and from who?
        12*11*10*9*7*7*7*7*6*5*5*4*3*2*1*0**
        • *Can we tweak the game during deployment? Is this a part of the plan?7.2 How does the game work for players? What is their experience?
        • 7.3 How will reports from the players or other stakeholders be handled?

        *

      • *
      • *
      • *(Not all of our games are designed to be serious games - this is a better question for the assessment section for specific games, will not apply to all projects)
        • *7.4 Can we provide feedback to encourage player engagement with the game?
        *This question is very broad, I'm not sure what it means and how it is different from resources section - needs to be defined better or broken up into sub questions)*
        • *7.5 How can feedback influence further design?

        *8.0 Closure

        • Intellectual Property:*What was the educational value of the project?8.1 What will the end-state of the project look like?
        • Time and Money:*Comparison and Competition:*

        *

        *

        • *8.2 Does the game meet its goals? How do you know that?

        *

        • *8.3 How will you know if stakeholders are satisfied?

        *

        • *(I think this document is supposed to be less a 'how to' guide and more of a check list/framework for doing the theoretical and technical research and implementation. Perhaps we can start a page of solid design 'how to' resources elsewhere on the wiki)8.4 Have you communicated to all interested parties that the project is over?

        Related Wiki Resources

        Personal tools