Freezing requirements in embedded product development

Dear All,
This question is slightly OT.Because this is going to deal with
managing embedded product requirements then into involving in nittie
grits.

I am currently working on a consumer electronics embedded product.On
every now and then when we are about to deliver, requirements keep
changing.I have informed my top management and they say when customers
need we need to give thats what we are paid for.While theres a
obligation to deliver to what customers want,how to manage these adhoc
requirements in a efficient manner?


When should we take a call to freeze the requirements?At what stage you
can say "Boss this point of time we cannot take any more
requirements"?Most of the time we fail to say straight no because of
fear of loosing the customer.Whats the best way of putting across to
the customer to freeze the requirement?

Can any one having good experience in managing requirements for
embedded product share their experience ?

Sorry if this question looks naive and amature.I am in learning stage
of my project.Incase this is not the right group please forgive me and
direct me to right group to address such issues.

Regards,
s.subbarayan

.

Relevant Pages

  • Re: Freezing requirements in embedded product development
    ... managing embedded product requirements then into involving in nittie ... changing.I have informed my top management and they say when customers ... Sorry if this question looks naive and amature.I am in learning stage ...
    (comp.arch.embedded)
  • Re: Freezing requirements in embedded product development
    ... managing embedded product requirements then into involving in nittie ... changing.I have informed my top management and they say when customers ... Sorry if this question looks naive and amature.I am in learning stage ...
    (comp.arch.embedded)