Segregating the EIF artifacts into three classifications helps to thresh the wisdom from this resource m lange. Think of the EIF as containing three types of resources: instructional documents, deliverable templates, and white papers. Once installed, you’ll find the following contents in your EIF directory.
EIF Setup and Overview
EIF System Design Guidelines
EIT Enterprise Project Overview
EIF Project Plan
EIF Red Flags
EIF Requirements Specification
EIF System Design
Microsoft Project 2002 Documents Overview
Microsoft Project 2002 Enterprise Codes Overview
Microsoft Project 2002 Enterprise Project Management Architecture Guide
Microsoft Project 2002 Issues Overview
Microsoft Project 2002 Notifications Overview
Microsoft Project 2002 Project Guide Architecture and Extensibility
Microsoft Project 2002 Resource and Skills Management Guide
Microsoft Project Server 2002 Architecture and Extensibility
Microsoft Project Server Configuration Guidelines White Paper
Microsoft Project Server Data Migration
Microsoft Project Server Security Architecture and Planning Guide
Microsoft SharePoint Team Services Integration Architecture and Extensibility
Migration to Microsoft Project Professional 2002
The white papers are available redundantly on the Microsoft site. The selections listed in the preceding section pertain specifically to enterprise configurations and represent a slightly expurgated list of all available white papers. You can find a complete list of Project 2002 version white papers at http://www.microsoft.com/office/project/techinfo/whitepapers/default.asp. The important thing to keep in mind is that half of the EIF file payload is composed of white papers that are available elsewhere. I strongly recommend that you read the white papers and all of the other documentation Microsoft makes available through TechNet and MSDN, but I do not discuss the white papers included in the EIF bundle here. Instead I focus on the unique information the EIF contains.
Examining the deliverable templates and instructional documentation makes one significant first impression: You have a project on your hands. Have you already begun your planning? Have you appointed a project manager for this initiative? Who are your stakeholders? If you don’t have the wherewithal to organizationally support your Project Server implementation as a formal project and a model for the business rules driving your implementation, then you should ask yourself why you’re implementing project management software. No project management application provides a silver-bullet solution. Project management is a discipline and, as such, adding a tool will confound an organization that hasn’t already succeeded in implementing the management disciplines of project management. Your organization must have at least made a commitment to project management disciplines to have reasonable expectations for success.
The EIF Setup and Overview document provides a high-level framework for conducting your Project Professional 2002 and Project Server 2002 implementation, as you can connect the process it outlines to its recommended deliverable templates. The EIF System Design Guidelines document is a very compressed, comprehensive guide to the feature-to-organizational use mapping considerations you’ll make in pursuing your EIF implementation strategy. It includes detailed instructions for completing the deliverable templates. These two documents embody the EIF strategy and the instructions for its practical use. You also have an FAQ document, which clarifies some of the concepts expressed, and the EIT Enterprise Project Overview document, which is a primer on the Project Server big picture. Consider this last document optional reading if you read the first chapter of this book.
The list of templates can be bifurcated along the lines of training outlines and process templates. The latter group includes a model project plan to govern your implementation effort. An interview question-and-answer template constructed in Excel supports the creation of a Red Flags Report from a Word template and the creation of a requirements specification document from another Word template. The information gathered during the requirements phase is coalesced into a system design document provided as a multitab workbook.
The other half of the deliverable templates consists of training outlines for the various roles predefined in Project Server. Training is an important step and I endorse its emphasis by these template inclusions. Essentially, the documents are lists of specific Microsoft Project 2002 courseware training modules recommended for each predefined role. The Project 2002 courseware itself is available for download on the Microsoft Web site at http://support.microsoft.com/default.aspx?scid=kb;en-us;325846. You must tailor these recommendations to your specific needs, keeping in mind that you may not implement all of the default roles or you may implement other roles not considered by the EIF architects. Training is an important reason to have outside resources lined up for your Project Server implementation.