Advertisement
English transcript
Hey everyone this is Raja,Enterprise agile coach from ProXL consulting.
so now coming onto the last two reasons
reason no 6&7 delivery through
small baby steps is always better than
a huge delivery by the end of the development life cycle.
Especially because the requirements are ambiguous
and the customers do not know everything that they want ,if you ask them
tell me, what are the top five or six requirements that you really want.
that develop that do a requirement do Design
quoted, tested show your
working software to the client.let the client
this is fine. playing this is what I expected.but this part is not i wanted
but I want something more also
the understanding of the customer will go much higher
if you quickly show working software. so delivery through
small baby steps are much better than
single huge delivey by the end of the development life cycle.
that is why we should go to Agile.
and frequent reflections by the development team is very important.
when every software development is a discovery by itself then you have to
reflect on what you learn and what should you improve.
what do we do right now in the traditional software development life
cycle
we do some reflections that this mostly by the end of the development
life cycle.
end of the project you do a project retrospection meeting or
some projects called it as the project closer meeting.
are rock in some other name.
that is too late even if you learn a lot of new things are if you want to change
a lot of things
it is already too late, it is already end of the project
most probably you can use this learning in the next project but
again next project is going to be new discovery
the requirements or the background may
change in the new project so it may or may not be useful
in the new project or some projects do the rosperosection meeting
during every mile stone so for example at the end of
requirements face you may do a meeting.
but again you will discuss everything about what did you do wrong
in the requirements phase
by the end of that milestone again. where are you going to use it?
the requirements are already completed. you are going to jump into design phase
so probably it may not be useful.
for your project.this current project probably may be useful for some other project but
not in this project so
we need to do lot of frequent reflections within the project this is what Agile does.
at the end of every iterations that is what Agile called a parallel step-by-step
complete delivery .end of every iteration
the project team sits with the
customers the end users and their managers
and discus what went right, what went wrong, what should we improve
in this what you really wanted we do all those reflections
and in this same similar one year project we
spoke about this reflection happens almost
end of every month so you do 12 times the reflection in an Agile project.
where as you do only once
are the maximum two or three times
let me spend
little bit more time on explaining how Agile does it differently.
Ambiguous requirements ,agile understand
requirement will always be ambiguous requirement.agile understands customer
may not know everything in the beginning
so every agile projects start with
what you currently know and tell me the top most five or six
features or requirement that you want in this product .we will quickly show you the
working software
after seeing the working software then you are free to add
new changes your requirements so requirements changes are welcome
in Agile we don't stop the customer to change their mind.we encourage
the customer to change their mind
based on what is already shown to them.
and big up-front planning is not done in Agile.
planning that's happening in agile but it happens over a period of time
there is a release planning there is a iteration planning there is a daily
planning
various planning happens but in agile we do
just in time planning up for example you may not see any schedule
on a contract off by saying
eight months from now what developer A will do
and what activity even work on you will not see that in agile project.
that's going to happen on the end of the seventh month.
at Best you will have every monthly plan and a very high level plan.
other if we don't do complete up-front planning in agile.
reviewing the working software that is the major corner stone of agile.
as we discussed earlier we sure the workKing software
at the end of every month not every two weeks if possible
so we show the working software to the client and ask the client to evaluate the working software
and give additional ideas
and we do it more frequently I'm
as the saying goes we shows the working software to the client
as early as possible and as often as possible.
and I think all Agile development life cycle is iterative
we don't do a complete
Big Bang approach of development.no sequential iterative or incremental
and the delivery is done through
more baby steps really discuss that small iterations
every monthly iteration and frequent reflections by the
development community along with the customers to understand what went
right what went wrong
what should we improve on what else do you know ,do you need
so now coming onto the last two reasons
reason no 6&7 delivery through
small baby steps is always better than
a huge delivery by the end of the development life cycle.
Especially because the requirements are ambiguous
and the customers do not know everything that they want ,if you ask them
tell me, what are the top five or six requirements that you really want.
that develop that do a requirement do Design
quoted, tested show your
working software to the client.let the client
this is fine. playing this is what I expected.but this part is not i wanted
but I want something more also
the understanding of the customer will go much higher
if you quickly show working software. so delivery through
small baby steps are much better than
single huge delivey by the end of the development life cycle.
that is why we should go to Agile.
and frequent reflections by the development team is very important.
when every software development is a discovery by itself then you have to
reflect on what you learn and what should you improve.
what do we do right now in the traditional software development life
cycle
we do some reflections that this mostly by the end of the development
life cycle.
end of the project you do a project retrospection meeting or
some projects called it as the project closer meeting.
are rock in some other name.
that is too late even if you learn a lot of new things are if you want to change
a lot of things
it is already too late, it is already end of the project
most probably you can use this learning in the next project but
again next project is going to be new discovery
the requirements or the background may
change in the new project so it may or may not be useful
in the new project or some projects do the rosperosection meeting
during every mile stone so for example at the end of
requirements face you may do a meeting.
but again you will discuss everything about what did you do wrong
in the requirements phase
by the end of that milestone again. where are you going to use it?
the requirements are already completed. you are going to jump into design phase
so probably it may not be useful.
for your project.this current project probably may be useful for some other project but
not in this project so
we need to do lot of frequent reflections within the project this is what Agile does.
at the end of every iterations that is what Agile called a parallel step-by-step
complete delivery .end of every iteration
the project team sits with the
customers the end users and their managers
and discus what went right, what went wrong, what should we improve
in this what you really wanted we do all those reflections
and in this same similar one year project we
spoke about this reflection happens almost
end of every month so you do 12 times the reflection in an Agile project.
where as you do only once
are the maximum two or three times
let me spend
little bit more time on explaining how Agile does it differently.
Ambiguous requirements ,agile understand
requirement will always be ambiguous requirement.agile understands customer
may not know everything in the beginning
so every agile projects start with
what you currently know and tell me the top most five or six
features or requirement that you want in this product .we will quickly show you the
working software
after seeing the working software then you are free to add
new changes your requirements so requirements changes are welcome
in Agile we don't stop the customer to change their mind.we encourage
the customer to change their mind
based on what is already shown to them.
and big up-front planning is not done in Agile.
planning that's happening in agile but it happens over a period of time
there is a release planning there is a iteration planning there is a daily
planning
various planning happens but in agile we do
just in time planning up for example you may not see any schedule
on a contract off by saying
eight months from now what developer A will do
and what activity even work on you will not see that in agile project.
that's going to happen on the end of the seventh month.
at Best you will have every monthly plan and a very high level plan.
other if we don't do complete up-front planning in agile.
reviewing the working software that is the major corner stone of agile.
as we discussed earlier we sure the workKing software
at the end of every month not every two weeks if possible
so we show the working software to the client and ask the client to evaluate the working software
and give additional ideas
and we do it more frequently I'm
as the saying goes we shows the working software to the client
as early as possible and as often as possible.
and I think all Agile development life cycle is iterative
we don't do a complete
Big Bang approach of development.no sequential iterative or incremental
and the delivery is done through
more baby steps really discuss that small iterations
every monthly iteration and frequent reflections by the
development community along with the customers to understand what went
right what went wrong
what should we improve on what else do you know ,do you need