Get the latest Education e-news
 
  • Learn By Doing: The Auxilium Postmortem

    [05.08.18]
    - Justin Gibbs

  • What went wrong

    • We didn't grok POCT
    • Didn't have a clear end goal
    • Ill-defined roles
    • Documentation
    • Stakeholders and project lead communication
    • Strong identity, weak culture
    • Lack of trust
    • 4 sub-teams
    • Poor sprint planning
    • Non-existent product backlog
    • Lack of agile fundamentals
    • Learned bad habits in boot camps

    Takeaway:

    Our biggest pitfall was our lack of agile fundamentals. This was apparent in our poor scrum hygiene, lack of a product backlog, and incomplete sprint planning. In the beginning of the project we became so distracted with the most immediate issues on our team that we forgot our agile training. The problem was across the whole team, as nobody realized until far too late in the project that we were not performing some of the agile fundamentals.

    The lack of a product backlog was due to an undefined direction to the game, and made our sprint planning much more difficult as we had to start our planning from scratch every sprint. When our sprint plans became rushed and incomplete, that had an effect on the scrum meetings as some people were unsure what they were doing day-to-day. All of these problems served to slow down our development cycle and prevented us from making something stellar, but provided us with excellent learning opportunities.

    What we learned

    • Realize POCT is about risk mitigation, not R&D
    • Develop a clearer vision in preproduction
    • Use RACI to define roles early, revisit constantly
    • Validate understanding/comprehension by leads/producers from stakeholders
    • Work on holding each other accountable to team standards
    • Organize the team by discipline and function, hold people accountable
    • T.b., accountability, culture + time (what does this mean?)

    Takeaway:

    "Trust but verify" is a phrase we learned to echo at the end of Auxilium. Simply, it means that it is okay to trust that someone else is doing something, but it is your responsibility to follow up with them and make sure everyone is on the same page. If we had followed this thought process from the beginning, we would have caught several of our classic software development mistakes before they derailed our project.

    Two instances where this would have been helpful would be with understanding the roles of the individual on each of our sub-teams. Throughout the project there were people that thought someone else was working on a task when they were not. Following up with the person would have alleviated that problem on the spot. Additionally, we had a miscommunication with the stakeholders about the definition of our proof of concept: technology milestone. We thought we were expected to research solutions to risks, but were informed in a regrettable milestone presentation that we were supposed to be mitigating those risks and delivering solutions.

    Our milestone could have been saved if we had verified our assumptions with the stakeholders at the beginning of the sprint. This goes to show the power that "trust but verify" holds in a game development context, and it would be one of the most important lessons we would learn from Auxilium.

Comments

comments powered by Disqus