I expect the priority for Bombardier is to carry out any required software updates and software testing on 345s. I expect any programmer etc resources used on the 710s will be to enable some but not all further mechanical testing. I always remember, when I was an Analyst/Programmer, that if there was too much going on then some projects (in this case class of train) would be prioritised over another. I think, at this stage, Bombardier would be focused on getting the almost complete fleet of 345s in action and paid for.
Lamentable that the delays are gradually dragging on leaving the user (Goblin route) with no forward planning ability. It would have been kinder for the supplier to be realistic about what they could achieve at an earlier stage. After all IIRC Siemens were not bidding for some contracts because they believed they could not deliver in the timescale required (OK that was on a mechanical front I suspect). It is what I always hated - having to keep quiet about an expected delay and watching parts of a company making unrealistic plans. I have seen unrealistic promises made just to get or retain the work.
Is the above what is happening here with the 710s ?.
It is not unusual. After all look at the timetable fiasco that everyone was too scared to admit might happen - and did happen. That is what happens when there is too much pressure to meet demands.
</killjoy>