Software Engineering Week 7

 Two important project design methodologies are the Waterfall process and the increasingly popular Agile process. While both processes have been tested and are proven to be effective, there are key differences between the processes that may be a deciding factor over which methodology to use for a project. Some of these differences include how a project design is approached, the flexibility afforded by the methodologies, and how the project is planned. When approaching a project, Agile and Waterfall processes greatly differ with Agile processes breaking their tasks up into sprints and utilizing stories to track tasking. Agile also emphasizes iteration, feedback and adaptiveness. In comparison, projects using the Waterfall process emphasize rigidity and sequential tasking where tasks are clearly defined and must be executed one after another. These two approaches affect the flexibility afforded, where Agile allows easy adaptability to changing requirements, where Waterfall projects are more resistant to change. Lastly, project planning with Agile is intended to continuously evolve. As previously stated, Agile utilizes sprints which are intended to provide tasking for the short term. With Waterfall, all the project planning is done at the beginning with no flexibility or updates intended. Each of these processes offer unique strengths depending on what a project is required. If flexibility is needed in a project, the Agile process is a great choice. However, if a project demands stability and clearly defined requirement, the Waterfall process makes more sense.