Advertisement
English transcript
Hai everyone this is Raja ,enterprise agile coach from, proXl consulting
Now the reason no 5.iterative and
incremental development
it's better than sequential water fall development.
what are the assumptions? software development shall be done
in a sequential step-by-step manner.that is an assumption.
it is possible like
how an automobiles manufactured .you first make the Chases
move it to the next person then the engine is fitted on that
so sequential way of producing toyota campri so we believe software can
also be developed
sequentially, step-by-step and
we also assume customer can wait until the end of the project to get the final delivery.
why do we have to show them in between?.no need.
so that is another assumption so what we do
develop the software sequentially, with one big final delivery.
in the end if the customer is lucky or
the customers insist and probably you may make one or two additional deliveries.
but otherwise usually we delivered by the end of the life cycle
and what is the reality
on this spot, in the customers actually get to see the final deliverable
it may be very different from what they originnally thought
they would get that happens almost always.
and it is too late to change anything
and the customer sees the end product is, almost the 11th month or the twelfth month.
when they were supposed to use this product
and when they come up with and find out this is not what they really wanted,they are in a fix it is really very
late to make any changes that is why we have maintenance base
whatever changes you want right now let's sign another contract
and give me more money then i fix it or a period of time probably after six
months or eight months
you may get what you actually want that's what we
indirectly tend to say,the result
most of the customers are unhappy with the deliverables.
unfortunately they are stuck with you probably they have to sign on with you
for the maintenance project so that is reason number five
let's look at at different context
of the traditional development life cycle analysis, design ,coding, testing
we already discussed the time process this way the cost of changing increases
at that time process in the customer asks the change some time
in February a second month of the development probably be much cheaper to
make that changes if the customer wants the
change some where during coding phase
it will be really very expensive because the requirements have been already
understood and frozen and all the design have been done
if you make if you request any changes here I have to go back and change the design
that requirement and it is going to become a is going to
first going to be very expensive and it is going to further delay your deliveries.
so look at another context
for whatever reason customer wants to stop the project halfway through
so somewhere in the month june july
for whatever reason he's what do the customer get.
do they get half the solution
no.the customer probably may get
and nice requirements analysis document
and nice design document and if the customer is
lucky he may get some code some working code
I'm most of the code which had just code may not be working
so that is what the customer gets and what do they do with that
having invester close to
fifty percent of the cost of this particular software development
what do they get this nothing and they cannot make use of that
in their business very difficult.
Now the reason no 5.iterative and
incremental development
it's better than sequential water fall development.
what are the assumptions? software development shall be done
in a sequential step-by-step manner.that is an assumption.
it is possible like
how an automobiles manufactured .you first make the Chases
move it to the next person then the engine is fitted on that
so sequential way of producing toyota campri so we believe software can
also be developed
sequentially, step-by-step and
we also assume customer can wait until the end of the project to get the final delivery.
why do we have to show them in between?.no need.
so that is another assumption so what we do
develop the software sequentially, with one big final delivery.
in the end if the customer is lucky or
the customers insist and probably you may make one or two additional deliveries.
but otherwise usually we delivered by the end of the life cycle
and what is the reality
on this spot, in the customers actually get to see the final deliverable
it may be very different from what they originnally thought
they would get that happens almost always.
and it is too late to change anything
and the customer sees the end product is, almost the 11th month or the twelfth month.
when they were supposed to use this product
and when they come up with and find out this is not what they really wanted,they are in a fix it is really very
late to make any changes that is why we have maintenance base
whatever changes you want right now let's sign another contract
and give me more money then i fix it or a period of time probably after six
months or eight months
you may get what you actually want that's what we
indirectly tend to say,the result
most of the customers are unhappy with the deliverables.
unfortunately they are stuck with you probably they have to sign on with you
for the maintenance project so that is reason number five
let's look at at different context
of the traditional development life cycle analysis, design ,coding, testing
we already discussed the time process this way the cost of changing increases
at that time process in the customer asks the change some time
in February a second month of the development probably be much cheaper to
make that changes if the customer wants the
change some where during coding phase
it will be really very expensive because the requirements have been already
understood and frozen and all the design have been done
if you make if you request any changes here I have to go back and change the design
that requirement and it is going to become a is going to
first going to be very expensive and it is going to further delay your deliveries.
so look at another context
for whatever reason customer wants to stop the project halfway through
so somewhere in the month june july
for whatever reason he's what do the customer get.
do they get half the solution
no.the customer probably may get
and nice requirements analysis document
and nice design document and if the customer is
lucky he may get some code some working code
I'm most of the code which had just code may not be working
so that is what the customer gets and what do they do with that
having invester close to
fifty percent of the cost of this particular software development
what do they get this nothing and they cannot make use of that
in their business very difficult.