It's an iterative Arctic Blast Review approach! Do what you need to when you need to - that way you'll manage change in the project a lot better. You're far less likely to waste time writing documents that end up never being used when the customer changes their mind, or you hit a snag in development. is RUP for you? Maybe it is. If you have a project team larger than five developers, then chances are you will actually benefit from a formal and all-encompassing Process. RUP would be a good foundation for you to create your own Process on. If RUP isn't an option as far as you're concerned, then that doesn't mean you shouldn't be trying to define the software development process you use! As I said before - RUP is a foundation for a Process. This does NOT mean that all Processes are RUP. https://consumerscomment.com/arctic-blast-review/