|
| This first section is performed prior to any obligation from the customer. In this section, you will define the vision and create a Project Scope. Then you will be required to present in to the customer in the form of a Vision / Scope or otherwise know as a Statement of Work (SOW). To define the vision is to define the project. It is the business reason you are deploying the MetaFrame Access Suite, i.e. the benefits that your customer is expecting to receive from a successful deployment. It is very important as it is the basis for all decisions made throughout the lifespan of a project will be verified against the vision so you will need to spend time on this, make sure it is as accurate as possible. A vision is derived from your customers goals and business case for the project. You will be required to set up a meeting with the customer to identify and quantify this. You will want to discuss what they see as the goals of the project and you will need to make sure to set the proper expectations. In most cases, the customer might not understand completely what they want to accomplish. If this is the case, you will need to explain what the MetaFrame Access Suite can and cannot do for them. Explain the benefits of Server Based Computing, the ease and reliability of application deployment, the flexibility of remote office connective and the ease of anywhere remote access. Then and only then will you be able to create a high-level list of goals that the deployment will address. Once documented, make sure that your customer reviews and understands the Vision, and then have them sign off on it before moving forward with defining the scope of the project. Once we have defined the vision we are able to start scoping what it will take to achieve that vision. I like to break the project scope down to what I call in scope, out of scope. This is probably the second most important element of the project, so be very careful in creating it. You do this by creating a table that documents the vision and any requirements and then you create a table that is broken down into five phases of project management. In each phase you will list the high level tasks that will need to be performed in order to achieve the vision. You will want to start off as vague as possible and then get deeper until you achieve a 30,000 foot view of the tasks needed to achieve the vision. In the scope you be required to list what you are responsible for, what you are NOT responsible for, what the customer is responsible for and the resources that you will be utilizing throughout the project. For example, if you are deploying MetaFrame XP for both LAN and WAN access, you will need modifications to the firewall that requires you to document who is responsible for those changes. In some cases, this may be you, but more often, you will need to work with a 3rd party who is responsible for the routers/firewalls. In this case, you will document the changes required and more importantly, who in the router/firewall group is responsible for what tasks and by what date. You will also create a list of the applications and content the will need to be aggregated to the end-users. This will assist in defining the products needed to achieve the vision. i.e., Should you deploy MetaFrame Secure Access Manager or Web Interface and or both? It will also help define the Project Plan, Proof of Concept and help you determine the time it will take to complete the project. Once you have completed the Project Scope you will want to create a document, called the Statement of Work, that will be comprised of the Vision, any bullet point requirements to the vision and the Project Scope you will follow to define and create the Project Plan to achieve the customers overall vision for the deployment. You will then need to present it to your customer in the form of the most presentable document during a formal meeting. I recommend creating a company template for Statement of Works with the company logo and a bit of color. Then print out the SOW and gather all the people involved with project together for the presentation. This gives you the opportunity to show the customer the professionalism you and your organization brings to the project and you will leave them with the ability to engage your services to continue with the MetaFrame Access Suite project as defined in the Statement of Work. Throughout the lifespan of a project, it will probably be necessary to modify the project scope to meet the vision based on new information found, decisions made and or requirements added. It is important for you to inform the customer of this before it happens and for you to create a policy for a Scope change. This will prevent you from experiencing scope creep and it prevents your project from going over budget and over time. If a scope change is necessary, you will need to have the customer sign off on the change request and modified Project Scope. Always remember that a successful project is one that not only achieves the vision but one that comes in on time and under budget. From my experience, scope additions can and will cause a project to come in over the estimated time and dollar amount. If you present your customer with the knowledge that any addition to the scope will result to a change in the time and dollars estimates then you will have set the proper expectations. Remember that creating the Project Scope, you are creating the rules and plays of the game so you need to be thorough as possible as you are only protecting yourself. The following is an example of a basic Statement of Work. |  Statement of Work
November 7, 2003 Executive Sponsor: Douglas Brown, Owner Project: Citrix MetaFrame Access Suite deployment DABCC.COM would like to deploy the Citrix MetaFrame Access Suite to obtain the following benefits. To have greater centralized management of all their corporate resources, application and content to reduce the total cost of ownership while increasing productivity. DABCC.COM currently has a network infrastructure in place to electronically communicate with remote sites. DABCC.COM would like to make it easier for the end-user to securely gain access to corporate resources on a locked down environment any location at any time. This vision includes the following key objectives: - Enhance application availability for end-users both locally and remotely by providing a secure, reliable, stable, and efficient application deployment system.
- Reduce administration, support and operational costs of supporting front-end workstations.
- Reduce administration, support and operational cost of supporting passwords and password resets
- Provide value added services now and in the future including portal services that will provide for team collaboration, document management, conferencing services and other web and MetaFrame XP Server applications
- Increase productivity of employees by providing them with a comprehensive application and content presentation system.
- Provide reliable printing from any application to both local and remote devices.
- Provide a mechanism for improving productivity through better user collaboration.
- Take advantage of the newly implemented corporate wide Windows 2000 Active Directory.
Project Scope | | | | Project Plan | Prepare and document detailed project plan. | | Infrastructure Assessment | Prepare for assessment questions and inquiry. Schedule times and meetings with DABCC.COM personnel for questions and inquiries. Document and present assessment. | | Proof of Concept | Define and document assumptions Defines tests and success criteria Perform tests Document results | | Analysis Phase Checkpoint | Prepare for and schedule meeting with DABCC.COM for a formal presentation of the Analysis Phase deliverable. | | | | | Server Design | | | MetaFrame Access Suite Design | MetaFrame XP Architecture o MetaFrame XP Farm Design o MetaFrame XP Zone Design o MetaFrame XP Data Collector Design o MetaFrame XP Data Store Design o MetaFrame XP Load Management Design o Applications o MetaFrame Conferencing Manager Design o MetaFrame Printing Design Application Delivery Architecture o MetaFrame XP Web Interface Design o MetaFrame Secure Access Manager Design o MetaFrame XP ICA Client Design Security Architecture o Secure Gateway for MetaFrame Design o MetaFrame Password Manager Design | | Infrastructure Design | File Storage Logon Scripts Infrastructure Modifications | | | |
Design Phase Checkpoint | Prepare for and schedule meeting with DABCC.COM for a formal presentation of the Design Phase deliverable. | | | | | | | | Develop installation procedures & Build initial MetaFrame environment | Prepare the Network Environment. Install MetaFrame XP Server Data Store Install Windows 2000 or Windows Server 2003 Install MetaFrame XP Server with Feature Release 3 Tune MetaFrame XP Server with Feature Release 3 Install Image Applications Image Server Deploy Image Install Remaining Application Install MetaFrame Conferencing Manager 2.0 Configure ICA Client Updates Configure Server Reboots Configure MetaFrame Administrators Configure MetaFrame XP policies Configure Drive Mapping Configure Content Redirection Publish Applications Configure MetaFrame XP Printing Design Install ,Configure and Secure Web Server Install and Configure Web Interface 2.1 Install and Configure Secure Gateway for MetaFrame Install and Configure Remote Administration Install and Configure ICA Clients Install and Configure Microsoft Terminal Services Licensing Install and Configure Windows System Policies Install and Configure MetaFrame Password Manger 2.0 | | Implementation Phase Checkpoint | | | | | | | | | Test, Test, Test | | | Production Pilot | | | Rollout Additional Servers | | | Change Management | | | Readiness Phase Checkpoint | |
| | | | End-User Training | | | Administrator Training | | | Go Live | | | Rollout Phase Checkpoint | | Out of Scope | Router Configuration | | | VPN Configuration | | Proposed Applications | 1. Microsoft Office XP (Access, Excel, Outlook, PowerPoint, Word) 2. Microsoft Visio 2003 3. Symantec Corporate Edition Antivirus 8.1 4. Adobe Acrobat Reader 6.0 5. Microsoft Exchange 2000 Admin Tool 6. Microsoft Active Directory Administration Tools 7. WinZip 8.0 | Analysis Phase estimated X hours starting 11/8/03 Design Phase estimated X hours starting 11/15/03 Implementation Phase estimated X hours starting 11/22/03 Readiness Phase estimated X hours starting 11/29/03 Rollout Phase estimated X hours starting 11/5/03 | |