ABSTRACT
The scrum approach focuses on the business needs of projects when developing products and services. It provides the same benefits with line management with only minor modifications to the tools. The scrum approach strips away non-value-added activities and impels delivery by focusing on the immediate details. It is not possible to interpret scrum as anything but a disciplined development model. Its counterpart, the waterfall model, is a sequential development framework in which each major phase appears to be “pouring” its results into each successive phase. Scrum is not only iterative, but has actions that require team learning and allows the rest of the project to be built on such learning. Much team learning will occur during each cycle of the scrum activities for the project in the form of the sprint retrospective and customer planned input. Hence, we control the end game activities-the customer going directly to the developer-while still allowing the customer to make adjustments to the product as time passes. If anything, the scrum approach enhances the ability of the customer to add changes to the product.
