Project Management Overview
The report illustrates the importance of adapting Business Intelligence (Transferring Data with Intelligence) tools for improving the existing logistic business operation of Evergreen Cargo Service private Limited. The supply chain management system of Evergreen Cargo Service is too weak and thus the relationship between the consumer and the service provider is not up to the mark.
In order to improve the SCM system of Evergreen Cargo Service a business intelligence architecture which is introducing SAP BI tools and using different technologies data warehousing, dashboard, Ad Hoc reporting and discovery of data technologies are used by the project development team to improve the existing business operation of Evergreen Cargo Service (Kerzner 2013). The overview of the project including the scope of the project, its objectives and constraints, statement of work, roles and responsibility of the project team members and a project schedule is developed in this report. Apart from this, the current issues and problems of the system are also illustrated in this report. In order to manage the issues accurate stakeholder analysis and management process are proposed in this report.
1. Project Management Overview
1.1 Scope of Project
- The project scope elaborates the operations those are served by the newly proposed Business Intelligence (BI).
- The project elaborates the role of Business Intelligence and the vision of the project that is transferring data with intelligence.
- Proper Business Intelligence tool helps to utilize the gathered data in terms of knowledge based information.
- Helps to develop a high level architecture, with accurate planning and implementation of the business intelligence
- A project schedule will be developed that helps to divide the work responsibility
- The data confidentiality will be maintained and the data efficiency will also increase.
1.2 Objectives & Constraints
1.2.1 Objective
- To analyze the issues associated to the supply Chan Management system of Evergreen Cargo Service.
- To implement SAP Business Intelligence tools along with the existing business operation of Evergreen Cargo Service
- To get competitive advantages from the logistic marketplace
- To develop the visibility style off the management authority
1.2.2 Constraints
For this particular project triple project management constraints are considered that include proper time management, budget management and scope management as well. It means that within the allotted time phase, by considering appropriate budget and the scope developed by the project management team the project should be completed (Too and Weaver 2014). If the project management team fails to deliver the preliminary settled expected outcome then the entire project will be a failure.
1.3 Statement of Work
For this particular project a routine documentation is required to be prepared by the project management team after considering the accurate time schedule, roles and responsibility and aim as well (Verzuh 2015). Certain specified activities and developed by the project development team in order to distribute the work burden the activities are divided the project manager and the two other project participants. As this professional project does not have any professional finance manager, operational manager and IS manager thus based on work accuracy the activities are divided among three of the project team members.
1.4 Project Team Members and Responsibilities (RACI matrix)
WBS |
Name of the tasks |
Project manager (Ms. Indra Seher) |
1st Project team members Sujeet Kumar Shrestha |
1.1.1 |
Team management |
R |
|
1.1.2 |
Kick off meeting arrangement |
R |
|
1.1.3 |
Selection of relevant case study |
R/A |
|
1.1.4 |
Analysis of the issues with supply chain management system |
C |
C |
1.1.5 |
Defining project scope |
C |
C |
1.1.6 |
Defining project scope and constraints |
C |
C |
1.1.7 |
Responsibility division |
C |
C |
1.1.8 |
Task estimation |
C |
C |
1.1.9 |
Scheduling |
C |
C |
1.2 |
Project requirement gathering |
||
1.2.1 |
Research on business process |
R/A |
R/A |
1.2.2 |
Research on competitors |
C |
C |
1.2.3 |
Research on big data tools |
C |
C |
1.2.5 |
Research on the big data system |
C |
C |
1.2.6 |
Research on the distribution models |
R/A |
R/A |
1.3.1 |
Business process analysis |
C |
C |
1.3.2 |
Stakeholder analysis |
C |
R/A |
1.3.3 |
Risk analysis |
C |
C |
1.4.3 |
Reliability requirement |
R/A |
R/A |
1.4.4 |
Usability requirement |
R |
R |
1.4.5 |
Performance requirement |
R |
R |
1.5 |
System designing |
||
1.5.1 |
Model designing |
R |
R |
1.5.2 |
Selection of Big data tool |
||
1.5.3 |
Defining risk management |
R |
R/A |
1.5.4 |
Define business strategy |
R |
R/A |
M.1 |
Planning for project proposal |
R |
R |
M.2 |
Progress report 1 |
R |
R |
M.3 |
Progress report 2 |
R |
R |
M.4 |
Draft presentation |
R |
R |
M.5 |
Presentation documentation |
R |
R |
M.6 |
Self assessment |
R |
R |
M.7 |
Portfolio presentation |
R |
R |
M.8 |
Project reporting |
R/A |
R/A |
1.5 Project Schedule
Task Mode |
Task Name |
Duration |
Start |
Finish |
Auto Scheduled |
Schedule development for Evergreen Cargo Service |
78 days |
Thu 2/16/17 |
Mon 6/5/17 |
Manually Scheduled |
Project Planning |
18 days |
Thu 2/16/17 |
Mon 3/13/17 |
Auto Scheduled |
Team management |
1 day |
Thu 2/16/17 |
Thu 2/16/17 |
Auto Scheduled |
Kick off meeting arrangement |
6 days |
Fri 2/17/17 |
Fri 2/24/17 |
Auto Scheduled |
Selection of relevant case study |
1 day |
Mon 2/27/17 |
Mon 2/27/17 |
Auto Scheduled |
Analysis of the issues with supply chain management system |
2 days |
Tue 2/28/17 |
Wed 3/1/17 |
Auto Scheduled |
Defining project scope |
2 days |
Thu 3/2/17 |
Fri 3/3/17 |
Auto Scheduled |
Defining project scope and constraints |
1 day |
Mon 3/6/17 |
Mon 3/6/17 |
Auto Scheduled |
Responsibility division |
1 day |
Tue 3/7/17 |
Tue 3/7/17 |
Auto Scheduled |
Task estimation |
3 days |
Wed 3/8/17 |
Fri 3/10/17 |
Auto Scheduled |
Scheduling |
1 day |
Mon 3/13/17 |
Mon 3/13/17 |
Auto Scheduled |
Project requirement gathering |
11 days |
Tue 3/14/17 |
Tue 3/28/17 |
Auto Scheduled |
Research on business process |
2 days |
Tue 3/14/17 |
Wed 3/15/17 |
Auto Scheduled |
Research on competitors |
1 day |
Thu 3/16/17 |
Thu 3/16/17 |
Auto Scheduled |
Research on big data tools |
2 days |
Fri 3/17/17 |
Mon 3/20/17 |
Auto Scheduled |
Research on the expected solution |
4 days |
Tue 3/21/17 |
Fri 3/24/17 |
Auto Scheduled |
Research on the big data system |
2 days |
Mon 3/27/17 |
Tue 3/28/17 |
Auto Scheduled |
Research on the distribution models |
2 days |
Fri 3/17/17 |
Mon 3/20/17 |
Auto Scheduled |
Project analysis |
7 days |
Wed 3/29/17 |
Thu 4/6/17 |
Auto Scheduled |
Business process analysis |
3 days |
Wed 3/29/17 |
Fri 3/31/17 |
Auto Scheduled |
Stakeholder analysis |
3 days |
Mon 4/3/17 |
Wed 4/5/17 |
Auto Scheduled |
Risk analysis |
4 days |
Mon 4/3/17 |
Thu 4/6/17 |
Auto Scheduled |
Analysis on the system |
14 days |
Fri 4/7/17 |
Wed 4/26/17 |
Auto Scheduled |
Current analysis on the system |
3 days |
Fri 4/7/17 |
Tue 4/11/17 |
Auto Scheduled |
Defining system requirement |
2 days |
Wed 4/12/17 |
Thu 4/13/17 |
Auto Scheduled |
Function requirement |
1 day |
Fri 4/14/17 |
Fri 4/14/17 |
Auto Scheduled |
On functional requirement |
2 days |
Mon 4/17/17 |
Tue 4/18/17 |
Auto Scheduled |
Reliability requirement |
2 days |
Wed 4/19/17 |
Thu 4/20/17 |
Auto Scheduled |
Usability requirement |
1 day |
Fri 4/21/17 |
Fri 4/21/17 |
Auto Scheduled |
Performance requirement |
3 days |
Mon 4/24/17 |
Wed 4/26/17 |
Auto Scheduled |
System designing |
4 days |
Thu 4/27/17 |
Tue 5/2/17 |
Auto Scheduled |
Model designing |
1 day |
Thu 4/27/17 |
Thu 4/27/17 |
Auto Scheduled |
Selection of Big data tool |
2 days |
Thu 4/27/17 |
Fri 4/28/17 |
Auto Scheduled |
Defining risk management |
2 days |
Mon 5/1/17 |
Tue 5/2/17 |
Auto Scheduled |
Define business strategy |
2 days |
Fri 4/28/17 |
Mon 5/1/17 |
Auto Scheduled |
Milestone |
25 days |
Tue 5/2/17 |
Mon 6/5/17 |
Auto Scheduled |
Planning for project proposal |
4 days |
Tue 5/2/17 |
Fri 5/5/17 |
Auto Scheduled |
Progress report 1 |
4 days |
Mon 5/8/17 |
Thu 5/11/17 |
Auto Scheduled |
Progress report 2 |
2 days |
Mon 5/8/17 |
Tue 5/9/17 |
Auto Scheduled |
Draft presentation |
3 days |
Fri 5/12/17 |
Tue 5/16/17 |
Auto Scheduled |
Presentation documentation |
4 days |
Wed 5/17/17 |
Mon 5/22/17 |
Auto Scheduled |
Self assessment |
3 days |
Tue 5/23/17 |
Thu 5/25/17 |
Auto Scheduled |
Portfolio presentation |
2 days |
Fri 5/26/17 |
Mon 5/29/17 |
Auto Scheduled |
Project reporting |
5 days |
Tue 5/30/17 |
Mon 6/5/17 |
2. Proposed Strategic Alignment
In this project the project manager and the project team participants will analyze the existing issues in Supply Chain management of Evergreen Cargo. Then they will introduce business intelligence tools to the operational activities.
3. Description of Current System
3.1 Issues
Though, it has been expected that after successful completion of the project it will be able to make faster decision over the SCM and the performance of the project dashboard will also improve (Martinsuo 2013). However, the BI failed to utilize the data properly in the business operations. Apart from this, the expected returns are also not generating from the process.
3.2 Problems
Other problem of the project is lack of security. Due to lack of security the data those are stored in the server of Evergreen Cargo Service are not properly secured thus external users of the organization can easily hijack the information from the server. Moreover, the operational dashboard of Evergreen Cargo Service is also cannot be handled easily by non-experienced users.
4. Proposed Stakeholder Analysis and Management
The stakeholders of the project are the consumers, project manager and the two project participants. In order to manage the proposed project properly, the project must serve such outcome those are satisfactory to the consumers (Ahern, Leavy and Byrne 2014). Rather the project participants are needed to consider the content security accurately.
In the field of project management different stakeholder analysis and management tools are widely used by the project manager for the successful completion of the project. The stakeholder management system helps the project manager to understand whether the current situation of the project is beneficial for the logistic company or not. Even in order to identify the key person of the project the stakeholder management system is required to be used. For managing the stakeholders appropriately the steps that are needed to be followed are given below:
Step 1: Identification of the stakeholders
This is the initial phase of the stakeholder analysis. In this period the stakeholders are initially needed to be identified. For this project the stakeholders are:
Name of the stakeholder |
Roles |
Project manager |
Control and monitoring |
Project sponsors |
Sponsor selection |
Finance manager |
Estimate the project budget |
Suppliers |
Delivers both the functional and non functional requirements |
Project customer |
Give feedback for further improvement |
Step 2: Stakeholder’s prioritization
Based on the type of the business all the stakeholders of the project will be positively a well as negatively impacted. In order to keep the security and satisfaction level of the consumers the project manager is required to establish the priority of them individually.
Step 3: Understanding the key stakeholder of this particular project
In this step the stakeholders of the project are needed to be analyzed properly and based on their priority the value should be distributed.
References
Ahern, T., Leavy, B. and Byrne, P.J., 2014. Complex project management as complex problem solving: A distributed knowledge management perspective. International Journal of Project Management, 32(8), pp.1371-1381.
Kerzner, H., 2013. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Lu, Y., Luo, L., Wang, H., Le, Y. and Shi, Q., 2015. Measurement model of project complexity for large-scale projects from task and organization perspective. International Journal of Project Management, 33(3), pp.610-622.
Martinsuo, M., 2013. Project portfolio management in practice and in context. International Journal of Project Management, 31(6), pp.794-803.
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.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.
Snyder, C.S., 2014. A Guide to the Project Management Body of Knowledge: PMBOK (®) Guide. Project Management Institute.
Teller, J. and Kock, A., 2013. An empirical investigation on how portfolio risk management influences project portfolio success. International Journal of Project Management, 31(6), pp.817-829.
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.
Verzuh, E., 2015. The fast forward MBA in project management. John Wiley & Sons.