Project Management: Cloud Based SAP Instance Implementation For Dai-Ichi Corporation
Objectives and high-level requirements
The objectives of the project are as follows:
- To deploy the same platform into the Oceania operations
- To deploy the SAP instance on the cloud
- To facilitate SAP instance to be managed out of Europe
The high-level requirements for the project include:
- 2X Database servers
- 2X Application servers
- 3X Web Services Layer servers
- X86 Image- per instance
- SAP Cloud instance
- JIRA
The project can be controlled by utilizing methods that are as follows:
Conducting regular meetings: It is very much necessary to conduct regular meetings in so that the project team members can able to discuss about the project hurdles as well as can update the tasks of the project effectively. Team meetings involves identification of dependencies as well as risks that are assigned to the tasks.
Using earned value analysis: Earned value analysis is one of the project control technique that mainly helps in measuring the performance of the project. It is one of the technique, which not only assists in quantifying project progress but also helps in controlling project. It is very much necessary to keep an eye on the CPI as well as SPI, which are related with earned value analysis in order to ensure that the entire project will be completed within the estimated budget and time.
Using critical path analysis: If the activities that are related with critical path is delayed then the project completion date gets impacted and therefore inn order to monitor as well as control the project it is necessary to keep proper track on the critical path of the project.
The resources that are required in the project are listed in the table below:
|
Resource Name |
Type |
Initials |
Max. Units |
Std. Rate |
Accrue At |
Base Calendar |
|
Project manager |
Work |
P |
100% |
$2,000.00/day |
Prorated |
Standard |
|
Paulo-SAP Expert |
Work |
P |
100% |
$2,000.00/day |
Prorated |
Standard |
|
Sanjay-Cloud architect |
Work |
S |
100% |
$7,500.00/month |
Prorated |
Standard |
|
June-SAP expert |
Work |
J |
100% |
$7,500.00/ month |
Prorated |
Standard |
|
Larry jones-LAMP stack specialist |
Work |
L |
100% |
$3,500.00/ month |
Prorated |
Standard |
|
Jenny Harvey-Linux Administrator+ LAMP |
Work |
J |
100% |
$3,250.00/ month |
Prorated |
Standard |
|
Amazon cloud infrastructure( X 86 image-Per instance) |
Work |
100% |
$2,750.00/ month |
Prorated |
Standard |
|
|
SAP Cloud instance-Site License for Australia |
Material |
$200,000.00 |
Prorated |
|||
|
JIRA |
Material |
J |
$50.00 |
Prorated |
||
|
Travel and accommodation expenses for Paolo |
Work |
100% |
$10,000.00/month |
Prorated |
Standard |
It is estimated that the cloud based SAP instance for Dai-Ichi Corporation will be completed successfully within the budget that is around $864,668.75. The table below helps in reflecting the cost that is needed to complete each of the activities of the project.
|
Task Name |
Duration |
Cost |
|
Creating cloud based SAP instance for Dai-Ichi Corporation Australia |
60 days |
$864,668.75 |
|
Initiation Phase |
4 days |
$9,387.50 |
|
Defining scope of the project |
0.5 days |
$1,000.00 |
|
Defining project time |
1 day |
$2,375.00 |
|
Defining cost constraints of the project |
1 day |
$550.00 |
|
Defining high level requirements |
0.5 days |
$1,462.50 |
|
Forming project team |
1 day |
$4,000.00 |
|
Milestone 1: Completion of project initiation phase |
0 days |
$0.00 |
|
Planning phase |
6 days |
$211,650.00 |
|
Developing project plan |
1 day |
$2,550.00 |
|
Creating schedule of the project |
1 day |
$375.00 |
|
Creating detailed budget for the project |
2 days |
$4,750.00 |
|
Obtaining sign off on plan |
0.5 days |
$1,437.50 |
|
Getting approval for the project |
0.5 days |
$2,000.00 |
|
Signals approval by steering committee |
1 day |
$200,537.50 |
|
Milestone 2: Completion of planning phase |
0 days |
$0.00 |
|
Design/build phase |
36 days |
$220,818.75 |
|
Detailed requirement gathering |
1 day |
$202,375.00 |
|
Security requirements |
1 day |
$162.50 |
|
Infrastructure planning |
1.5 days |
$206.25 |
|
System operation strategy |
1.5 days |
$825.00 |
|
Training preparation |
2 days |
$4,000.00 |
|
Configuration and development |
2 days |
$5,100.00 |
|
Unit/Process business acceptance testing |
3 days |
$525.00 |
|
Infrastructure implementation |
5 days |
$500.00 |
|
Implement AWS Cloud Infrastructure |
5 days |
$0.00 |
|
Develop SAP on the System |
4 days |
$0.00 |
|
Test the SAP on the AWS Cloud Infrastructure |
3 days |
$0.00 |
|
Find Bugs and Glitches |
2 days |
$0.00 |
|
Troubleshoot Issues |
2 days |
$0.00 |
|
Make Some Modifications in System Function |
3 days |
$7,125.00 |
|
Milestone 3: Completion of design/Build phase |
0 days |
$0.00 |
|
Go live phase |
10 days |
$414,437.50 |
|
End user training |
3 days |
$7,500.00 |
|
Business simulation |
2 days |
$0.00 |
|
End user practice in the system |
1 day |
$200,375.00 |
|
Infrastructure finalization |
1 day |
$200,137.50 |
|
Data migration to production |
2 days |
$4,050.00 |
|
Pre-go live operations |
1 day |
$2,375.00 |
|
Milestone 4: Completion of go live phase |
0 days |
$0.00 |
|
Closure phase |
4 days |
$8,375.00 |
|
Post-project review |
1 day |
$2,000.00 |
|
Stakeholder sign off |
1 day |
$2,375.00 |
|
Documentation |
2 days |
$4,000.00 |
|
Milestone 5: Completion of project closure phase |
0 days |
$0.00 |
|
Task Name |
Duration |
Start |
Finish |
|
Creating cloud based SAP instance for Dai-Ichi Corporation Australia |
60 days |
Mon 4/9/18 |
Fri 6/29/18 |
|
Initiation Phase |
4 days |
Mon 4/9/18 |
Thu 4/12/18 |
|
Defining scope of the project |
0.5 days |
Mon 4/9/18 |
Mon 4/9/18 |
|
Defining project time |
1 day |
Mon 4/9/18 |
Tue 4/10/18 |
|
Defining cost constraints of the project |
1 day |
Tue 4/10/18 |
Wed 4/11/18 |
|
Defining high level requirements |
0.5 days |
Wed 4/11/18 |
Wed 4/11/18 |
|
Forming project team |
1 day |
Thu 4/12/18 |
Thu 4/12/18 |
|
Milestone 1: Completion of project initiation phase |
0 days |
Thu 4/12/18 |
Thu 4/12/18 |
|
Planning phase |
6 days |
Fri 4/13/18 |
Fri 4/20/18 |
|
Developing project plan |
1 day |
Fri 4/13/18 |
Fri 4/13/18 |
|
Creating schedule of the project |
1 day |
Mon 4/16/18 |
Mon 4/16/18 |
|
Creating detailed budget for the project |
2 days |
Tue 4/17/18 |
Wed 4/18/18 |
|
Obtaining sign off on plan |
0.5 days |
Thu 4/19/18 |
Thu 4/19/18 |
|
Getting approval for the project |
0.5 days |
Thu 4/19/18 |
Thu 4/19/18 |
|
Signals approval by steering committee |
1 day |
Fri 4/20/18 |
Fri 4/20/18 |
|
Milestone 2: Completion of planning phase |
0 days |
Fri 4/20/18 |
Fri 4/20/18 |
|
Design/build phase |
36 days |
Mon 4/23/18 |
Mon 6/11/18 |
|
Detailed requirement gathering |
1 day |
Mon 4/23/18 |
Mon 4/23/18 |
|
Security requirements |
1 day |
Tue 4/24/18 |
Tue 4/24/18 |
|
Infrastructure planning |
1.5 days |
Wed 4/25/18 |
Thu 4/26/18 |
|
System operation strategy |
1.5 days |
Thu 4/26/18 |
Fri 4/27/18 |
|
Training preparation |
2 days |
Mon 4/30/18 |
Tue 5/1/18 |
|
Configuration and development |
2 days |
Wed 5/2/18 |
Thu 5/3/18 |
|
Unit/Process business acceptance testing |
3 days |
Fri 5/4/18 |
Tue 5/8/18 |
|
Infrastructure implementation |
5 days |
Wed 5/9/18 |
Tue 5/15/18 |
|
Implement AWS Cloud Infrastructure |
5 days |
Wed 5/16/18 |
Tue 5/22/18 |
|
Develop SAP on the System |
4 days |
Wed 5/23/18 |
Mon 5/28/18 |
|
Test the SAP on the AWS Cloud Infrastructure |
3 days |
Tue 5/29/18 |
Thu 5/31/18 |
|
Find Bugs and Glitches |
2 days |
Fri 6/1/18 |
Mon 6/4/18 |
|
Troubleshoot Issues |
2 days |
Tue 6/5/18 |
Wed 6/6/18 |
|
Make Some Modifications in System Function |
3 days |
Thu 6/7/18 |
Mon 6/11/18 |
|
Milestone 3: Completion of design/Build phase |
0 days |
Mon 6/11/18 |
Mon 6/11/18 |
|
Go live phase |
10 days |
Tue 6/12/18 |
Mon 6/25/18 |
|
End user training |
3 days |
Tue 6/12/18 |
Thu 6/14/18 |
|
Business simulation |
2 days |
Fri 6/15/18 |
Mon 6/18/18 |
|
End user practice in the system |
1 day |
Tue 6/19/18 |
Tue 6/19/18 |
|
Infrastructure finalization |
1 day |
Wed 6/20/18 |
Wed 6/20/18 |
|
Data migration to production |
2 days |
Thu 6/21/18 |
Fri 6/22/18 |
|
Pre-go live operations |
1 day |
Mon 6/25/18 |
Mon 6/25/18 |
|
Milestone 4: Completion of go live phase |
0 days |
Mon 6/25/18 |
Mon 6/25/18 |
|
Closure phase |
4 days |
Tue 6/26/18 |
Fri 6/29/18 |
|
Post-project review |
1 day |
Tue 6/26/18 |
Tue 6/26/18 |
|
Stakeholder sign off |
1 day |
Wed 6/27/18 |
Wed 6/27/18 |
|
Documentation |
2 days |
Thu 6/28/18 |
Fri 6/29/18 |
|
Milestone 5: Completion of project closure phase |
0 days |
Fri 6/29/18 |
Fri 6/29/18 |
The figure that is provided below is the Gantt chart, which is one of the graphical tool that helps in reflecting activities as well as tasks that are needed to be performed against time. In this project, the Gantt chart reflects the activities that are needed to be completed in order to execute the project of SAP within organization “Dai-Ichi Corporation” in 12 weeks.
The figure that is provided above helps in highlighting the critical path of the project which is considered as the longest sequence of activities that are needed to be completed on time to complete the entire project on due date. The project activities that are present on the critical path cannot be initiated until its predecessor is complete. For example, Requirement gathering for the project cannot be started until project is approved by the steering committee.
|
Communication Type |
Objective |
Medium |
Frequency |
Audience |
Owner |
|
Project kick off meeting |
Project kick off meeting is mainly arranged in order to introduce the project objectives and for discussing about goals and objectives of the project. |
Face to face |
Once |
Project sponsor Project team |
Project manager |
|
Project team meeting |
Project team meeting is arranged in order to know about the difficulties that are faced by the project stakeholders. |
Face to face Conference |
As required |
Project team |
Project manager |
|
Monthly status meeting |
Monthly status meeting is mainly arranged in order to track the status of the project. |
Face to face Presentation Conference |
Monthly |
Team leaders |
Project manager |
|
Risk |
Description |
Probability |
Consequence |
Mitigation |
|
Schedule slippage |
Due to slippage of project schedule, the project manager faces difficulty in completing the entire project on time and budget. |
High |
High |
It is very much necessary to track the budget and schedule of the project with the help of earned value analysis. |
|
Budget shortfall |
If the resources of the project are misused then the project manager can face budget shortfall. |
High |
High |
It is very much necessary to utilize the resources of the project effectively in order to reduce issues and challenges related with project budget. |
|
Security issues |
If proper security measures are not utilized then important data and information related with business can be leaked or can be misused. |
Medium |
High |
It is necessary to have proper authentication in order to reduce security related issues and challenges |
Chih, Y.Y. and Zwikael, O., 2015. Project benefit management: A conceptual framework of target benefit formulation. International Journal of Project Management, 33(2), pp.352-362.
Conforto, E.C., Salum, F., Amaral, D.C., da Silva, S.L. and de Almeida, L.F.M., 2014. Can agile project management be adopted by industries other than software development?. Project Management Journal, 45(3), pp.21-34.
De Carvalho, M.M., Patah, L.A. and de Souza Bido, D., 2015. Project management and its effects on project success: Cross-country and cross-industry comparisons. International Journal of Project Management, 33(7), pp.1509-1522.
Hornstein, H.A., 2015. The integration of project management and organizational change management is now a necessity. International Journal of Project Management, 33(2), pp.291-298.
Joslin, R. and Müller, R., 2015. Relationships between a project management methodology and project success in different project governance contexts. International Journal of Project Management, 33(6), pp.1377-1392.
Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A.M.E. and Villanueva, P., 2014. Project risk management methodology for small firms. International journal of project management, 32(2), pp.327-340.
Mir, F.A. and Pinnington, A.H., 2014. Exploring the value of project management: linking project management performance and project success. International journal of project management, 32(2), pp.202-217.
Riol, H. and Thuillier, D., 2015. Project management for academic research projects: balancing structure and flexibility. International Journal of Project Organisation and Management, 7(3), pp.251-269.
Svejvig, P. and Andersen, P., 2015. Rethinking project management: A structured literature review with a critical look at the brave new world. International Journal of Project Management, 33(2), pp.278-290.
Too, E.G. and Weaver, P., 2014. The management of project management: A conceptual framework for project governance. International Journal of Project Management, 32(8), pp.1382-1394.
The network diagram that is provided above helps in reflecting the activities that are interrelated with each other from project initiation to closure phase. The interrelation that are provided above with project activities helps in calculating the total time for the project. In addition to this, it is identified that with the help of the interdependencies that is highlighted within the network diagram one can complete the project as per the sequence.