Advertisement
English transcript
Hey everyone, this is Raja
Enterprise Agile Coach from ProXL Consulting
however, there are lot of the issues people face
in following this traditional model. So, before I
speak about those issues or challenges of traditional life cycle model
I would request you to list down from your own perspective
from your own experience what are all the major challenges
or issues you are currently facing with this traditional life cycle model,
either waterfall or V, any of the sequential model that you follow
what are the issues we're facing? I would suggest to pause this video
take about 10 minutes, come up with all the list
If required you can also involve your team members so that we'll get
get to know the complete set of issues. Once you are ready with the list of
issues we'll continue further. Please pause the video.
okay hope you've come up with a decent list of issues.
Let's look at those issues. unfortunately I cannot see the list of issues you
currently have
but let me go through the list that I have faced myself personally
pIus I have conducted this training almost all over the world
I have interacted with so many different developers and I have listened to them in
my live
training various issues that they are facing.let's try to go over
the list one by one
so the first one the most popular issue
of traditional software development is unclear requirements or ambigious requirements
almost everybody complaint about this
and the second one requirements change
customers change their mind half way through the development life cycle
you're already in the coding face customer comes up it's completely new
requirements
so requirements change during the development life cycle after the requirement
and the lack of involvement of the customer
traditionally in this life cycle customers are involved in the initial
requirements phase
and may or may not be involved during design and coding phase
finally they come back and get involved in the final testing phase
usually the user acceptance testing phase
in between there is a big gap between
development community and the customers
keep waiting to see the product for
long time so lack of involvement of customers
then accuracy of estimation probably because of the
unclear requirements when you start with unclear requirements then your estimation cannot be very accurate unfortunately
so estimation is an issue
then un even loading of resources
say for example during requirements phase
they involved Business Analyst during design phase
We need architects during coding phase we need programmers or developers
during testing phase we need testers so these people are
not level throught the the development life cycle
they come and perform a role in different phases of the life cycle so
the resources are not leveled properly and then
The last minute correction is very difficult primarily because of this
sequencial way of developing software if at all customer wants some change in
the last minute
it is really very difficult to major change so that's what another problem mentioned by
other developers and not much time is available for testing
unfortunately the design may get delayed
coding may get delayed but you have to still maintain the end delivery date so
unfortunately you may not get much time
for testing and because u don't have much time for testing .You may not have much t time for fixing defects obviously
another issue face by peopel are a lot of documentation
requirement specfication document you need design document you need various
program documents you need test plans, test cases
and you need configuration management document so many different documents
need to be prepared for this traditional life cycle
and most of the people complain there is a schedule at cost over
probably because of ambigious
requirements probably because of
requirement change
Schedule and cost overruns to happen
and interesting one lot of midnight oil
just before the final delivery. I have never
seen a development team working peacefully
just before the final delivery and then peacefully deliver that to the client
almost every probably two to three weeks before the final delivery
everyone slocks, works up to 12'o clock or 1'o clock mid night
almost everyday so lot of mid night oils before final delivery
and finally customers are not happy with
what he see . End of all those hurdles
finally customers are not happy these are the issues with the traditional software
development
probably you may have something more in your list
But I think reasonably, we have captured the decent list of issuses.
Enterprise Agile Coach from ProXL Consulting
however, there are lot of the issues people face
in following this traditional model. So, before I
speak about those issues or challenges of traditional life cycle model
I would request you to list down from your own perspective
from your own experience what are all the major challenges
or issues you are currently facing with this traditional life cycle model,
either waterfall or V, any of the sequential model that you follow
what are the issues we're facing? I would suggest to pause this video
take about 10 minutes, come up with all the list
If required you can also involve your team members so that we'll get
get to know the complete set of issues. Once you are ready with the list of
issues we'll continue further. Please pause the video.
okay hope you've come up with a decent list of issues.
Let's look at those issues. unfortunately I cannot see the list of issues you
currently have
but let me go through the list that I have faced myself personally
pIus I have conducted this training almost all over the world
I have interacted with so many different developers and I have listened to them in
my live
training various issues that they are facing.let's try to go over
the list one by one
so the first one the most popular issue
of traditional software development is unclear requirements or ambigious requirements
almost everybody complaint about this
and the second one requirements change
customers change their mind half way through the development life cycle
you're already in the coding face customer comes up it's completely new
requirements
so requirements change during the development life cycle after the requirement
and the lack of involvement of the customer
traditionally in this life cycle customers are involved in the initial
requirements phase
and may or may not be involved during design and coding phase
finally they come back and get involved in the final testing phase
usually the user acceptance testing phase
in between there is a big gap between
development community and the customers
keep waiting to see the product for
long time so lack of involvement of customers
then accuracy of estimation probably because of the
unclear requirements when you start with unclear requirements then your estimation cannot be very accurate unfortunately
so estimation is an issue
then un even loading of resources
say for example during requirements phase
they involved Business Analyst during design phase
We need architects during coding phase we need programmers or developers
during testing phase we need testers so these people are
not level throught the the development life cycle
they come and perform a role in different phases of the life cycle so
the resources are not leveled properly and then
The last minute correction is very difficult primarily because of this
sequencial way of developing software if at all customer wants some change in
the last minute
it is really very difficult to major change so that's what another problem mentioned by
other developers and not much time is available for testing
unfortunately the design may get delayed
coding may get delayed but you have to still maintain the end delivery date so
unfortunately you may not get much time
for testing and because u don't have much time for testing .You may not have much t time for fixing defects obviously
another issue face by peopel are a lot of documentation
requirement specfication document you need design document you need various
program documents you need test plans, test cases
and you need configuration management document so many different documents
need to be prepared for this traditional life cycle
and most of the people complain there is a schedule at cost over
probably because of ambigious
requirements probably because of
requirement change
Schedule and cost overruns to happen
and interesting one lot of midnight oil
just before the final delivery. I have never
seen a development team working peacefully
just before the final delivery and then peacefully deliver that to the client
almost every probably two to three weeks before the final delivery
everyone slocks, works up to 12'o clock or 1'o clock mid night
almost everyday so lot of mid night oils before final delivery
and finally customers are not happy with
what he see . End of all those hurdles
finally customers are not happy these are the issues with the traditional software
development
probably you may have something more in your list
But I think reasonably, we have captured the decent list of issuses.