You should plan builds with the ability to back out and revert to previous versions of the code. This should be standard practice. You should have, after 4 years, a list of the actions a player will perform within the FIRST 10 minutes of play. Then...and this isn't splitting atoms here...you perform those actions ON AN INTERNAL TEST version of a server. You should have an EJECT EJECT EJECT button for any person who suggests doing any code development and deployment based on "Agile methodology". Joe Trendy: "Hey gais, let's all attend a daily stand-up where we plan sprints! I'll be the Scrum Master!" Bob Beentheredonethat: <hits red EJECT EJECT EJECT button linked to Joe Trendy's chair> Joe Trendy: "We can leverage lift in the..." WHOOOOOOOSH "...omg...gais? GAIS!? I can see my house froooom heeeeere!"
Feels more like spirals. Besides, agile can work* *if you have the right team and the right project and everyone knows what they're doing