Collegiate Starleague

The best place to play eSports on Campus
The Problem

Collegiate StarLeague (CSL) had originally been built by an assortment of developers and designers. Most of the league and season generation was operated through manaul jobs that an engineer had to execute against the production database. Season registration was handled through email, PayPal, and managed in a spreadsheet. Before starting the project, we ran the codebase through code climate and it received a score below 0.9/4.0.

The Personas

Alan, the Admin

Alan manages season registration, season generation, and match reporting for 5 games on CSL. That is anywhere from 500-1,000 teams in any given season. Alan is a full-time grad student, gamer, and dog lover.

Chris, the Team Coordinator

Chris coordinates the Berkeley Legends, the Division 1, League of Legends team at UC Berkeley. Chris is a full-time pre-med student, when he is not studying he can be found watching his favorite players on Twitch, coordinating practice sessions, or playing his two favorite games LoL and Overwatch.

The Solution
  • Automate season generation
  • Integrate with a payment processor
  • Automate season registration
  • Improve work flow of match reporting for coordinators
  • Give coordinators a way to contact eachother on match days
Key Takeaways

Because the Code Climate score was so low, we opted to do an entire site rebuild. By the end of the engagement our Code Climate score was at a 3.8/4.0. A huge improvement.

Coaching the Product Owner on the importance of user research was extremely difficult on this project. We asked him to sit in and observe 3 sessions, and by the end of the final session, he completely understood why user research and usability testing are important and even added it to the happy column in our weekly retrospective. We are working on integrating these insights into our next engagement with CSL.