Moving, Loss of Computer, and Reminiscing on the Past

Sorry for the lack of blogs recently. I recently moved out of my place and I'm looking for a new one. As is the case, I've clearly decided to change EVERY FACET of my life.

I guess the fates have the same idea for me as well. My computer completely died this weekend. So, if there is a bit of delay on other post I'm apologizing in advance. I'll need a bit more time to finish up PART 2 of Project Management Programs and YOU! since Part 2 is about the search for a good program. In the meantime, I wanted to give a bit of history as to how I even got into the industry and how I became a producer.

Brace yourself, this is a longer blog post.
                                                                                                                                                  

I was 18 when I first got into the industry. A big eyed and bushy-tailed kid fresh out of high school with no idea what he wanted to do with his life. I had an amazing teacher at Newport Harbor named Mr. (Dr. now) Naaz who taught psychology, and my mother also went to school for psychology, so I thought that it was a natural fit for me to see about going to school for Psychology and seeing what kind of job I could get with that degree.

I couldn't afford one of those big wig UNIVERSITIES so I started going to the local college near me. It was there and 6 additional months when I realized that I wasn't cut out to be going for another 8 years. I knew that I had to do something, and it had to be something that I would enjoy for a long, long time.

Honestly, there weren't a lot of things that I really enjoyed doing, nor were there a lot of things that I was generally good at. I was always the kid that was "ok" at everything, but never excelled at anything. I am a decent writer, an ok photographer, terrible artist, not a strong swimmer and I wasn't tall enough for basketball. But one thing I was always pretty good at was people and playing lots and lots of games. Ever since me and my siblings were younger we played tons of games. From Commando and Zelda on the NES, to all the Final Fantasy games, to WWF games, GoldenEye, Perfect Dark, Rush 2049, Super Smash Brothers, Chrono Trigger, Tomb Raider, Thief, and Super Mario, I played games. I thought that gaming wouldn't be a bad idea to try.

I searched through the various ads online and found a local hiring agency that had Quality Assurance positions for a local publisher named Crave Entertainment. It had recently moved to Newport Beach and was in need of new testers for their upcoming release, World Championship Poker II Featuring Howard Lederer. I applied and almost immediately got the position. I didn't even know what the job of a tester was, but I knew it would at least give me an idea of what the industry was all about.

I didn't have a car at the time, so responsible Alvin took the day before riding on the bus to see what the best way would be to get to the office on time. The first day I was about 30 minutes early, and there was no one there, so I waited outside until my lead came up. He introduced himself and opened up the back door (seems I went through the wrong door).

Crave was a small place, mostly marketing people, actually. The gaming division was in the small cubicles off to the side, with 2 or 3 producers overseeing all of the projects that were in the pipeline. The QA was spread out in 3 different areas, each working on different games. It was probably the strangest thing that I had ever seen. People were just sitting with these strange looking versions of PS2's and PSP's and playing games. Just sitting and playing games. It made no sense to me but I loved it. It seemed awesome.

There was a large room off to the side where my seat was. There were about 10-12 PS2 dev kits and one computer where folks would write up all of the bugs that were found throughout the day. My lead introduced me to the various people that I would be working with, then showed me to my seat and console. After finding out that I have never done QA before, he went through a pretty brief synopsis of what a tester does. "Find any issue that you wouldn't want to find if you were an end-user and mark it in our database." Seemed pretty simple to me so I just started playing the game. It was a strange thing to do, to sit and just play a game and look for bugs. I was always the kind of person to try some strange stuff in games, and always see what would happen if I did something rather strange when playing games, so I ended up picking it up pretty quickly and grew to one of the better testers there. I also got pretty good a poker. :)

After being there for about 6 months, I realized that there was a definite ceiling there, and they were looking to cut a number of people, so I started looking for other places. I didn't really know how to find companies that were near, so I just started looking at all of the game boxes that I had and searched to see where they were located. One of the first ones that I looked at was Obsidian Entertainment. And look at that, they were in Irvine, not too far from me! I quickly put in my application, hoping that my 6 month experience would be enough to land me a gig there. I got a call pretty quickly, asking me to come in for an interview. I still didn't have a car at the time, so again I took a day before and scoped out the place to ensure I would be there on time. I knew that this place was going to be very different from Crave, so I wanted to make sure that I looked pretty good for the interview.

I'm pretty sure I wore slacks, a long sleeve shirt, took a notepad, and got on the bus and made it there 45 minutes early. The receptionist had me wait in the lobby for awhile while the Producer and Lead Tester came back from lunch. They introduced themselves and took me to the Producer's office, where they asked me about my resume, how it was working at Crave, and what kind of games I played. My interview at Crave (or lack thereof) was different, but this had to have been the strangest one I've ever been in. I'm never been so comfortable in an interview, just essentially shooting the shit, talking about games.

I figured that after such a strange interview I definitely didn't get the job, but, they asked me if I wanted the position pretty quickly afterwards. I ALMOST didn't take it. They offered me a Lead Tester position at Crave, and I thought that it might have been a good idea to just take that and ensure that I would have enough experience to work at some of these bigger companies. Also, I was comfortable there, I knew everyone, and I was scared that I would be fired for some weird reason. My good friend (thanks again Roger Chang) told me that I should definitely take the position if they offered it to me. So, I accepted the position and pretty much put in my two weeks that day.

I started at Obsidian on the 2nd of January with 3 other testers at the time. Well, technically 2. Someone was late (we still give her shit about it) so she came in the day after. The rest of us introduced ourselves to each other and got to work. Our first task? Build our own chairs. The QA team was so new that we didn't even have chairs made. It was pretty darn strange, but kind of a nice, family-type feel. I knew this was going to be different.

The coffee was in main lounge, so I went to get some, but I couldn't figure out how the newfangled machine worked. A man came out of his office right in the lounge and offered to help. He introduced himself as Feargus Urquhart, the CEO of the company. He already knew my name and mentioned to me that I was currently the youngest person at the company. I was blown away. I still don't think I know who the owners of Crave were, and yet here I was on my first day at Obsidian, I meet the CEO, and he knows who I am? It was right then and there that I decided that I wanted to be at this place for awhile and that I would do what I can to work hard for these folks to ensure their games were as Quality Assured as I could make them. I thanked Feargus for the directions on the coffee machine and headed back to my office. I went up to my lead later that day and told him that I planned on staying here. He gave me a strange look, but I didn't care. I wanted him to know that I was going to work hard to stay here.

Flash forward to about 7 months later. I had been there awhile and by that time I was the Lead Progression Tester on Neverwinter Nights 2. I worked hard to become a lead because I felt that our team didn't get enough information about certain things, so by becoming a lead I could get more information, which in turn I could give to the team. By that time I had actually met a lot more developers, learned what a lot of them did, and decided that I wanted to go into Production. The second owner that I had the pleasure of meeting on a personal scale was Darren, and he was a pretty darn good example of what I wanted to do. I spoke to him and the other producers and told them that I wanted to learn how to be a producer, and that I would take any extra work off of them while continuing to do my own tasks. People love less work to do, so they gave me a number of small tasks to help them out with. I made sure that they were taken care of, while continuing to ask for more things as I finished. At the end of Neverwinter Nights 2, they enjoyed my work, so they kept me on for their new project, Alpha Protocol.

One of the producers, Chris Parker, sat down and told me that they wanted me to become a producer, but at the time there was no positions, but they had a technical position with the motion capture team that I could take if I wanted, until something opened up. I immediately said yes and set to work. I knew nothing about animation, let alone how motion capture worked, but I was willing to take some time to learn. I sat down with the team and learned what the processes were that we used, and after awhile I took what they taught me and improved the motion capture process from 2+ weeks for some animations to about 3 days. It was right around then that I officially became the producer for the Animation Team, and the rest is history.

I could keep going (write in the comments if you'd like me to!) but I just wanted to sit and write all of that down. It's definitely different getting in the industry now as it was in 2005, but with the determination and motivation, it's still definitely possible.

Next blog post will go back to Project Management Software, I swear. For now, I'm done writing. Peace out.

-ACN

Project Management Programs and YOU! Part 1, The Questions

First things first, in my last post I talked about some project management (PM) software that I was looking at to possibly implement at my new job. Take a look yourself, but there are TONS out there that people have begun to make. It seems that there really isn't a perfect way to manage a project, but that's another topic i'll go into later on.

In any case, when choosing software you have to ask yourself a number of things:

• Why (my favorite question!) do I need this?
• What's the reason that you need PM software? Are you working on a small project and you need to track what the team is doing? Maybe you're building a new feature for something and just need to see all of the items that need to be done. Make sure you actually need software before you start to look.
• Who is going to be using this?
• Is just your team needed to view the software? Does your team have an easy viewable way to track their tasks and mark them complete? Does your client or publisher need access? If so, then you need to make sure that the software has a view that is easy for them to digest. Or, it at least has a good way for you to export information. 
• What information is needed?
• How are you managing your team? Do they like having tasks and subtasks assigned to them? Do they enjoy only seeing their items and nothing else? Do you want them to track time? Do you need to be able to separate things by department?
• How many people are going to use this?
• A lot of the programs are based on how many users, so that is a big factor that you should make sure you're aware of. Some, like Asana, can be used by up to (don't quote me) 10 people before you have to pay, so that's something to keep in mind.
• What are the tools you use in tandem?
• Do you have your own cloud server that holds all your files? Does the program you're looking at support that server? Are you expecting the program to hold your files?
• How much money are you willing to spend?
• Let's be honest. A decent amount get expensive as your team grows. Make sure you're willing to put up some big bucks to use the "primo" systems (Hansoft, JIRA, etc).
• What kind of project methodology are you using for your team?
• Are you using a agile scrum type method? Maybe agile kanban? Whatever method you're using, make sure that the PM software supports it.

These are just some of the things that I personally think of when looking. What are some of the thoughts that you think of when choosing a program?

First Day at the New Job, and WHY?

So, after getting to bed around 4am last night, (yay jetlag), I started my first day at FireForge, an independent game developer, strangely enough, right next to Obsidian Entertainment. :)

I spent the beginning of my first day doing what I do best: analyzing my situation and assessing the team's structure to attempt to help with issues or fix pipelines in the current system. I believe that every Producer and Producer-In-Training should be thinking this at all times: "Why?"

"Why" really allows a lot of change to happen, if you really think about it. It's something that we did as a child (asking why), but it really got beaten out of us. One of the things that I learned from a lot of my personal favorite Producers that I have worked with is that they are constantly asking why is this the reason we're doing something a certain way. If you ask a artist or designer why do something, it forces them to think "could there be a better way to do this?" Honestly, even if they don't necessarily think that, as a producer I believe that you should. A producer's main job is not just to make sure the schedule is on time, but also to make sure that the team has the tools necessary to get the job done effectively. Asking "why" helps get the juices flowing to facilitate change and make things better.

Later on today, I sat for a decent amount of time talking to the owner about where the company plans on going, how the team is doing, what is needed from me to help get the game moving forward, and what I think we need to do to help get the game out on time. This was such a new experience, just being put in a situation where I actually have the ability to make some good change. That's not to say that I never had those situations at Obsidian, I actually had the ability to do a lot there, but in this instance I am brought on much earlier, allowing me to try a lot of new things that I always wanted to but never had the chance. It's a humbling feeling hearing that you have a bit of free range to try some stuff, but also just a bit scary.

I finished off today looking into various Project Management programs that we can use. This was such a fun thing, I'm going to make tomorrow's post simply about some of the ones that I looked at.

Ta-Ta for now!

-ACN

Starting Off

Well, I guess I should start some sort of blog to pass the time.

Oh, but I should introduce myself. I'm a 27 (at the time of writing) year old male who lives in the sunny state of California and works in the video game industry. At the time of this writing I work at FireForge Games, which is a relatively new game studio. I worked at Obsidian Entertainment for 8 years, starting from QA and eventually becoming a producer.

As a producer, I help manage schedules, assign out tasks, go to meetings, write notes, and help fix pipelines for the team. I gotta say, I absolutely love it. The best part is that my job is never the same every day. Each day and each project is different. Different people, different publishers, different issues. I really couldn't ask for a better job.

Well, this is how i'll start my blog. I might talk about Production, I might talk about games in general, I might talk about a recipe. But, I guess I'll just talk, so stay tuned!

-ACN