WIF_Killzone -> RE: When? (11/21/2009 1:42:29 PM)
|
I took a moment to fictionalize how the project could have been managed, and usually is, at least in the business world of computing, as opposed to the game development world--which I admit I don't know much of. Lets say the game was developed with a more traditional approach, with a team of consultants (or Matrix employees) hired, the project structure may look something like this: Project Manager (reporting to Matrix) Project Leads (reporting to the PM) Business Analysts Technical Analysts Architecture (security, application, database, network) Programmers and Programmer Analysts (5-10) Graphic Artists Research Test Lead, Testers Marketing and Communications Controller Coffee Girl (I wish) So now you have a staff of say 20 people being paid everyday (although some are contracted-in when the time is appropriate (i.e. testers). Regardless, there is a certain monthly burn rate in cash for the project. The first thing the PM would do is determine from Matrix where their priorities lay. Matrix would have most likely already set a budget after performing a feasibility study and determined the ROI (return on investment) which said we can afford XYZ dollars to make this viable. Perhaps the PM first needs to perform that with the business analysts in order to determine if they should even start the undertaking. Either way, they come out with a fixed dollar amount with some contingency that the PM can play with to deliver the project. Now, the PM's first conversation with Matrix is focused on the project priorities in Scope(Quality and Breadth of product), Budget, and Schedule in order for him/her to manage the project and make the ongoing decisions without having to run to Matrix for approval on every decision. How do you think the conversation would go? Most likely is would be; budget (high priority), you need to deliver the project on budget or we don't make any money. Schedule, you need to deliver this in a reasonable timeframe and you can sacrifice some scope-quality in order to meet the schedule. Let me be clear Mr. PM, sacrifice scope in order to deliver on schedule and on budget--we don't need bells and whistles (as they cost) but we do need a quality product. So off he goes, he has his marching orders and he tackles the project. He starts a forum so he can get input from the knowledgeable user community. And he starts to notice that maybe he has underestimated this project. It looks like a bigger project than he first realized. The user community is passionate and a little demanding (not that he cares really), but they have tons of good advice for him. I will utilize them he thinks, like free resources-money for the project. Cool. In fact, I am going to appoint my star business analyst-programmer to moderate the forum as he is very passionate as well--he wants to deliver the best product he can. Time goes on, and he starts directing the projects activities, reporting monthly to Matrix, and everything goes along fine but he start to notice that his star is running everything by the user community and its starting to impact the project negatively. He sits his star down and has the following conversation: I need you to stop asking for so much input, its holding up the project and your adding modules and functionality we just can't afford. His star argues back, we need this, we need that, their are colour blind people and they need to be able to read the maps and counters(like me). Are you saying we have to re-do all the counters and maps for the colour blind? Yes. Do you know how much that will cost, NO, it's already programmed, sorry. His star storms away and notifies the user community. They rebel (as this is just one example in many design decisions that were denied in order to deliver on-time and on-budget). The PM determines this a project risk and decides to limit communications with the user community and just build it to the best of their ability within the current budget and time constraints. The user community from then on is shown only marketing hype, some glitz and glamour and a whole bunch of good news stories and they are happy again, waiting for their new game--how exciting. The project gets delivered, the PM is payed, gets a nice bonus for delivering on time and within budget and goes to Jamaica with the Coffee Girl. Wonder how the game would turn out?[X(] I'm not going to get on my soap-box and discuss how Matrix's and Steves approach is better, suffice to say in my humble opinion I like what I see. As a PM myself you seldom, if ever, get a chance to do what they are doing. Matrix I would theorize (oh-oh the soap box) doesn't care how long it takes (they will still be in business), the money isnt coming out of their pocket. Moreover, you can seldom hire people to perform peace work (i.e. not get paid) to speed up the project--most people are risk adverse or need money to support themselves on an ongoing basis. If they did hire ($$) extra people design decisions would be made that would result in a lessor product being delivered--guaranteed, full stop! Keep up the fantastic work Steve. Btw, maybe you can get someone else to moderate the forum so you can concentrate on the programming (could'nt resist--I'm evil) Seriously--keep up the good work. Craig
|
|
|
|