​​Project: Home Base

Role: Producer

Team Size: Core Leads 4, Total 13

• What is it?

  • Client work for Scholastic (Book Publishing) on their MMO games and reading engagement platform Home Base. As of writing, the project is 5 years old and has 10,000 active users (across PC, Mac, Web, iOS, and Android). Home Base is an ongoing engagement tool where players can read/listen to books (frequently updated), play minigames, interact with characters from books, and islands based on book series’/brands, create avatars, win prizes (often clothing/trophies), receive notifications, post comments and custom content, live events with authors, and join groups/classes (circles) for tracking updates communication.

  • It was made in Unity (front end) for all of the content and platform itself, with a backend handling data and moderation.

• Process to Completion / What I do?

  • Typically featured monthly updates of content updates (books and their podiums, clothing and furniture for player avatars, bug fixes) with small to medium-size feature updates/inclusions.

  • Scholastic would request these updates and when they would like them delivered, and it would be on me to organise the resources and scope for them to be achieved.

  • Communication (outside of Trello, Slack, Email) was two Weekly meetings: and Scholastic Sync with ​Scholastic Games Project Coordinator, Scholastic Digital Product Director, and BFS Home Base the core team leads, as well as a Dev Sycn/Check-in. 

• My Contribution

  • Active from early ​​​​2022 to present.

  • BAU

    • Release tracking

    • Release planning and budgeting (people hours) of staff for release.

    • Feature book covers blender

    • Meetings (Internal/External), board groom, internal presentations, 

    • Resource limitations and Feature solutions with client and team.

    • Timeline and deadline reminders (it would be remiss to not mention this!)

    • Release documentation and priority bug tracking

    • Build delivery

    • Scoping and Implementing larger features/additions to game

    • Studio Documentation within Notion

  • Software Used 

    • Notion

    • Miro

    • Source Tree

    • Insomnia

    • Community Sift

    • Gitlab​

​

Project: Virtual Book Fairs

Role: Producer

Team Size: Core Leads 2, Total 4

• What is it?

  • Client work for Scholastic (Book Publishing) for their digital alternative to School Fairs created during the 2020 Covid Pandemic when visiting schools was not possible. Users could use both a VR and a web browser. Users could explore different sections of a book fair (divided by reading level), and the books and videos on display here. A parent/teacher and student version was made (one featured links to purchases, and the other didn't).

• Process to Completion / What I do?

  • Production involved quarterly updates with no additional programming or functional changes. All new content (Art, prices, book information, display videos) was substituted in Pano2VR then uploaded to the server using Cyber duck.

  • My role was to review all the upcoming materials from the client, and input or request them as needed. I would also need to request of our art team new changes to the interactive shell (the 'gymnasium') as needed. I would then add them to the PanoVR file (or remove/substitute if not available).

• My Contribution​

  • Active for fall ​​​​2022.

  • BAU

    • Editing interactive tags and book information​

    • Conforming files

    • Coordinating between Scholastic, BFS Art Team, and Scholastic Technical Services

  • Software Used 

    • PanoVR2

    • CyberDuck

    • SourceTree

​

Project: MotoGP Guru

Role: Producer

Team Size: Core Leads 7, Total 15+ 

• What is it?

  • A partnership between Animoca (BFS), Gryfyn, We.Play, Dorna to create a prediction tool for the Moto GP Championship. The goal was to utilsie the Gryfyn wallet for quick signup/login and engagement with crypto and NFTs, using the simultaneous engagement of prediction of outcomes of races on MotoGP as the gameplay and means for the stakes.

• Process to Completion / What I do?

  •  Gryfyn (purchased by Animoca) was sponsoring the Circuito de Jerez, and We.Play was hired to incorporate a means of engagement with the wallet. BFS was utilised for Production (myself), Art, and Design.  

  • Oversaw and assisted with UX and UI design.

  • Converted ideas of Creative Director into an actionable workload, and oversaw both the BFS (UX and UI) and We.Play (Development and additional UI) teams.

  • Challenges

    • Gryfyn wallet was not ready until close to event.

    • Extremely tight deadline

    • Making a waterfall production model as (micro level) iterative as possible.

    • Managing different work (and overtime) expectations of the Managing Director, Spanish/Polish development team, Australian UX/UI teams, and American/Singapore UI teams. ​

    • Localisation ​​

• My Contribution​

  • Development was from Feb to May 2023.​

  • BAU

    • Regular meetings across 4 time zones

    • UX/UI Document reviews

    • Expectation setting

  • Software Used 

    • Figma

​​

Other Things That Happened!

• Pitch decks (x2)  

  • Ideation and collaboration with leads and MD

  • Alignment with parent company (Animoca) and external clients

• Studio utilization live spreadsheet

  • Staff limitations and overview needed

  • Collate data in master sheet (live) from individual project using query formula staff utilisations managed by producers.

​