YouSub
Untitled

en English

Untitled English subtitles

0 downloads · 97 lines · added Nov 4, 2015

Report a problem
What's wrong?
Advertisement

English transcript

Reason no 2
First is ambiguous requirements, what is second reason?
requirement changes are inevitable, if the customers do not know what they want
in the beginning
customers will eventually come back to you and ask for something
new later in the life cycle it is quite obvious
we don't only look at the obvious
now lets discussed this particular point
a little bit more. what are the assumptions
Do we have?. when we freeze the requirements or
why don't we allow any requirement change later.
here is the assumption,the cost of change increases
during the development life cycle so freezing the requirement is
absolutely required in the beginning that's an assumption
so what we do, we freeze the requirements in the beginning
in the end of the requirement analysis phase, the requirements are frozen.
please don't ask for any changes, that's what we say to the customer.
and interesting still, we penalized the customer for adding things later.
if customer comes up with an excellent idea,
Three months after starting of the project, we tell them
no its not possible as of now. If it is required, probably we have to initate
change control cycle .we will do an impact analysis on those changes
We will come up with the reestimation of the cost,
and the schedule and even tell you how much more you have to
and how much more you have to wait to get the final product.
so that's what we do. the reality
new ideas may emerge at any time. See halfway through the development life
cycle
if the competetor of the customer has released a product and that product has
a nice feature
obviously your customer wanted to have that feature also
we cannot afford to say no to your customer.
and requirements will evolve over a period of time.
as we discussed earlier, no customer comes to you with a complete set of
requirements in the beginning
if you found one, please show me that customer I want to do business with them .
I rarely seen that kind of customers.
so what is the result of not allowing the changes. Changes any way happen
customer
who need that particular change on yes it's quite obvious customer has not
mentioned that in the beginning
but it is going to happen and when there is a
discussion between customer and you the customer is always
going to forces me into
making that change happen, so changes are going to happen.
and if we put all strict in control procedure
because of these changes both development community
as well as the customers are going to be unhappy, so that is what
actually happens in the result. so lets discuss
what all the key challenges what are the main issue
why do we have to have landed with requirements why do we have to have requirements changes?
soft ware teams are building something
that does not exist in the beginning. see software development is not like automobile production. Say for
example automobile company producing a car,sayToyota manufacturing campri in the
and in the assembly line say about 100
Toyota campris are to be manufactured today
manufactured on that day. what should be the size of chases.what should be the size of the car.
what should be the engine.what should be the
steering, everything is very clear and they have to mechanically do
things as per the instruction
given to them. unfortunately software development does not like that.
probably sotfware development can be equated like the product development part of automobile campany.
Say when you want to come up with the toyato campri model
the first place
you may have to do lot of development activities.
What should be the engine size?
what should be the cabin sizes ?.who are our competitors?
how are we going to match with the competitors? . Say Honda accord has
in their product
so what should be match with that?.so
they have to do a lot of things during the initial development phase.
so software development, every software development
is like product development, if you think or equvate this to a manufacturing
part of
the industry, it is very difficult. let's understand once again, software teams
are building something that does not exist in the first place
and that is the first challenge second one
the customer is attempting to describe,what they imagine is
not existent entity should be.Even
customers do not know, so they tried to
imagine and visualize and give you some requirements.
in the beginning and our developers
then tried to imagine what customer is describing
are the product and they believe what they heard.
that the customer describes.This is what they pursuive and take this as initial input.
subsequently
and more interestingly the first opportunity
anyone has to truly see the product built
is the one the customer really needs, is after the development is completed
one when the complete development is through, you will also see whether what the customer wanted is what we have given.
there is a famous law which is called humphries law which has been pronounced by Dr Watts Humphery
considered as a father of software quality.
As per Watts Humphery
you will understand the complete set of requirements of a software, only after
It has been used by the customer.
before that you will never understand the requirements completely.
well

Need subtitles from another video?