8. Why Agile? Seven Reasons for Agile Software Development: Reasons 6 & 7: and conclusion

8. Why Agile? Seven Reasons for Agile Software Development: Reasons 6 & 7: and conclusion

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

91 thoughts to “8. Why Agile? Seven Reasons for Agile Software Development: Reasons 6 & 7: and conclusion”

  1. Really the video version of Agile is much more effective than the documented version. I did not find any other videos or documents as complete as it is in these 8 sessions on Agile..It's a great initiative.

  2. I would request you to share your 'Scrum' knowledge (which you shared with us in interactive sessions) through 'Scrum Video Sessions'. It will be extremely useful.

  3. amazing ..need more of your videos..way of teaching is very logical and easy to understand.
    if you can manage to share your knowledge on complete Business Analysis concepts that will be great..

  4. Well this is good approach especially when your customer ready to sign the project on T&M basis otherwise mmm.. huge risk on project management.  Anyhow thanks for the knowledge sharing, its really nice to learn things in a simple way. Great.

  5. Excellent raja, you done a great job, U lecturers are like full blue moon with a dark spot, I mean dark spot as you have not given more idea about scrum and retrospective, if possible please le t me know this is my id : [email protected]
    Please let me know any docs available with for retrospective and scrum

  6. Hello Raja, Great video collection, thank you for your insight on Agile vs. Waterfall.  I'm off to watch the rest of your videos

  7. Raja, good series, thanks for this.  Question: What is your position regarding Agile in an environment such as embedded development where showing frequent code builds is not feasible due to the interdependency of the code and the hardware it's controlling (which may not always be available as readily as the code) ?

  8. Thank you very much for all your effort.  Couldn't explain it better!!  Good presentation and explanation.
    Watched all of your videos.  Thanks again.

  9. very nice, simple and clear understanding of the subject. Thanks Sir :)

    If you have more tutorials please share with me.

  10. very good sharing, thanks Raja. we will switch from Waterfall to Agile methodology in our company from this year. you help us have better understand on the benefit of Agile in SDLC.

  11. Thanks you so much for sharing the wonderful information. Its really great and clear understanding concept even though we had half knowledge and ambiguity on both waterfall and Agile!!

  12. So good explanation.. I was very confused with this model now through your videos got the concept very clearly and easily understood. Thank you

  13. Hi Raja, Excellent video on Agile. Wonderful presentation…. Thanks for sharing. Looking forward for more such presentations…. 🙂

  14. I liked all your videos sir… It gave me complete set of understanding about waterfall model and Agile Methodology of software development. Good Presentations and Explanation. Really a good job in helping students to watch when ever they require.
    Thanks a lot sir 🙂

  15. I really liked this series and I loved your video on Scrum. Do you come to Chicago IL to teach? I see you have a LinkedIn account. I will contact you there! Again, thanks for all this great content. You put a lot of effort and work into this. It is fantastic. I'm recommending this series to anyone I now who wants to know why Agile over waterfall. Thanks! Mike Chase

  16. very impressive videos… well arranged the words, data, pictures and so on. also liked the way of presenter describing the slides

  17. Thank you Sir, Your videos helped me alot to understand why we need Agile. Can you please advise how Agile can be adopted in project management ?

  18. Thanks a lot for comprehensive coverage about Agile. Would like to see a session from you how you can prepare an agreement with customer for Agile type of projects both T&M and Fixed Price model. What are the conditions are the assumptions to be mentioned while building the agreement/SOW/Scope statement. Thanks again in advance

  19. Best Explanation Of Agile I Have Ever Seen In YouTube .. Thank You For Such.. Keep Making Videos Like This..

Leave a Reply

Your email address will not be published. Required fields are marked *