Discussion: Division between Agile and Waterfall

Discussion
Name
Institution
Discussion
The information included in the article describe a possible division that exist between Agile and waterfall despite the actuality that more of a continuum existing between the two. Several other skilled practitioners are making attempts of coming up with ways of using both of them. Waterfall and Agile are not differing; they can as well be complimentary.
There is the self-management versus the formal structure whereby Waterfall weighs deeply on formal structural model (which defines the manager as the boss) whereas the Agile principles dictate on self-managing teams (which defines the manager as the facilitator). Supposing the discussion is primarily about the life cycle or process, the waterfall methodology goes stage by stage while the Agile methodology regulates the work in advancement. Scrum regulates it by a sprint while Kanban regulates it by the amount of work items while a blend of both is used by other approaches (Fair, 2012).
There is the heavily plan-drive versus the heavily adaptive, which compares Agile and Waterfall in a more descriptive manner. Rather than thinking what is considered “Agile” and “Waterfall” by other people as individual distinct methodologies, it is more precise to consider it as a endless range of approaches. Many other approaches could be prearranged and accomplished in the middle of the range that merge the precise level of practices and principles driven by the Agile plan with practices and principles that are adaptive with Waterfall to suit a given conditio...