Status Meetings

  • General status meeting: Fridays at 9
  • Tech group: Tuesdays at 11
  • Design meeting: Mondays at 11
  • Math Content Meeting: Tuesdays at 2

Unless otherwise specified, to join the meeting:

  • ID 122
  • 877-690-2478

See the EventsCalendar.

Meeting Notes


  • Lawyers, contracts, IRBs.
  • IRB
    • Exemption for informed consent for classroom?
  • Grants and stuff
    • SCORM is now not required for (?)
    • Something about DARPA and the health care bill?
  • Development
    • Set up weekly call for
    • Daniel working on test harness and game controller.
    • No HTML game engines yet.
  • Make schedule for Pellissippi testing.
    • Use the google calendar?
    • Which week is which task, etc.
    • Usability testing and design feedback.
  • Design for new games.
  • Planned assessments for knowledge transfer coming soon.


  • CLI new programmer John starts 8/1.
  • More subcontract drama.
  • Discussed math topics documents from Pellissippi.
    • Focus on benchmark fractions:
      • x/2, x/3, x/4, x/10. x/5 is controversial.
    • Don't focus on slightly-off-benchmark fractions like 1/17.


  • Mary
    • Faculty made list of topics. Details coming Monday.
      • Compare fractions, decimals & percents around the benchmark numbers (snowboarding game)
      • Equivalent fractions including unit rates, rate of change and fractions a division (mario)
      • Operations with integers (# line game)
      • Board to # line (equivalent models) (# line game)
      • Equivalent equations (Mario)
      • Order of operations (new maze or train track game)
      • Addition & multiplication of integers (new)
      • Ordered pairs on coordinate plane (new)
      • Is ordered pair a solution? (new)
    • Each of the above bullets would be a "game", with topics inside of them represented as levels.
    • Need student games website up by 8/25.
    • Students play for part of each of 2 lab days per week, for 12-13 weeks.
  • Students play until time limit (20 minutes?) or until they receive a medal.
  • Sequencing:
    • Linear
    • User choice
    • Something smart (not for fall '11)
  • Login mechanics:
    • name + birthday? Or class/teacher + name?
    • Should collect demog data along with IRB consent form, if required.
  • Leaderboards? Competitive aspect is most "game-like".
    • Teacher might not be cool with it. Make it anonymous or show only relative position of the student.
  • Derek demos:


Agenda item: work with Pellissippi to define math goals.

  • CLI:
    • Interviewing programmers.
    • Pelissippi(?) will sending 5-10 content areas to address.
    • E.g. distinguish between signs and operations.
    • Exam questions.
    • 7/26 end of summer program, 8/27 start fall term.
    • Example game controller demo: fluencydemo
  • Ion:
    • Subcontract just needs to be signed.
    • Amanda on board.
    • New space with game lounge.
  • Tiffany:
    • Working on paperwork for contract.
    • Team of students for design once we have content.
  • Derek, Mary, John are out.


  • Still working on subcontracts.
  • Need to define math goals --> Math team.
    • Measurable metrics, assessments?
      • Games will address prerequisites for higher ed assessments, so they won't be directly measurable.
      • Improve performance in Cognitive Tutor.
    • Limiting scope: fluency.
    • Abacus?
    • Need for instruction and not assume students learn methods elsewhere.
    • Paired associate math facts. Strategy vs memorization.
      • More existing games stress memorization. Should teach strategy.
    • Tradeoffs between broad frameworks that cover a large domain area vs specific games that teach narrow domains better.


  • Grant evaluator visit the second week of August. Who can come to Pittsburgh for that?
  • Demos!
    • Tiffany demoed games from a summer program at UNCC:
    • Ion presented games from NYU:
      • Games for middle school-aged girls. Identity formation.
      • Simulations, such as model of diffusion. Looked at highly-vs-less guided instruction and executive control.
      • Solo vs competitive vs collaborative game play.
      • geometric transformations.
      • Use of eye tracking and other sensors to validate in-game measures.