Well, this will be the second to last journal for my software engineering course at CSUMB. This week, we are tasked to discuss some of the differences between the Agile process and the Plan and Document process, often referred to as Waterfall. To start, Agile is a process that doesn't really concern itself with how long something will take or how much something will the end client. Compared to Agile, the Waterfall mythology also tends to heavily rely on the the previous work that was done, to develop in a sequence like approach. Agile doesn't really do this, Agile focuses on developing in iterations that are referred to as sprints where the work that is being done is broken down into smaller pieces that don't necessary have to depend on previous work. Additionally, Agile is a mythology that revolves around evolving requirements, so in-terms of client feedback, Agile allows for me for this. Waterfall, on the other hand, focuses on have specifications upfront with a more rigorous process in changing the requirements when compared to Agile. Overall, I would say that Agile is best suited for projects that evolve over time, while Waterfall is best suited when a project will have very little change once the project is deployed.
No comments:
Post a Comment