Advertisement
English transcript
Hey everyone, This is Raja, Enterprise Agile Coach
from ProXL Consulting.
now, let's move on to Agile. I'm going to give
7 reasons for moving on to Agile. May or may not be covering all the issues
there, but some or other those issues are covered in this
seven reasons. The first one, ambiguous requirements. This is the most common
issue as we discussed earlier
Ambiguous Requirements. See, most of these issues that we discussed earlier
do come because of some assumptions we have in the traditional software
development life cycle.
so if you go and question that assumptions, probably those issue may not be there
so let's start with the assumption for ambiguous requirements
We assume customer can and shall identify
all the requirements in the begining this is quite obvious, right
you should not only know just piece of what you want you should know
everything about what you want that is an assumption
looks reasonable so what we do, ask
customers what they want ,when they really don't know
at the starting of the project is not the right time for the customer to
understand
everything
adding to that what we do, we also ask them to the sign of the requirements. we tell them to sign off the requirements
how many of your customers are comfortable
signing on the requirments
ok, and what happens when you ask
the customer what they want, when they really do not know
and if you're going to say later they are going to freeze the
requirements
and you cannot make any changes what
would be the reaction of the customer, customer would think
okay these guys are going to freeze the requirements end of this month so what I will
do I will give all the requirements, I may currently know
I may also give all the requirements, I may not know
because later I cannot add anything. so give all the requirements you think
that should be there in the software.
so customers may not know all that requirements in the beginning that is given
no customer knows completely everything about the product and
at the time of starting of the project, They may not know, so the result
is over production of features
let's look at one of the very popular ser veys by Standish group,this group
has come up with something called chaos report, this is
very popular report but
this is a different than what I'm talking about Standish Group did a
survey very recently
on they studied various software applications
and the study what percentage of features are
really used by the customers or the end users. The results were stunning
starting with the first one as per their
study , only seven percent of the features
are always being used by the clients .or the end users.
and another thirteen percent of the featurers
are often used. And sometimes used about sixteen percent of the features.
and interestingly about nineteen percentage of the featurers are rarely used
but the most interesting part is this
about 45% of features are never used
by the users,end users. If you add this and this together rarely
and never about 65% features are either rarely used or
never used by the end users.
which means about 2/3 of
features or rarely used or never used
I'll and one only about one third of the requirements are always used often
used are sometimes used
this may look strange to you, but let me let me give you an example
what is the most popular program or the software product you use?, say for example
XL or word so do you know how many features are there in Msword?
probably you may not know
but just estimate or give from your own
experience what percentage of features of Ms word do you use
throughout your career so far.
proably in a single digit.
if you are really a very experienced user of the word processing program
you would have used about 10 percent. I am sure ,have used
much less than seven percent of Ms word feature
take for example a excel . Excel is like mini data base.
How many of us used Excel for the complete
capability of it. very few probably it would fit to the seven percent
so most of the software products
have a lot of features which are rarely or never used.
The reason could be this
freezing the requirements in the beginning.
could be.
from ProXL Consulting.
now, let's move on to Agile. I'm going to give
7 reasons for moving on to Agile. May or may not be covering all the issues
there, but some or other those issues are covered in this
seven reasons. The first one, ambiguous requirements. This is the most common
issue as we discussed earlier
Ambiguous Requirements. See, most of these issues that we discussed earlier
do come because of some assumptions we have in the traditional software
development life cycle.
so if you go and question that assumptions, probably those issue may not be there
so let's start with the assumption for ambiguous requirements
We assume customer can and shall identify
all the requirements in the begining this is quite obvious, right
you should not only know just piece of what you want you should know
everything about what you want that is an assumption
looks reasonable so what we do, ask
customers what they want ,when they really don't know
at the starting of the project is not the right time for the customer to
understand
everything
adding to that what we do, we also ask them to the sign of the requirements. we tell them to sign off the requirements
how many of your customers are comfortable
signing on the requirments
ok, and what happens when you ask
the customer what they want, when they really do not know
and if you're going to say later they are going to freeze the
requirements
and you cannot make any changes what
would be the reaction of the customer, customer would think
okay these guys are going to freeze the requirements end of this month so what I will
do I will give all the requirements, I may currently know
I may also give all the requirements, I may not know
because later I cannot add anything. so give all the requirements you think
that should be there in the software.
so customers may not know all that requirements in the beginning that is given
no customer knows completely everything about the product and
at the time of starting of the project, They may not know, so the result
is over production of features
let's look at one of the very popular ser veys by Standish group,this group
has come up with something called chaos report, this is
very popular report but
this is a different than what I'm talking about Standish Group did a
survey very recently
on they studied various software applications
and the study what percentage of features are
really used by the customers or the end users. The results were stunning
starting with the first one as per their
study , only seven percent of the features
are always being used by the clients .or the end users.
and another thirteen percent of the featurers
are often used. And sometimes used about sixteen percent of the features.
and interestingly about nineteen percentage of the featurers are rarely used
but the most interesting part is this
about 45% of features are never used
by the users,end users. If you add this and this together rarely
and never about 65% features are either rarely used or
never used by the end users.
which means about 2/3 of
features or rarely used or never used
I'll and one only about one third of the requirements are always used often
used are sometimes used
this may look strange to you, but let me let me give you an example
what is the most popular program or the software product you use?, say for example
XL or word so do you know how many features are there in Msword?
probably you may not know
but just estimate or give from your own
experience what percentage of features of Ms word do you use
throughout your career so far.
proably in a single digit.
if you are really a very experienced user of the word processing program
you would have used about 10 percent. I am sure ,have used
much less than seven percent of Ms word feature
take for example a excel . Excel is like mini data base.
How many of us used Excel for the complete
capability of it. very few probably it would fit to the seven percent
so most of the software products
have a lot of features which are rarely or never used.
The reason could be this
freezing the requirements in the beginning.
could be.