Drawing upon 15 years’ experience making serious learning and assessment games for external customers, the presenter will discuss common mistakes organizations have made (or allowed their developers to make) in the procurement, design, development, and employment of serious games. Strategies for overcoming these issues will be shared to prepare stakeholders to lead successful serious game initiatives. The presentation will conclude with a discussion session where attendees will be encouraged to share their questions and experiences related to serious game efforts.
2. Custom serious game for client
Developed by a game creation partner
Highlights across all phases of a project
Driven by MY observations and experiences
http://www.experimentswithsuccess.com
3. Procurement
Design
Development
Employment
PreSolicit
/ RFP
Kickoff Design Develop Test Deliver
9. They are cool, but why?
Learning and assessment with:
◦ Engagement
◦ Repeated practice
◦ Record of behavior
◦ Authentic experience and environments
◦ Sense of organizational loyalty
Requirements
10. During pre-procurement many have input:
◦ Management
◦ Customers (Internal or External)
◦ Information Technology
◦ Human Resources
◦ Training and development
◦ Marketing
More perspectives are great
More requirements, not always
Requirements
11. Visual quality ≠ training fidelity
Platform capabilities should meet needs
Integration must be supportable
Accessibility
Ensure your budget supports requirements
Focus on the need and desired outcomes
Requirements
12. Must be in line with needs / expectations
Secret to getting a top developer
Requirementshttp://lifevesting.com
13. What are you really buying?
Goal is to select a team
◦ You can trust
◦ Feel comfortable working with
◦ Can minimize the risks
Share fixed budgets, timeframes, or scope
*Similar idea for general software development in Finding a Partner to Trust:
The Agile RFP, by Peter Stevens
Solicitation
14. Talk to bidders
Incorporate orals
Ask about process and products
Define resources
Ask what is expected of you
Support required integration
Ongoing maintenance / help desk
Provide “big picture”
Solicitation
18. Developer and customer are a team
Customer provides dedicated resources
Clearly define roles and responsibilities
Kickoff
19. High level definition of problem
Separate management and design meetings
Mutually agree upon schedules
Define approval and change process
Kickoff
34. Pilot/soft launch
Push with a marketing campaign
Support other vendors or internal cost centers
Have a plan for the data produced
Plan for maintenance
◦ Content
◦ Technology
Launch & Beyond
International Serious Play Awards https://seriousplayconf.com/about-spcsga/
Serious Game Showcase and Challenge Finalists http://sgschallenge.com/wordpress/
Training Industry listing https://www.trainingindustry.com/learning-communities/serious-games-and-simulation.aspx