Your organization has just completed the Initiation Process for implementing an Email System Upgrade. It was identified in a recent meeting with management leaders from the Sales, Consulting and IT departments that the current email system is causing significant amount of business interruptions and must be updated immediately. You have been assigned the role of project manager to develop the project schedule and budget. As project manager, you are responsible for implementing and enforcing the project schedule and its estimates, expected costs, and the techniques and methods that will be chosen to execute and control the project. The project is being initiated with the following initial project scope in mind:

• There are five email systems currently being used across twelve departments and offices. These will be replaced and consolidated into one email system.
• New Email Standards and Protocols will be established and training provided to all departments.
• All 2000 current email users will be converted to the new system, and 500 new users that did not have email before will be added.
• Users will have both LAN and remote access to email.
• Help desk and support infrastructure will be set-up to accommodate the new system.
• Equipment will be salvaged.

User PCs will be upgraded to accommodate thenew email system.

Part 1 Deliverables

• Use MS project software to complete the following:
• Creating your WBS in MS Project SW or a similar tool, then the project schedule.Using MS Project, enter all the WBS deliverables/outputs then all associated activities, and tasks into a new MS Project file and save it with your name and course #.
• Sequence your activities. Now that you have defined your activities, ensure that they are listed in the order that they should be completed. If one activity is dependent on another, be sure to list that dependency in the "Predecessor" column.
• Activity estimation. Assign an initial work effort to each of the activities.

Provide an estimation framework. This should be approximate. You're allowed to make assumptions as long you're being realistic.The framework should be estimated in days.

• Duration estimation. Now that you have defined the schedule activities, sequenced them in a logical order and defined the dependency relationships between them, and estimated resources, add the activity duration for all activities then add a start date to each task. The finish date should automatically populate. If you have a conflict, review your predecessor relationships. Remember, you do not need to add anything to the summary tasks (the deliverable/output). The summary tasks will update automatically as soon as you link the activities.
• Assign resources. In the resource name column in your MS Project file or similar SW, add a resource name to each task. You may use hypothetical names.

Part 2 Deliverables

• Based on your work in Part 1:
  • Apply the standard PERT estimating formula and calculate the expected estimate (Te) for each activity.

Example Group Project Table

Task	Most Optimistic	Most Likely	Most Pessimistic	Expected Estimate

• Explain the purpose behind the PERT calculations.

Submitted Assignment:

• Deliverable (Part 1)
  • There is no length to how many tasks your schedule should be made up of, but it should be long enough to convince your CIO at a glance that this is all the work that needs to be completed for this project. Ideally, you shouldn't have less than 50 tasks and your WBS should be at least 3-5 levels.
• Deliverable (Part 2)
  • PERT estimate calculations and your explanation of them.