Scrum is one of the most popular agile methodologies.
It is an adaptive, iterative, fast, flexible, and effective methodology that delivers value throughout a project. Scrum ensures transparency in communication. It also creates an environment of collective accountability and continuous progress. The Scrum framework, as defined in the SBOK™ Guide, supports product and service development in all types of industries. It supports any type of project, irrespective of its complexity. (Download the SBOK™ Guide here.)
One of Scrum’s key strengths is its use of cross-functional, self-organized, and empowered teams. Teams divide their work into short, concentrated work cycles called Sprints.
Traditional project management emphasizes detailed upfront planning for the project. It focuses on fixing the scope, cost and schedule – and managing those parameters. Whereas, Scrum encourages data-based, iterative decision making. The primary focus is on delivering products that meet customer requirements.
Scrum promotes prioritization and time-boxing over fixing the scope, cost, and schedule of a project. This approach delivers the greatest amount of value in the shortest amount of time. With Scrum, the individuals who are doing the work estimate and take ownership of tasks.
Traditional project management emphasizes conducting detailed, upfront planning for the project. The emphasis is on fixing the scope, cost and schedule – and managing those parameters.
Scrum encourages data-based, iterative decision making. The primary focus is on delivering products that meet customer requirements.
Scrum promotes prioritization and time-boxing over fixing the scope, cost, and schedule of a project. This delivers the greatest amount of value in the shortest amount of time. An important feature of Scrum is self-organization. This allows those doing the work to estimate and take ownership of tasks.
The following table summarizes many of the differences between Scrum and traditional project management:
|Parameters||Scrum||Traditional Project Management|
|Emphasis is on||People||Processes|
|Documentation||Minimal – only as required||Comprehensive|
|Prioritization of Requirements||Based on business value and regularly updated||Fixed in the Project Plan|
|Quality assurance||Customer centric||Process centric|
|Change||Updates to Productized Product Backlog||Formal Change Management System|
|Leadership||Collaborative, Servant Leadership||Command and control|
|Performance measurement||Business value||Plan conformity|
|Return on Investment||Early/throughout project life||End of project life|
|Customer involvement||High throughout the project||Varies depending on the project lifecycle|
If your organization is interested in scheduling a private SCRUM class, please use this contact form: