Both methodologies are considered to be Agile and approach project activities in the iterative way. However, RUP methodology calls for a formal definition of scope and major project milestones are associated with specific dates. SCRUM methodology uses project backlog instead of scope and allows the backlog to be redefined at the end of each iteration (usually about every 4 weeks). In addition, RUP subdivides the project lifecycle into 4 major phases (Inception, Elaboration, Construction, Transition). Even though it encourages concurrent workflows across the entire cycle, the general understanding is that certain activities will peak during certain phases (for instance, requirements analysis will spike during the elaboration phase). On the contrary, SCRUM dictates that the entire “traditional” lifecycle fits into one iteration. In other words, a workload for one iteration at a time is determined and then the entire cycle occurs within one iteration (e.g. the requirements for a particular feature are collected, documented as a user story, then coded, tested and presented for the user review).
RUP vs. SCRUM Comparison
|Cycle||Formal Cycle is defined across 4 phases, but some workflows can be concurrent.||Each sprint (iteration) is a complete cycle.|
|Planning||Formal project plan, associated with multiple iterations, is used. The plan is end-date driven and also has intermediate milestones.||No end-to-end project plan. Each next iteration plan is determined at the end of the current iteration (NOT end-date driven). Product Owner (Key Business User) determines when the project is done.|
|Scope||Scope is predefined ahead of the project start and documented in the Scope document. Scope can be revised during the project, as requirements are being clarified, but these revisions are subject to a strictly controlled procedure.||Instead of scope, SCRUM uses a Project Backlog, which is re-evaluated at the end of each iteration (sprint).|
|Artifacts||Vision/Scope Document, Formal functional requirements package, system architecture document, development plan, test plan, test scripts, etc.||The only formal artifact is the operational software.|
|Type of Project/Product||Recommended for large, long- term, enterprise-level projects with medium-to-high complexity.||Recommended for quick enhancements and organizations that are not dependent on a deadline.|