ABSTRACT

There is a reason why a 50th wedding anniversary is such a rare and special occasion. It's easy to get married. It's difficult to stay in love (or even together) for decades. In software development, too, eventually your honeymoon period is over and all of your distributed development partners have stopped thinking of your game as an exciting new opportunity. Instead, they're seeing it as a real job, featuring lots and lots of very difficult work. How, then, do you keep all of the plates spinning smoothly? How do you maintain a distributed development organism once all of the parts are in play?