Let's have a peek at what Agile is and how it works.
What is Agile?
Agile methodology is just another methodology to control/track/improve
Project Development. Other project development models include the Waterfall
model etc. The main advantage of Agile is that all the development is broken up
into sprints which allow the teams the flexibility to develop iteratively and
can also help increment the number of chances that a client has to impact the
direction of the project.
What is Scrum?
Scrum is nothing but a means of carrying out software
development in small iterative units called Sprints. These sprints usually form
the backbone of why the development is iterative.
What is a Sprint?
A sprint is usually a 2-4 week cycle where the team is
allowed to develop working code and a demo of which is available at the end of
each sprint length. This working code provides the stimuli to the client through
demos who then come back with feedback (Response) on the demo.
It is essential to choose the right Sprint length. For a
project which has a small duration the Sprint length has to be small while for
a project with a large duration the sprint length can be longer. This is due to
the fact that we want to have as many Stimuli – Response cycles as possible so
that at the end of the product we don’t have a client who goes “Eh? What is
that? I didn't want this to be built in this way” . This leads us to the
conclusion that smaller the sprint length greater the satisfaction of the
client because he has had the chance to influence the direction of the project.
This post is so straightforward and easy to understand that it could be included in a handbook for beginner software developer. You give a concise and sufficient explanation of agile and its concepts, how it can be used and how it helps developers to manage their projects. I like the outline of this post. Question-answer format engages the audience's interest and thus make this post more reader-friendly. I believe that your post would look more appealing if you could include some images, and more convincing if there are links to other professional article regarding agile and its application.
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteHi Ashwin,
ReplyDeleteYou explained the basic terminology of agile in a simple and easy to understand way. I agree that the sprint length must be chosen appropriately to benefit using agile methodology. If the sprint length is too short, the developers might panic and may not be productive. On the other hand if the sprint length is too long, developers might lose focus and the results may not be good. Agile methodology is a win-win for both developers and the client.
Hello Ashwin,
ReplyDeleteI love the format that you used for this blog post by asking a question and then responding to it in a short but straightforward answer. I agree with Huy that your explanation of Agile and Scrum is easy to comprehend as I was a bit confused about the techniques when I first read about them. I also agree with Huy that you could add a picture or a link to more information on Agile in case other readers are interested in learning more about the methodology. You also misspelled a few words such as missing an “s” in the word “because” in your last sentence of your blog. Overall good job.
Hi Ashwin,
ReplyDeleteNice Blog Post, You explained agile terminology by using question and answer format. I found your agile explanation was easy to read. Good work. But it would be an even better post if you add an image or diagram about agile. Some additional information links would be great for user who want learn more about agile. Overall, Nice work!