Skip to main content

What is the difference between Scrum and RUP?

When I present Scrum to customers, I often hear, "yes but we do RUP, that's iterative, so it's Agile, right?"

I spent some time looking at "Project Management with Rational Unified Process" by Gerhard Vergsteen (in original German) and "Projektmanager", published by the German Society for Project Management. Two thoughts:
  1. The RUP Book got to chapter 3 before it even mentioned people. Then it spent the rest of the book telling "Workers" how to do their jobs in very minute detail. (And yes, even within the iterations, the waterfall lives.)
  2. I looked for the word "Responsibility" (Verwantwortung) in the index of both books. I didn't find it.
I just gave a presentation on Scrum to a group of potential customers in the public sector, one of whom believed quite strongly that good people make good product managers, regardless of the methodology. He's absolutely right on one point. People make projects succeed, not methodologies. And a bad project leader can screw up a project under any methodology.

But Scrum emphasizes people and their responsibilities & committments to each other. It doesn't tell them what to do, but ensures procedurally that if everyone plays by the rules, all the necessary information will become available as quickly as possible so people can do their jobs optimally.

I am now a much better project leader thanks to Scrum. Scrum helped me discover my capabilities.

So I believe methodology and frameworks do make a difference and that Scrum brings out the best in the people on the project.

Update: May 28:
Some futher thoughts on the differences between Scrum and RUP, check out Rational Scrum. I am starting to think that the combination of Lean, Scrum and XP offers the top to bottom framework analagous to RUP, but in an agile context.

Comments

Anonymous said…
This is what I tell anyone who asks about the best methodology: "The best one is the one that works for your company in your situation". Anyone who says otherwise is trying to sell you something.

e.g. In an fast paced company (say a .com) where time of delivery determines if you live or die your points for Scrum are well taken. However not "everyone plays by the rules" so in say pharma, nuclear, defense, there needs to be a more risk based and controlled approach. In those cases RUP has advantages over Scrum.
Peter said…
Hi Anon,

I agree with you that not all projects are suitable for Scrum. I also agree that belief in and passion for what you're doing are essential for success.

So if you deeply believe that RUP is the right method for you and your situation, I will be the first to tell you that you should do RUP.

Having said that, I now have customers in 2 of the 3 fields that you mentioned. Early returns are quite positive. So am I wondering, what are the advantages? And why can't you integrate them into Scrum?

Cheers,
Peter

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …