Agile methods and frameworks


Development methods exist on a continuum from adaptive to predictive. Agile methods lie on the adaptive side of this continuum. One key of adaptive development methods is a rolling wave approach to schedule planning, which identifies milestones but leaves flexibility in the path to reach them, and allows for the milestones themselves to change. Adaptive methods focus on. Adapting quickly to changing realities. An adaptive team changes as per the needs of the project. An adaptive team will have difficulty describing exactly what will happen in the future. The further away a date is, the more wage and adaptive method will be about what will happen on that date. One asked about a release 6 months from now, and the Adaptive team might be able to report only the mission statement for the release or a statement of expected value versus cost.

Predictive methods, in contrast, focus on analyzing and planning the future in detail and cater to known risks. In the extremes, a predictive team can report exactly what features and tasks are planned for the entire length of the development process. Predictive methods rely on effective early phase analysis and if this goes very wrong, the project may have difficulty changing direction. Predictive teams will often institute a change Control Board to ensure that only the most valuable changes are considered.

The methods described in the PMBOK guide and PRINCE2 manuals are on the positive predictive side of the continuum. The methods and frameworks such as Scrum, Kanban, extreme programming, and DSDM are on the adaptive side of the continuum. Therefore, the answer to the question “whether required or not?” – Yes, absolutely. They address different types of problems. In this article, let us focus on the adaptive continuum.

Agile software development is a group of software development methods where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time worked, iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen tight interactions throughout the development cycle.

The Agile Manifesto introduced the term in 2001. Since then, the agile movement, with all its values, principles, methods, practices, tools, champions and practitioners, philosophies, and cultures, has significantly changed the landscape of modern software engineering Commercial software development in the Internet era.

There are many specific agile development methods. Most promote development, teamwork, collaboration, and process adaptability throughout the life cycle of the project.