Agile (Scrum) Vs Traditional Approach

Traditional Project Management Approach

Traditional project management approach most importantly conducts upfront project planning with focus on fixing the scope, cost and time and managing these project management constraints. It may succeed where requirements can be tightly defined upfront, and there will be no change during the project while at times it leads to a situation where the plan has succeeded but the customer is not satisfied.

Common problem that usually faced by traditional project management approach.

• Late Delivery
• Over budget
• Wrong thing is delivered 

Where the Need Come?

This is the belief that knowledge workers of today can offer much more of their domain than they even know about, and ask for the fully mapped out plan for an ever changing environment.

Agile Scrum

Agile scrum framework was founded on the belief that customer satisfaction is much more important. Therefore, Agile Scrum encourages data-based and iterative decision making through which primary focus is to deliver products that satisfy customer requirements in small iterative shippable increments.
Agile Scrum is used to deliver the greatest amount of value in the shortest time.
It encourages prioritization and Time-boxing over fixing the scope, cost and schedule of a project. The most important feature of Agile Scrum is self-organization, which allows the individuals who are actually doing the work to estimate and take ownership of tasks.

Agile Scrum Vs Traditional Approach

The main difference between the Traditional Approach and Agile Scrum is the priority given to the three aspects of any Project – “Features”, “Time” and “Cost”. Traditional approach takes “Features” as totally fixed by initiation of the project. 

Agile Scrum takes the “Time” and “Cost” in a tight discipline, but reviews the “Features” on priority basis which need to be delivered first

Traditional Project Management 

• Phased : Divide in phases, with technical handoffs to transition
• Sequential: A phase starts when previous phases are completed and perfected
• Non-Iterative: one shot to get everything right
• Plan driven: develop a plan and then execute according to the plan
• Project Flows: like waterfall

Agile Scrum Process

• The terminology “Scrum” derives from a rugby analogy
• Scrum teams value self-organizing themselves
• Initially starts with creating the product backlog where the user requirements have been written in the form of user stories with prioritization of each task.
• Moving with multiple sprints, each provides valuable deliverables.

View PDF