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. ...
Gear Up launched today! Wow...seven years almost to the day since my first book. What took so long? Well, cranking out 250 pages of text, illustrations and doing most of the proofreading on my own took years. I'm proud of the result, but it was a "check off the bucket list item" thing at the time. This book was different. First, let's visit its origin. Developers always ask me “we’re having problems doing X with methodology Y, what should we do?”. My first answer is always “What have you tried?”. I ask this because the best solutions usually come from the people doing the work and experimenting with new practices, not following so-called “best practices”. “Best practices” implies there are none better. Practices will always change as do our players, technology and markets. This leads to experimental practices, where teams explore ways of adapting to change and improving how they work together. Thinking about that original question, I think of al...
Gear Up! Advanced Game Development Practices has 15 practices alone on how to improve the effectiveness and productivity of your iterations/sprints. Burndown your PBIs Measure your daily progress adding features into the game Estimate in Days not Hours If hour estimates are too precise, don’t use them Feature Flow Cards Manage workflow on a cross-discipline feature that requires some hand-offs Fix-it Friday Manage debt by setting aside every Friday to fix, polish and fine tune the game Iteration Reviews Celebrate the amazing accomplishments of the team Priority Status Board Create transparency for iteration priorities Sprint Day Review, retrospect and plan the next sprint in a day! Swim Lanes Create, visualize and track a work category for solving urgent requests The "Done Done" Column Elevate the role of quality in your iterations Th...
Comments
Post a Comment