It was pushed back by over a year so can't see it as being publisher pressure.
I don't know the details, but the fact that it was pushed back doesn't mean it didn't have anything to do with pressure from the publisher. Companies like Valve and Blizzard that are in a position to take a, "it's done when it's done" position on time lines tend to have much, much longer development cycles than those that aren't. What does that tell us? Software projects can very easily blow their time line projections. As a developer, what do you do when you simply don't have enough time and resources to produce what you're being asked to? Without knowing more about what happened we have no idea where the failures were.
And from what I've read, Alpha Protocol doesn't sound that bad. It's getting generally above average reviews.
That's what I thought, too.
OOOOhhhh... well you should have said scope creep than I would have understood... I have taken project management courses know about creep, I guess I didn't know feature creep was a programmers term.
Actually, our dev shop refers to it as scope creep as well, as did the last one I worked in. Feature creep is a form of scope creep (in our lexicon, anyway).
From what I understand, the project was severely mismanaged on every level, from the owner of the company stepping in and assuming he is a great producer, to the publishers saying "rawr, I want this new feature that worked in game [X], implement it now!", to the other producers bailing from the project once the owner started meddling.
I hadn't heard that, but those types of things will definitely slow down your project.
second its totally NOT for stealth players
third it takes forever to kill a guy
i shot a guy 4 time's in the face whith a shotgun....... and he didnt died >.>
and fourth it realy bugs me that a shot in the head isnt a instant kill
Are you talking about Alpha Protocol or Fallout 3?