Management of IT Systems and Projects Assignment - "Work Breakdown Structure & Project Schedules using Microsoft Project"
There are two parts to this assignment:
Part 1: MS Project
Project Title: Dai-Ichi Corporation Australia (DCA) - SAP Project Phase 1
Project Background: The Dai-Ichi Corporation is a major international player in the mining industry. The head office in Italy has recently completed the rollout of SAP for its European headquarters. The decision has been made to deploy the same platform into the Oceania operations commencing with Australia. Given the distance and time zone difference, a decision was also made to deploy the SAP instance on the cloud. This will facilitate the SAP instance to be managed out of Europe.
Final negotiations for cloud resources has been completed between Amazon and Dai-Ichi Europe. The Australian team will be the first Cloud SAP instance for the Dai-Ichi group. As such it was decided to break the project down into different phases. You have been appointed as the project manager of the pilot phase and you have been given the following resources.
You team comprises the following:
1) Paulo Mossimo - SAP Expert from Italy - familiar with deploying SAP in house
2) Sanjay Srivastava - Cloud Architect - recently hired from HP with experience deploying Amazon Web Services
3) June Smith - SAP Expert - recently hired from Fujitsu.
4) Larry Jones - Linux Apache, MySQL, C programmer. LAMP Specialist.
5) Jenny Harvey - Linux Admin and LAMP Specialist.
Your brief is to set up a test instance of SAP on the AWS cloud infrastructure. You have 12 weeks to get the first instance of the SAP up and running. Since Cloud resources are instant on resources, it is assumed that you can start immediately.
A total of 20 Cloud servers are available for you to create the SAP instance. You don't need to use all of them as they cost $2750.00 per month per instance.
The configuration of the Test Instance is as follows:
2 x Database Servers
2 x Application Servers
3 x Web Services Layer Servers
Deliverables of Part 1MS Project File -
This component requires some preparation and then data entry into the MS Project file as follows:
1.1 Create a WBS (Work Breakdown Structure for the Dai-Ichi SAP Cloud Pilot. See Schwalbe pg. 198-208) for the above scope of work and translate this into a task list in MS Project 2013. Add dependencies and durations to create a Gantt chart (See Appendix A Schwalbe for detailed instructions on how to use MS Project to create a Gantt Chart). You might want to consider adding regular Steering Committee meetings and communications to specific stakeholders on the progress of the project.
1.2 Provide the critical path for your implementation. Illustrate your critical path using a sequence of nodes and edges along the following lines.
1.3 Add resources to your Gantt Chart and print a resource based task list (who does what when, view of the project) for your own reference.
1.4 Finalise your pricing and technical specs and calculate your budget.
1.5 Microsoft Project File.
1.5.1. Implement the project scope into MS Project 2013 (or 2010), showing costing and indenting subtasks appropriately.
a. Use the outline numbering feature to display the outline numbers. For example your WBS should start with
i. 1.0 Initiating...
b. Enter any duration or dependencies
c. Allocate resources
d. Show costing for your staff members
e. Document WBS and insert into MS Project.
f. Cut and paste into Project Report:
i. Gantt Chart
ii. Network Diagram showing critical path
iii. Resource Schedules
Part 2: Project Report
2.1 Create a Word Document that details how the project will be managed. Consult Schwalbe p 161-165 for some hints on how to construct the content of your Summary Project Management Plan.
The Project Management Plan (PMP) should not exceed 10 pages excluding diagrams and tables. This is not a full PMP but rather an abridged summary overview plan.
As this is not a complicated project, keep the documentation simple and clear. Omit headings that are not applicable. Most of the content you need for the PMP is provided in the scope document above either explicitly or implicitly. Read it carefully to extract, extrapolate and interpret the information required. For example: What are the deliverables of this project? What are the objectives? What are the benefits?
How will the project be measured for success? What are the constraints? What are the project controls (Hint Steering Committee)?
Do not put version control in your summary PMP. (In a real project, the PMP is a living document subject to change control, and versioning is critical.)
You must include the following as a bare minimum:
Objectives
Deliverables
High level technical requirements
Project Management Controls
Resources (See 1.3 above)
Budget
WBS diagram - Schedule (Gantt Chart and Critical Path using the Network Diagram), these should be briefly discussed, including any critical assumptions and dependencies.
Attachment:- Assignment File.rar