This week we learned a bit more about the Plan and Document process versus the Agile process. The Agile process that we're a little more used to involves more flexibility when it comes to the requirements surrounding a project. The timeline is broken up into small iterations or sprints where smaller, working chunks of code are created and delivered. In the Waterfall process, delivery of the complete project happens at the end and the requirements are more rigid. When we develop using the Agile process, feedback is often and expected, which can lead to a lot of re-working code and pivoting to accommodate design changes. When using the Plan and Document style, the planning happens up front and any design changes need to undergo a formal procedure to do so. I can see how there are benefits to both strategies depending on the scale and length of the project, but so far I like the flexibility of the Agile process as it is more in line with the way I naturally approach projects with many parts.
No comments:
Post a Comment