Increasingly our customers demand greater visibility of the final product will be delivered, in order to verify the quality and scope that was committed at the beginning of the project. If you work with a waterfall methodology (ASAP, for example) deliveries are planned within the stages of the project as
specification, analysis, design, implementation and go live. This way you can’t tell whether the quality that will be delivered in the go live is equal to the initial idea of the customer. This idea surface is passed only when testing with the End User, and may be too late to make any change.
Well, this is a general and simplistic idea of the waterfall methodology, applying SAP projects. And why we hear about Scrum? You know what is SCRUM?
SCRUM is an agile project methodology. Initially designed for manufacturing companies of cars and consumer products, by Takeuchi and Nonaka in “The New Product Development Game” (Harvard Business Review, January-February 1986). They made an analogy between the projects for small teams multidisciplinary training Rugby Scrum. The first project implementation using this methodology was carried out at Easel Corporation in 1993. The main focus of this methodology is the project management software development. Nevertheless, if analyzed and understood, can be implemented for teams of software maintenance as well.
The main feature of this methodology is delivery or display of products in less time. Thereby, you can receive feedback from your client about the progress of your project not only with documents and screens of the system, but also shares the features already developed and in a timely
to make any adjustment in scope.
Below I’m linking the best documentation and the 2 best blogs I found regarding SCRUM, enjoy…
WebBlog and SDN