I’d like to add a bit more to the discussion mix pertaining to Risk-Driven model. My company has several Software Architects within the Implementation side of the house and they are responsible for mitigating risk throughout the project by examining the software designs and what is being proposed by the development team as solutions. What we have found over the years is to use sound software patterns and structures, which have been implemented time and time again. If the team wants to go in a new direction with new software patterns or technology, they must first have the Software Architect review their proposal and approve the approach. This helps to mitigate a vast majority of the risk in the development process as the Software Architect give the stamp of approval before any code is developed. Class, any other thoughts on the subject?