Comprehensive summary
Woolworths was the targeted company who is facing lots of trouble in the modern environment while trying to make a higher place among the competitors. The proposed solution was to establish an automated information system that can allow the organization to deliver operational activities in an efficient and effective way. The proposed system will allow the employees and the consumers to avail better and efficient ways for operational deliveries and better services respectively. This report will be analysing the figures and constraints represented in the previous part in manner to analyse its feasibility and efficiency and how it could be managed to deliver the project output in much effective and efficient way without altering the quality of the project. The following report includes PERT analysis, early, and late, start and finish calculations in manner to highlight the critical and non-critical activities. An earned value analysis has also been proposed in this report in manner to highlight the expected and on-going project constraints and how these could be managed for the delivery of the project in an efficient and effective manner.
Project Early start, Early Finish, Late Start, and Late Finish
WBS |
Task Name |
Duration |
Early Finish |
Early Finish |
Late Start |
Late Finish |
1 |
Development of an Automated Information system for Woolworths Limited |
126 days |
Mon 29-10-18 |
Mon 29-10-18 |
Mon 07-05-18 |
Mon 29-10-18 |
1.1 |
Project planning |
30 days |
Fri 15-06-18 |
Fri 15-06-18 |
Mon 07-05-18 |
Mon 18-06-18 |
1.1.1 |
Budget planning |
10 days |
Fri 18-05-18 |
Fri 18-05-18 |
Mon 07-05-18 |
Fri 18-05-18 |
1.1.2 |
Project time scheduling |
10 days |
Fri 01-06-18 |
Fri 01-06-18 |
Wed 23-05-18 |
Tue 05-06-18 |
1.1.3 |
Risk management planning |
12 days |
Tue 05-06-18 |
Tue 05-06-18 |
Mon 21-05-18 |
Tue 05-06-18 |
1.1.4 |
Communication management planning |
8 days |
Fri 15-06-18 |
Fri 15-06-18 |
Wed 06-06-18 |
Fri 15-06-18 |
1.1.5 |
Milestone 2: Completion of project planning phase |
0 days |
Fri 15-06-18 |
Fri 15-06-18 |
Mon 18-06-18 |
Mon 18-06-18 |
1.2 |
Project execution |
61 days |
Mon 10-09-18 |
Mon 10-09-18 |
Mon 18-06-18 |
Tue 11-09-18 |
1.2.1 |
Prototype design of the Information system |
46 days |
Mon 20-08-18 |
Mon 20-08-18 |
Mon 18-06-18 |
Mon 20-08-18 |
1.2.1.1 |
Features incorporation to the Information System |
26 days |
Mon 23-07-18 |
Mon 23-07-18 |
Mon 18-06-18 |
Mon 23-07-18 |
1.2.1.1.1 |
coding |
10 days |
Fri 29-06-18 |
Fri 29-06-18 |
Mon 18-06-18 |
Fri 29-06-18 |
1.2.1.1.2 |
Modelling |
16 days |
Mon 23-07-18 |
Mon 23-07-18 |
Mon 02-07-18 |
Mon 23-07-18 |
1.2.1.2 |
Connection to database management system for storing data |
20 days |
Mon 20-08-18 |
Mon 20-08-18 |
Tue 24-07-18 |
Mon 20-08-18 |
1.2.2 |
Incorporating Graphical User Interface |
15 days |
Mon 10-09-18 |
Mon 10-09-18 |
Tue 21-08-18 |
Mon 10-09-18 |
1.2.3 |
Milestone 3: Completion of project execution phase |
0 days |
Mon 10-09-18 |
Mon 10-09-18 |
Tue 11-09-18 |
Tue 11-09-18 |
1.3 |
Project control and monitoring phase |
22 days |
Wed 10-10-18 |
Wed 10-10-18 |
Tue 11-09-18 |
Thu 11-10-18 |
1.3.1 |
Unit testing of the Information System |
10 days |
Mon 24-09-18 |
Mon 24-09-18 |
Tue 11-09-18 |
Mon 24-09-18 |
1.3.2 |
Integrated testing of the Information System |
10 days |
Mon 08-10-18 |
Mon 08-10-18 |
Thu 27-09-18 |
Wed 10-10-18 |
1.3.3 |
Acceptance testing of the Information System |
12 days |
Wed 10-10-18 |
Wed 10-10-18 |
Tue 25-09-18 |
Wed 10-10-18 |
1.3.4 |
Milestone 4: Completion of project control and monitoring phase |
0 days |
Wed 10-10-18 |
Wed 10-10-18 |
Thu 11-10-18 |
Thu 11-10-18 |
1.4 |
Project closure |
13 days |
Mon 29-10-18 |
Mon 29-10-18 |
Thu 11-10-18 |
Mon 29-10-18 |
1.4.1 |
Project stakeholder’s signoff |
2 days |
Fri 12-10-18 |
Fri 12-10-18 |
Thu 11-10-18 |
Fri 12-10-18 |
1.4.2 |
Final project document submission |
6 days |
Mon 22-10-18 |
Mon 22-10-18 |
Mon 15-10-18 |
Mon 22-10-18 |
1.4.3 |
Post project maintenance planning |
5 days |
Mon 29-10-18 |
Mon 29-10-18 |
Tue 23-10-18 |
Mon 29-10-18 |
1.4.4 |
Milestone 5: Completion of project closure phase |
0 days |
Mon 29-10-18 |
Mon 29-10-18 |
Mon 29-10-18 |
Mon 29-10-18 |
Figure 1: Pert Analysis
(Source: Created by Author)
The above present PERT analysis demonstrates the critical path of the project emphasizing on the slowest path that can be taken for the completion of the project without altering the output and performance of the project. The critical activities must not be altered in manner to meet the project constraints however, the critical activities timeline can be changed with respect to the critical activities.
Earned Value Analysis Report |
Please Fill you name |
27th August |
[42] |
Month 6 |
Planned Value (PV) or Budgeted Cost of Work Scheduled (BCWS) |
TBC |
10256 |
15520 |
7328 |
2944 |
36048 |
Cumulative Planned Value (PV) |
Actual Cost and Earned Value |
Cumulative Actual Cost (AC) |
Cumulative Earned Value (EV) |
Project Performance Metrics |
Cost Variance (CV = EV – AC) |
Schedule Variance (SV = EV – PV) |
Cost Performance Index (CPI = EV/AC) |
Schedule Performance Index (SPI = EV/PV) |
Estimated Cost at Completion (EAC) |
The following graph represents the earn value analysis in single graph:
Figure 2: Cost Benefit Analysis
(Source: Created by Author using excel)
The above calculated values provide cost variance and schedule variance negative that states that the project is behind the schedule and under the budget. One of the constraint is beneficial for the project however, the schedule variance is lagging as per the planning. The work % of the stakeholders can be increased in manner to accomplish the project activities much faster than the present scenario. This will be helpful in meeting the future constraints for the project assuring that the delivery of the project is within the estimated time and cost. It is necessary to manage the timeline even if it brings the actual cost reaches to the estimated value. The schedule variance should be a positive figure or in other words the project should be ahead of the schedule along with the under budget of the project only then, the project planning can be considered as feasible and ready to deliver. Thus, the health of the project can be categorized in moderate level that needs certain modifications in manner to implement the necessary changes those can be further executed for meeting the objectives and goals of the project.
Analysing project schedule
Contemporary project management practice include the cutting-edge and time-tested project management techniques those can be of great value for the project manager in delivering the efficient and effective project. Agile and PMBoK practices have been very trending in the modern project delivering practices. Traditional project management practices emphasizes on the upfront planning and wasting lots of time and thus, it could be a lagging factor for the modern project management practices. However, the requirement of the modern time keeps changing with the time and thus, it could be not much effective to deliver modern projects. The contemporary project management practice emphasizes on the application of modern software and application that can be used for the planning and better estimations based on the calculative and quantitative values. The project constraints can be measured and planned in much efficient and effective way through the application of the MS project for the delivery of the project related activities. It allows the project manager to explain every aspect of the project in far better and effective way through highlighting every project constraints in association with many automated calculations for the necessary future strategies those could be adopted for the delivery of the project.
Conclusion
Based on the above report it can be concluded that the above report analyses the proposed project plan in part A. The MS Project 2016 project and Excel 2016 has been used for analysing the figures proposed in the previous section and make sure that the project meets the necessary production and output. The above report presents the PERT analysis on the same data as it was proposed in part A with the proposed estimated early start, late start, early finish, and last finish calculations. The proposed PERT chart can be followed for delivering the project within least estimated timeline moreover, the critical activities’ constraints must not be altered as such alteration will alternatively reflect on the entire project. On the other hand, non-critical activities can be altered to some extent even if the project is on schedule as it will not influence the entire project delivery.
Binder, J. (2016). Global project management: communication, collaboration and management across borders. Routledge.
Boud, D., Cohen, R., & Sampson, J. (Eds.). (2014). Peer learning in higher education: Learning from and with each other. Routledge.
Fleming, Q. W., & Koppelman, J. M. (2016, December). Earned value project management. Project Management Institute.
Gold, B., & Vassell, C. (2015, November). Using risk management to balance agile methods: A study of the Scrum process. In Knowledge-Based Engineering and Innovation (KBEI), 2015 2nd International Conference on (pp. 49-54). IEEE.
Harrison, F., & Lock, D. (2017). Advanced project management: a structured approach. Routledge.
Heagney, J. (2016). Fundamentals of project management. AMACOM Div American Mgmt Assn.
Hornstein, H. A. (2015). The integration of project management and organizational change management is now a necessity. International Journal of Project Management, 33(2), 291-298.
Joslin, R., & 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), 1377-1392.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Machado, T. C. S., Pinheiro, P. R., & Tamanini, I. (2015). Project management aided by verbal decision analysis approaches: a case study for the selection of the best SCRUM practices. International Transactions in Operational Research, 22(2), 287-312.
Permana, P. A. G. (2015). Scrum method implementation in a software development project management. International Journal of Advanced Computer Science and Applications, 6(9), 198-204.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
Spundak, M. (2014). Mixed agile/traditional project management methodology–reality or illusion?. Procedia-Social and Behavioral Sciences, 119, 939-948.
Tomanek, M., & Juricek, J. (2015). Project risk management model based on PRINCE2 and SCRUM frameworks. arXiv preprint arXiv:1502.03595.
Turner, R. (2016). Gower handbook of project management. Routledge.
Verzuh, E. (2015). The fast forward MBA in project management. John Wiley