Scrum or Classic Project Management: Which is Better?
Team Clarizen | Jul 12, 2021
Scrum project management is rooted in Agile methodology, which is a framework in which small teams carry out the incremental and iterative delivery of a product.
(…) There are generally two main types of methodologies exercised depending on project specs: Classic Project Management and Scrum.
(…) “The Iron Triangle” is a term for the basic foundation of any project management method and refers to the cost, schedule and scope of a project.
(…) Scrum is a process framework that was developed for project management after technology—and more specifically, software—became integral components of major projects. The term itself simply refers to an “ordered formation of players used to restart play,” and the method is all about prioritization and time-boxing over fixing the scope, schedule and cost of a project.
(…) The main difference between scrum and classic project management methodologies can be summed up as fixed scope vs. iterative decision making. Classic project management calls for project managers to look at the development as a whole whereas Scrum has no problem dividing it up into segments.
One of the largest discrepancies in the two techniques is due to the simple differences in terminology. The following are some ways in which the terms differ:
Schedule = Sprint (or Release)
Scope = Sprint Backlog
Work Breakdown Structure = Task Breakdown
Productivity = Velocity
Estimate to Complete = Burndown Chart
(…) Can You Use Both? If you can’t decide between the two, it’s perfectly acceptable for organizations to use both waterfall and scrum. It’s not uncommon for development teams to use a scrum method, for managers to use JIRA to handle their teams and for project managers within the same organization to use a waterfall method.
URL = https://blog.planview.com/scrum-classic-project-management-better/