Today we read and discuss Roman Voting. This is a quick and fun way to get a feel for what the team is thinking of an idea, or the current project. Check out the video below for the reading!
Summary - Some practices are meant to catch problems before they get too far. Don't make the mistake of having these practices humiliate or punish people. Assume they are human, didn't mean it and have some shared laughs. --- The practices collected in Gear Up! come from decades of experience, some painful, some that turned out fun in the long run. One such practice called “Lighten the Mood” came from the development of Midtown Madness in the late nineties at Angel Studios when we were struggling to keep the game from being continually broken. Often when a commit breaks a game, it's because someone ignored established testing practices. We didn’t have extensive build testing automation then. We had a dedicated PC, the “build monkey,” where any change committed had to be tested separately following every commit. Verifying the build on the build monkey could be a tedious task. Some people occasionally found excuses to skip it, sometimes to the detriment of the team. ...
By Grant Shonkwiler Hello again friends, today we read and discuss the Silent Hour practice from Gear Up! This practice has served me well on all types of teams, from small to large, this practice allows for the team to really focus on work for a good hour a day. It's all about providing time for people to enter and stay in flow. Gear Up! Advanced Game Development Practices
Often, large groups are hesitant to roll out change. I recently visited a team that releases a large sports title every year. The title always does well in the market, but it comes at the end of months of crunch and compromise. They know it needs to change, but doing something that would cause them to miss their sport's season start would be disastrous. I recommended a practice from Gear Up! Advanced Game Development Practices , called "Beachhead a New Practice", included below. ---- Beachhead a New Practice Most practice improvements are small and incremental, but sometimes bigger, more risky leaps are what is needed. It’s even riskier when you ask the entire studio to make the change at once. Examples of such changes could be: Reseating teams into an open cross-discipline space Adopting unit testing and continuous integration Pairing on all or most of the work Swapping out a major part of an asset production pipeline Beachheading is named after the mi...
Comments
Post a Comment