Describe some of the differences between using an Agile process and using a Plan and Document (or Waterfall) process
The Agile and the Plan and Document are two different processes ultimately looking to produce the same thing, great software that meets the end customers needs. Each process goes about this goal in very different ways, each with their own advantages and disadvantages.
The Agile process is all about quick, short iteration cycles. A developer takes input from the customer/end user and focuses in on one small aspect of the input, quickly iterating on a new feature or fix or behavior change. They then repeat these small iterations as necessary until all the feedback/input from the customer/end user is addressed.
The Plan and Document process (or Waterfall) takes a much longer, sequential view of a project. It sets to understand all the requirements, all the possible timelines, all possible scenarios before actually starting any work. The overall goal is to properly estimate accurate time and effort to each stage, so you can plan out your work and stay on track and deliver an end product on time, containing the planned out requirements.
The Agile process has advantages in being locked into a continuous cycle of feedback and improvement; short, quick cycles that lead to the end user getting results faster. By also using short cycles, typically there's less risk; one iteration gone awry doesn't spell disaster.
The Pan and Document process has advantages in that it's predictable and easy to understand the current progress of the project; Everyone has a clear understanding of were they and others should be in development of a project. To that end, when working across multiple large teams the detailed planning and documentation helps coordinate everyone.
0 comments:
Post a Comment