Using RUP to manage small projects and teams
From the developerWorks archives
Date archived: May 13, 2019 | First published: July 15, 2005
from The Rational Edge: Too frequently, software project managers assume that the Rational Unified Process, also known as RUP, is not appropriate for software projects of limited scope. This article offers two typical examples of small projects that benefited significantly from adherence to RUP through the phases of iterative development.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.