At the beginning of this book, in Chapter 1, I mentioned the absolute need for an SPMO to embrace a methodology and to use it for all software projects an IT organization will undertake. The next eight chapters described each phase of the SEP methodology in terms of how a business leader would expect the project to flow. Each chapter has provided a solid, evolutionary progression of the project development effort from a management viewpoint. The overview of each phase of the methodology is important because it sets standards and expectations for you, the IT leader. When you are looking at taking on any new effort, you want to ensure that you have the best set of tools, practices, procedures, and so on available to help you succeed. Understanding the SEP process is a key gating factor to your success. Granted, you may personally believe in another methodology and be more comfortable with it, but it really does not matter which methodology is used as long as it achieves the desired level of results and has been defined and documented with an equivalent level of detail as what has been provided in this book.

SEP was chosen because it is the most widely recognized software development project model used in the business world today. There are newer models out there, but the truth of the matter is that most IT leaders choose to go with an industry-proven model that will not limit their ability to succeed. When your reputation and...