Pharmacy Skill Challenge 2018

began sound sourcing usable sounds for elements of the prototype. 

majority of sounds found from zapsplat.com

sounds require trimming and slight alteration

The prototype is behind schedule

Plans for playtesting

Broderick Playtest Leader

Organise playtest script

Google forms

Aim to get the prototype finished over the holidays

Next team meeting 24/09/18

Assigned Tasks for the next sprint

Request access to pharmacy labs for video presentation

Broderick

Questions regarding turning the GDD into an extended proposal. 

focus on the development team

what we’ve tried to implement 

what is viable

Brandon

Questions regarding the visual style of game elements

Questions regarding which information is most important to display in the skill tester game.

Reassignment of some task from Dan to myself

Discussion about topics to discuss with Esther on monday

Broderick:

Audio has been reassigned from Dan to Broderick

Overlook GDD, make sure it all flows

Detail one distraction for Patrick to prototype

Work with Brandon to make it consistent

This research paper aims to review educational games used in pharmacy schools to aid in learning.

The main points taken from this paper were the rules and challenges, which students had to adapt too. and also that all games focus on solely testing a students knowledge and abilities but not how they would apply them in a real-world setting.

Added proposal to the overview section of the GDD.

Link

The proposal is an outline of the area, why it is important, and what our proposed plans are.

Original Proposal: serious skill tester with distractions and game-like elements

Updated Proposal: A pharmacy game, that is fun and engaging for students.

Reasoning: Mentor team would like a product which students can be motivated to access on their own. 

Key Deliverables:

Prototype Game

1 Main Skill task 

2 Distractions

Feedback and Scoring System

Demo video

GDD

Discussion with the teaching team to give the team a better understanding of our direction and deliverables

Project deliverables

Primary Artefact

Supporting Document(s)

Summary Document (sub 1000w)

README file for game

Week 13 (Friday 26th Oct)

Patrick sent an email to Esther about meetings

Allocated tasks for the following week

Broderick

Refine Overview section of GDD

Transition Overview to extended proposal

Review GDD document for where else extended proposal aspect can be implemented

Start and complete Formal Elements of GDD

link

Overview section of the GDD

Creation of a shared assets document was one of the outcomes of our team meeting.

Duration: 1hr 10mins

Notes

Summary

Email to mentors to organise another mentor meeting

plans for next week

Confirm direction with the teaching team

Deb wants innovation focussed 

Dan fine with mentor team approach

Continue work on shared asset list

helps convey thoughts and ideas to mentors

Workshop notes

Summary:

Workshop activities involved information on creating a hypothesis and validation charts

Notes from teaching team:

Louis 

Hypothesis driven approach

Design the game based on client brief and feedback

Dan

Game is innovative in its field

ok to look at innovation in a non game approach

Cross-reliance in the team for innovation

Team concerns:

aim for a research approach

currently a dev project rather than research project

Mentors want a GDD with demo

negates the potential of a hypothesis driven approach

This is a draft project timeline (subject to change)

The following is a rough project timeline

Week 3-4 Initial Design Phase

Confirm design requirements with mentor team

Identify when roles members are filling for project

Receive and analyse required tasks and distractions from mentors

Research other education/pharmacy games

Week 5-6 Design and Complete GDD

Formalise tasks and distractions into document

Use game theory to justify gamified implementation

Generate more examples of gameplay scenarios (though not implementable)

Week 6-12 Prototype of Development

Have mentors organise access to HTC Vive

Implement design detailed in GDD

Iterate GDD based on internal feedback

Move designers to playtesting role

Week 11-13 Playtest Prototype

Playtest with ideally first year pharmacy students provided by mentors

Meeting Duration - 1hr

Initial meeting to discuss our expectations of the project along with our mentor's expectations for the project.

Notes

Summary of Meeting

Example project

Pharmasee

Mentors thoughts on the balance between a fun or serious experience

Fun like Job Simulator but more formal and more direction

Mentor expectations on outputs

Fleshed out GDD 

Low-fi Prototype

Pharmaceutical-related tasks to be implemented

Mentors ok with a Demo level output

Other aspects that need to be tested

Students need to be able to use outside of class

Meeting Duration - 2hrs

Notes

Summary of Meeting 

Background on Mentors

Ideation for design solutions

Questions for mentors

Validate your solution

Research into dealing with distractions

The University of Sussex (Dealing with Distractions)

Tips for Dealing with Distractions

Research

Pharmacy Simulator

More focused on dealing with different customers and scenarios

Provide advice to virtual customers

Set dialogue options, obvious choices

Doesn’t deal with distractions

Doesn’t seem to deal with the actual process (checking scripts, collecting medication, etc.)

Designing of Game-Based Learning Framework for Training Pharmacy Students