“Agile” software development is a group of methodologies that are meant to keep a project running smoothly. These methodologies include “test driven development”, “extreme programming”, and the “scrum.”
Surveys (such as this one from Shine Technologies) have shown that agile works in “increasing productivity, quality, and business satisfaction,” while lowering cost. In fact, nearly half of respondents stated that costs were reduced or significantly reduced by agile processes. A whopping 93% stated that productivity was better or significantly better.
The same survey showed that by far the most used of the Agile processes is “extreme programming”. Surely, this technique is one of the most important of Agile’s methods.
Extreme programming is a style of development that encourages frequent releases, with a short development cycle for each one (as described by this article). This means that instead of the entire project being done with all of its feature some time in the (not-so-near) future, the team can release working versions of the most important features right away. Then they can build upon what they have each cycle (adding features, improving functionality, etc), until the customer is completely satisfied. The article says, “Extreme Programming emphasizes teamwork. Managers, customers, and developers are all equal partners in a collaborative team. Extreme Programming implements a simple, yet effective environment enabling teams to become highly productive.”
My experience with agile so far has been a positive one, and I’m excited to learn about the other methodologies throughout my programming career.
Hi Andres,
ReplyDeleteYour post is informative and detailed. I love how you introduced your blog post with the definition of the Agile software development and its methodologies. It is true that the survey from Shine Technologies states that Agile works to enhance your productivity and quality control. When you use Agile, it builds your work efficiency very quickly and that is the key in project building with your team. Your image on the Agile cycle really highlights your post because it helps readers understand the whole concept of it.
One suggestion for your post is to make a reference list from where you find your sources. I highly recommend that for your future blog posts. For example, what is the source of “this article” in your extreme programming paragraph? There is no title and no author for the posted link. And also, try and have a better flow in your writing.
Other than that, you did a very good job on your Agile post. I cannot wait to read some of your future posts in your blog. Keep blogging!
Hello, Andres!
ReplyDeleteThis post was very helpful and informative! I think it is great that you actually reference your findings and supply a link to your sources. It encourages me to actually spend more time researching rather than calling its quits after reading one blog post about the topic.
I also enjoy how you chose such an informative picture to post in your blog! As well as reasoning out how agile programming works, you also displayed it in a detailed picture, which is very helpful for visual learners! Not everyone can decipher such a jumble of words. Next step to becoming the best teacher in the world is to record an audio file for auditory learners as well as make a lab that exercises agile programming for tactile learners.
Hey Andres,
ReplyDeleteI wanted to say that I think you did a very good job with this Agile post because not only did you provide a very good summary with good statistical evidence to back it up but also your own insight on how you felt about using Agile throughout your group. The only thing I would suggest is to provide a little more information on why you thought your experience with Agile was a positive one.