Bad Scrum, but Pretty Good RUP
Most metals have a bit of springiness to them. If you want to bend them to a certain shape, you have to bend them further than that. When they spring back a bit, they’ll take the shape you want.
Today, I was looking at a milestone chart for a project transitioning from a serial lifecycle to an Agile one in a large organization. At first, I despaired at the picture it painted. There are Requirements and Design phases for the release, and a “hardening sprint” before release. Don’t get me wrong. Things are much better than they were before the transition started, but there is quite a way to go before this effort reaches what I would call truly Agile.
Then it struck me.
This is one of the best implementations of RUP I’ve ever witnessed. When I’ve seen organizations adopt RUP, they’ve done so in a very document heavy manner, maintaining all of the gate reviews they had before. In shooting for Agile, this organization has already hit a fairly lightweight version of RUP, eliminating a lot of documentation and gate reviews, and shortening the development iterations and release cycle.
Instead of a struggling Agile adoption I now see a successful RUP adoption. And this is just the beginning; perhaps they’ll reach Agile, yet. That’s not a bad state of affairs.