Agile: Moving forward

AGILE:

     What is Agile Development and what can it do for your team? 

   
In the past companies have conducted projects by using a Waterfall approach which would be considered starting from the beginning and moving step by step and advancing further. The problem with this though is that it does not allow as much room for change. Changing a phase one would mean redoing every other step after it that relies on the foundation. Apprehensively it is a very linear approach.

Look below and lets say a group approaches the same project with the same ideas and requirements in mind. But in order to achieve the final result they can take a different route. On the right side it shows the Agile chart, you can see how things are done almost at the same time and are iteratively processed. In the 2nd step the Initiation and Analysis are done at the same time and can be redone and change without delaying the timing of the project. 

The team that endorses and are the main founders of the Agile method has a Manifesto for Agile Software Development on their webpage. In it they describe in a short simple paragraph the idea and use of their method.

In the Work Place

Microsoft endorses the use of Agile for software development as stated in their Research Page. They prefer the variant that uses Scrum. They like the implementations on small scale projects but have doubts and concern on large projects with 20 members or more because the design is not as sustainable with such a large amount of people.

Overall when deciding which method to use whether Waterfall or Agile or any other development Model. Timelines, experience, resources, and requirements should be the factors in deciding your plan of action. With a Waterfall method, things can be executed faster and quicker so simple and small projects with definite requirements can be completed. With more freedom on a project I would prefer the Agile method because there would be more room for improvements or mistakes