On September 28 2017 05:05 Lazare1969 wrote:
![[image loading]](http://cdn.softwaretestinghelp.com/wp-content/qa/uploads/2013/09/project-planning-dilbert.gif)
+ Show Spoiler +
![[image loading]](http://cdn.softwaretestinghelp.com/wp-content/qa/uploads/2013/09/project-planning-dilbert.gif)
+ Show Spoiler +
If you ever worked in a large software corporation like Blizzard it's bureaucratic and can take an eternity over what simple decisions should be made. You often have to wait for that weekly meeting before you can make that suggestion to your team over "hey what if we made it so the server checks the network latency between the two players and auto adjust turn rate based on that?" Then if the project manager agrees with that idea, he or she needs to forward this to the project lead who will then need to discuss with the software and business analysts whether to make the final decision. Then when they approve it, it can take weeks until you're directed to work on this since you at the moment you have other work to do. Then you need to spend days having your work that you've done documented ad nauseam so that the software analysts will have something to do with their time, then you have to forward your changes to the testers which often takes longer than it should, then the results get reported back and if there are no bugs the project manager can decide whether to push this in the next update. Anyway, blame it on workplace bureaucracy and busywork. This has nothing to do with the difficulty of the actual fix that needs to be applied. There's an entire comic strip called Dilbert devoted to this subject.
I don't believe this is specific to software corporations. It's painfully slow change at my work, a large corporate insurance company. Slow as in, you suggest something, get the buyin at a meeting (that takes 3 months to set up), and it comes out a over a year later after you got the go ahead.