Game Production Blog

Chapter 10 is about agile technology, as its title implies. One of the first points the chapter covers is that the author was given an 80 page document detailing all the features the tool he was developing, which came as a surprise to him. It allowed the artists to detail what they needed, rather than leaving it up to him to figure out what the artists needed. However, the artists ended up not finding much use in the tool, as they didn't have the foresight to know what they wanted. Agile programming aims to fix this problem. Later in the chapter, it goes into detail on Extreme Programming, or XP, and its advantages and disadvantages. Chapter 11 involves the use of agile methodologies for art and audio. Audio in particular I find to be an interesting subject in this regard, as the book mentions that the audio team is often delegated to doing work at the end. In my opinion, it would make more sense to develop the audio at the same time as everything else (which would be more natur...

Reading: Chapter 3 of the book covers how Scrum came to be in the modern era, what team roles are and how they should be allocated, and the core principles of what Scrum is.. The history in particular is fairly interesting. In the early 1900's, factories were synonymous with dehumanization. They required humans to become robots, working on a factory line with no input of their own. Following World War II, however, this began to slowly change, and finally in the past few decades, the concepts of Scrum started to arise. Scrum's principles include details such as Empiricism, Emergence, Time Boxing, Prioritization, and Self Organization. These are accomplished through Sprints, which are explained in more detail in Chapter 4. The team role that stuck out to me most was the Scrum Master. The Scrum Master is the one that encourages the team and does everything he or she can to make sure they succeed. This includes being stubborn enough to make sure the Scrum processes always go t...