Agile Methodology With Scrum

Inhaltsangabe oder Einleitung

This work is about how lately Agile and especially Scrum have become more and more popular. A lot of people in higher management see the agile way of working as the key to success. But is this actually true? Have we found the silver bullet? Can every individual work in an agile way? If yes, does this mean that the team that he is part of will also adopt and use the agile way of working and thinking successfully? All those questions triggered this research.

One of the first questions we ask ourselves for each of our project implementations is "Which development methodology should we use?". This is a topic that gets a lot of discussion as it’s the way of organizing the work for the project and not as often misinterpreted about a style of project management or a specific technical approach. The two basic and most popular methodologies are: 1.Waterfall: which is known as the "traditional" approach, and 2.Agile: a specific type of Rapid Application Development and newer than Waterfall, but not that new, which is often implemented using Scrum. Both are usable, mature methodologies.

I started by providing basic information about both methodologies (Waterfall and Agile). I try to make the differences between the two methodologies visible and by giving more emphasis to the second one i present the history behind the methodology, the advantages and disadvantages and i try to come to a conclusion on what is agile and what is not. Next, at section two i briefly present the basic Agile Methods and Practices. I continue with section 3, that i explain Scrum and all the ceremonies and roles related to this methodology.