Mistake 5: Failing to Tailor the RUP Appropriately

I have seen some project teams learn about the RUP, decide to adopt it, and enthusiastically jump right in, determined to implement the RUP "by the book." However, the RUP should not be used "in its entirety." In other words, the RUP should be tailored. Some of the artifacts and activities suggested by the RUP may not be appropriate for all situations. Also, some teams may have adopted other artifacts that have worked well for them in the past. There is no reason that these cannot be continued in a RUP-based process. The RUP was intended by its designers to be a suite of processes and artifacts to choose from. The RUP should not be utilized blindly, without eliminating unnecessary artifacts or activities. Most projects should be documented to include their tailoring decisions in a document called the Development Case.