YouSub
Untitled

en English

Untitled English subtitles

0 downloads · 154 lines · added Nov 4, 2015

Report a problem
What's wrong?
Advertisement

English transcript

Reason no 3
big up-front planning
is not practical because we assume we can collect all the requirements in the
beginning and because we assume we can freeze the requirements
and it need not have to change later.we also assume we can plan everything upfront.
so is it possible? .what are the assumptions?why do we assume this way?.we assume
software is so simple
that development can be planned from the beginning to end without any problem and
we also assume all project variables can be
estimated or predicted in the beginning
project variables could be your scope,your size,your
cost ,your resources,
your schedule your risks everything.
all software variables or project variables
be assumed can be predicted in the beginning and we also assume
up-front planning it's possible and up-front planning is enough.
we may make some minor changes to the plan but most of those
planning has been done in the beginning. because we believe it is possible.
so what we do we prepare a detailed plan in the beginning.
if it is a one-year project we also planned what should developer A should
to do after 180 days from now what should the tester do,say 240 days from now
so we plan everything in the beginning.
and we strictly track to the plan.
we may adjust here in there somewhere but primarily we use
the main plan,so what is the
reality?. in reality big up-front planning is difficult
planning should also evolve along with your requirements.
you cannot freeze the requirements you cannot freeze the
plan also.
The results
okay this is a huge set up results and there is a big survey on this result itself.
so I cannot just explained that result in just one word in the slide.
let's move on and see what are the implications of
this assumption. big up-front planning is possible.that is an assumption we have.
so let's go back to the
Standish, a report which we mentioned earlier
so the Standish Group came up with the chaos report.
they did a analysis or survey
with about 365 respondents primarily the senior managers of various
software projects both small medium and large companies
and they covered major industry segments Health care,
insurance banking all the stuff and more than 8 thousands projects have been
surveyed
in this particular Standish Group survey and
they call this survey result as chaos report
and some people do not like that word because it is
on negative context it's also called failure report this is
the findings after they have
done that Survey they categorised the setoff projects in to three major
groups.
The first group is ,the first group of projects are successful projects.
so the Standish Group definition of success
if the project is completed on time and on budget with
all the features and functions as initially specified.
if all the three things happen it is called a successful projects.
the second set up projects challenged,
project is completed but it is
over budget ,behind schedule and
it does not offer all the features and functions originally specified.
it does not have something missed some something.
so that is the case those categories of projects are called
challenged projects.And the third category impact project
these projects are cancel halfway through or these projects never reach the client.
so stop some way down the lane.
so these all are the three categories
and they also come up with percentage of projects
in these three categories before I come up with that percentage,
let me ask you from based on you experience,
what percentage of project I've been successful in your company?.
eighty percent, fifty percent
forty-percent 30 33 percent one third of the projects
let's see what the survey results says,
sixteen-point two-person
probably one sixth of the projects only those percentage of projects
have been successful. and
close to fifty percent of the projects ,fifty two point seven percent of the projects are impact.
they've been delivered.
but behind schedule of it extra cost
and not with all the features.
52.7 percent other projects have been challenged
and interestingly about 31 point one percent of the projects
have never reach the customer after incurring lot of cost
it has never seen the light of the day it is really shocking
in fact when Standish Group release this survey summit in 1995
almost the entire software industries stun.
some people don't even believe this some people even question that data
you can dispute the numbers but you cannot dispute that the three categories of
projects
and you cannot dispute the fact that the successful projects are very very
less
compare to other two buckets of projects. now
standish group also came up with the Success Factors those three factors right
successful project, challenged projects,failed projects.
they also came up with the reasons or factors for
the successful projects as well as
challenge project as a left impact let's look at the first
list what all the reasons for project being successful
I'll ask you what are the reasons for
based on your experience. some projects to be successful
on time ,on schedule with all the original features.
with no extra cost .if you've ever delivered projects like that.
what are the reasons?. or if you're not done
if you do certain things right . you can do this what are the reasons?
As per Standish Group Report this is what it is.
a first and foremost user involvement throughout the life cycle.
second one executive management support.
on the third one clear statement of requirements
and planning comes slightly later.
realistic expectations and the list goes on.
but the topmost one is user involvement and executive management support.
same way they also came up with the project challenge factors.here are they
lack of user input that is the first major
reason for challenge projects incomplete requirements and
specifications
changing requirements and specifications lack of executive support.
some of them are repeated from the first list
and the also came up with the reason for
impact projects ,so here are the reasons
in complete requirements that is the major reason for projects to be cancelled.
and lack of user involvement that comes through out in the top 2 or 3.
lack of resources
and realistic expectations and all those stuff.
I'm sure many of these factors do happen in your projects
at least some of the projects.
now you may even ask me, what is that you are talking about?
you're talking about a 1995 report: things have changed a lot in the last
fifteen years
and I'm sure if you take a survey today that things would have been much
different
our projects we do not have only 16 point odd percentage of
success unfortunately
Standish Group keep on doing this survey every
year only 1995 report is the most quoted report
if you go to any website or any result or any survey
you find 1995 report.
but other ways they come up with this report almost every year.
so look at the successful project, it has marginally increased
from sixteen percent to say thirty percent to look at
absolute percentage of this probably just double from 16 percent to 32 percent.
but this is still
one-third of projects that are completely successful.
take the challenge projects they were around
so no major changes no major improvements and failed projects
also given our own on coming down
a bit but still it is not something which is
we can feel comfortable things have not improved much over a period of time.
now we have been talking about
the failure report .are there any success report?
so here are some so this doctor
they did what are the factors for projects to be successful?
so here are the results of that successful projects.
let me the man once again this is this our way up
successful party to keep this in mind believe you said
these points make after the complete although seventies

Need subtitles from another video?