The current release of your F1 racing game is showing some serious flaws, this you can not disagree with. While some enhancements to your product was released successfully, certain aspects still have not been fully developed and hinder your company in being able to claim this game release a success in the eyes of the hardcore gamer or F1 racing fan. Online communities are having problems in various forms and single players are hamstrung by a issues that in a testing environment would mark it as a 50% failure.
Firstly you will need to look at the project management style being utilised as this is the utmost pinacle of the development process, if this fails, so does all below it. Being an observer and unsure of the methodologies used, I will not comment whether that is the issue but simply state that if not already, you need to employ AGILE with Scrum weekly meetings. Simply put, this approach will galvanise the development team and you, the product owner, will be well aware of any issues before they become a problem.
The next level will have to be the testing regime, this is lacking in finding the most intrusive game errors before release, there can be no denying that F1 2017 was released with glaring obvious problems, the failure of one team not having any benefit from upgrades should have been discovered in testing, as every team should have been tested, not just one or a few as can only be assumed to be the case during your testing given you released with the problem existing. The online issues, again a testing environment would have found those most reported problems. In my experience most testing scripts are automated and pass, as they are written to prove aspects work, and do not actually test how a user may actually use the system, just that the release passes a test of code stability.
2018 and beyond:
Before any enhancements to the next years game,
1. sit down with current game and fix every error. Release as a patch -
2. use this for base of the 2018 game, adding the new drivers any car enhancements and track changes.
3. Create enhancements and if fully tested and ready for 2018 release then include them, do not give your customers another years broken release.
before remarking this isn't viable, remember most of your customers
still own a flawed, if not outright broken F1 2016. That is our opinion, the customer, regardless of how proud you may be of your staffs efforts to release a game with so many working parts, your customer sees it differently. Meet the game from our perspective before denying our claim of broken.
Ask yourself, would you be
happy with another purchase being left unrepaired, is this how F1 2017
will also be left? Codemasters owe it to the paying customer to fix, not
just state, "oh but we have already moved onto next years release, buy that it will be
better". We already paid. You owe it to us. It is a simple case of your
companies integrity in dealing with customers honestly.
thank you for your time.