New Forum Feedback - Part II

"no-one in his right mind would commit to s/ware dates until testing is finished you cannot be sure what else may have been disturbed"

Speaking with over 30 years software development experienceI have to say, sorry, but of course you can and the comment exhibits a lack of understanding of the software development process. For any change, big or small, the design process should address both the change and its impact on the system as a whole (i.e. including knock affects) and how much development work will be required. You also define what testing is needed to cover both aspects. Then you CAN specify how the long all the development and testing will take and can give a delivery date. Then you implement the change (including any software changes required elsewhere to accomodate it) and test it and other affected parts of the system. Then you deliver. Under no circumstances do you make a change and then see what knock-on effects it may have as implied by the above statement. Firefighting a knock-on effect will most likely raise another one and you end up with a series of ill thoughtout changes. Sure, you will encounter bugs during testing but should not encounter unexpected problems with functionality elsewhere as everything should have been designed-in. If that is how hoop.la operate then I would recommend that Naim drop them ASAP.