View Single Post
  #6  
Old 03-19-2012, 09:58 PM
mazex's Avatar
mazex mazex is offline
Approved Member
 
Join Date: Oct 2007
Location: Sweden
Posts: 1,342
Default

Quote:
Originally Posted by flyingblind View Post
Because, as has been said ad nauseum, there would be no point. If a stop gap, probably buggy interim patch were released then the knashing of teeth and rending of garments would be deafening. The developers have said that as far as they are concerned the only thing that will pacify the customers is a fully working patch that fixes the major problems besetting the game at the moment. And that is what they have promised and are concentrating on. Until they are sure it is in the bag they are not giving any hints, timelines or concrete information as clearly some just cannot cope with the disappointment should some unforeseen slip occure between cup and lip.

I mean, how many explanations and apologies do you need from BlackSix before you accept they are communicating.
Well, working like that when developing software is how it was done in the 80:ies and 90:ies. Developers worked with fixed requirements set the start of the project, fixed resources but in reality no fixed point of delivery as all requirements had to be done before release - and minimal customer involvement accept for the initial requirements... After a while the customers got so annoyed with the results that took forever and did not meet the customers expectations that the development managers realized that it maybe was a bad idea to work like that? These days the most of the software development world work in another way (agile development, XP, Scrum - there are many names but the same core principle applies). You have fixed resources, fixed points of delivery (you release to customers every 3-6 weeks) and the thing that is variable is what gets into the release... You work tight with the customers and get feedback every month from the end users what they liked and when you start the next sprint (the 3-6 week long iteration that end with a new end user delivery) you use the customer feedback to decide what goes into the sprint. After hearing that the users that really liked X but not Y the way it worked in the system it's possible to maybe focus more on X and less on Y in the next sprint? Or maybe ditch Y? Or fix it? Without the feedback from the customers there are just a bunch of engineers guessing what the end users like - and engineers are not good at guessing!

But not in mother Russia...
__________________
i7 2600k @ 4.5 | GTX580 1.5GB (latest drivers) | P8Z77-V Pro MB | 8GB DDR3 1600 Mhz | SSD (OS) + Raptor 150 (Games) + 1TB WD (Extra) | X-Fi Fatality Pro (PCI) | Windows 7 x64 | TrackIR 4 | G940 Hotas
Reply With Quote