Agile methods of software development are one of the most important requirements in the modern development scenario. As businesses operate in a fast changing manner, we need development which can keep pace with this scenario. This is done using program specification, design and implementation being interleaved in agile development and the software being released as versions and updates as opposed to plan driven development which is done in different phases and development stages.
Agile methods reduce overheads in the development process by limiting documentation and focusing more on code rather than design, while being able to adapt to changing requirements quickly. Agile systems focus more on customer involvement and incremental delivery ,embracing change quickly while maintaining simplicity to adapt quickly to that change.
Extreme programming was released as an agile method technique which focused on more and more versions being built as part of the release cycle and increments being delivered to the customers every few weeks. A test was decided for every build which were made multiple times a day often and the build was declared successful only if it passed that test. Builds were often sent out as small releases after incremental planning. The programming was done as pair programming and the ownership of the code was collective such that different people could add increments if needed. Any changes were continuously integrated into the system so the changes could be made tested quickly by unit testing. The pace was kept reasonable and sustainable so that the people working would be able to complete their tasks on time and such that the customers could reliably get their products. Also an On-Site customer was kept for the use of the XP(Extreme Programming) team’s use who was responsible for bringing system requirements to the team for implementation.
Due to the difference in Agile methodology, agile project management is different from standard project management which is plan driven. Agile project management is adapted to incremental development and the practices used in agile methods.
Scrum is an agile method which focuses on managing iterative development instead of the regular plan driven approach. Scrum has three phases – the initial outline planning phase where we establish the objectives for the project and create the architecture, The second phase is a series of sprint cycles, where each cycle develops an increment of the system. While the third is the project closure phase wraps up the project and completes the required documentation.
Scrum sprint cycles are usually fixed for about 2-4 weeks, the planning starts with the product backlog which states the things to be done and the selection of features by the team who work with the customer from the project backlog which are to be done. The scrum master is a facilitator who arranges daily meetings, measures the progress of the work and communicates with customers and management outside of the team. The main benefit of scrum is that it breaks down the project into a set of manageable and understandable chunks. And that customers see on-time delivery of increments and gain feedback on how the product works.
Scaling agile methods for large systems is tricky as they need up-front design and some documentation. Hence we’re concerned with 2 methods scaling up and scaling down where ‘scaling up’ is concerned with using agile methods for developing large software systems, while ‘scaling out’ is concerned with how agile methods can be introduced across a large organization.
Despite the benefits and necessity of Agile Methods, it has its flaws and hence most practical development methods are a mixture of plan-based and agile development.