Scrum vs Traditional Project Management

Scrum emphasis is on people, traditional project management’s emphasis is on processes.
In Scrum, documentation is minimal – done only as required. In some traditional methods, it is very comprehensive – often not fit for the scale of the project.
Scrum process style is iterative. Traditional is often more linear.
In Scrum, upfront planning is low, traditional high.
In Scrum, prioritisation of requirements is based on business value and regularly updated. Traditional is fixed in the project plan.
In Scrum quality assurance is customer centric. Traditional is more process centric.
In Scrum organisation is self-organized. Traditional is ‘managed’.
In Scrum, the management style is decentralized, traditional is centralized.
In Scrum change normally includes updates to prioritised product backlog. Traditional normally goes through a formal change management system.
In Scrum leadership is collaborative, servant leadership, vs traditional command and control.
In Scrum performance measurement business value plan conformity, return on investment (ROI) early/throughout project life, vs traditional end of project life.
In Scrum, the customer involvement is high throughout the project, traditional varies depending on the project lifecycle.

SALE: was ~~[woo_multi_currency_exchange price=’699′]~~

[woo_multi_currency_exchange price=’405′]

SALE: was ~~[woo_multi_currency_exchange price=’310′]~~

[woo_multi_currency_exchange price=’99’]