Game Career Guide is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Get the latest Education e-news
 
  • Captain Starshot: A Team Lead's Takeaway

    [07.02.19]
    - Nick Guilliams
  • Context

    Before I get to the actual interesting stuff I need to give you some context so that you can actually understand why certain things were more difficult than they needed to be.

    Together with a team consisting of 22 multi-disciplinary student developers we created a free game called ‘Captain Starshot' over the course of 32 weeks with 4 working days each. This game was created in function of Breda University of Applied Sciences as a year long project.

    I was the producer throughout the entire development process. This included concepting, pre production, production and post production

    Because we were working as students in a university we were forced to work in a flat hierarchy. Not because of any hard set rules but simply because of assumptions, desires and goals from every person involved in the endeavor. Here are some of the issues the team was tested with:

    • Attendance

    • Trust

    • Skill difference

    • Management, planning and structure

    • Communication

    At the beginning of the year we were given a project brief and were expected to make something of it. People that know each other and may or may not have worked together in the past were slammed in one team with the hope that it would work out. Concepting, procedures, rules,... nothing was defined and everything started at the same time.

    I will try to give you a production/management/lead perspective in case you are in a similar position that it might give you some inspiration and improve your team.


    Struggles

    In any team there will be difficulties. Company structure, titles and rules are usually what give teams structure. However in our case there was no predetermined structure, no official titles and the rules were extremely limited.

    Somehow a team of peers had to figure out what the best course was for a year long creative project that included software development, artistic art stuff and user experience design. No one that officially had more skill or authority for any of the disciplines. 

    So what did we do to make it work? 

Comments

comments powered by Disqus