View Single Post
Old 12-21-2013, 02:45 PM   #14
WACo
Minors (Rookie Ball)
 
Join Date: Nov 2013
Posts: 25
Have to say it: who cares about hockey? This is iOOTP Baseball. If FHM is that bad, scrap it and the smaller potential customer base, refund the money, and instead concentrate on the bigger revenue base with the sustainable code and customer base. Take the FHM code and do a rewrite for next year, relaunch with a discount for previous purchasers.. Either that or hire someone (or contract it out) to do the hockey thing. Looking at it as a business, If 2 projects are competing for resources in a business, you feed the one that is the bigger cash flow. You don't starve it in favor of a smaller stream. Don't throw good money after bad. Got x hours a week to work, then allocate Y hours based on revenue/profit. Say Prodct B produces 75% of revenues. Then product B gets 45 out of 60 hours in a week if u are in crunch mode 60 hour week. If product H becomes a drain, you either increase the resources (hire/contract) to help it, reduce its functionality or scope to where it fits into the limited resources available, or admit the failure and scrap it, taking those losses but preventing future losses to the main cash product B which will occur if it continues to be resource starved. Just my experienced opinion.

Last edited by WACo; 12-21-2013 at 02:59 PM.
WACo is offline   Reply With Quote