Project Background
Discuss about the Artificial Neural Network Model Based on Critical.
The paper mainly focuses on the technical upgradation of the archives website Destination in Australia. It is identified that the National archives of Australia is mainly responsible for preserving as well as storing Commonwealth records including different types of archival resources.
It is identified that technical upgradation of the website is mainly required for ensuring proper value of money as well as appropriate functionality of the website. It is identified that the website will generally help in enabling the National archives for gathering various types of user contributed photographic collection which is mainly featured on the site.
- To upgrade the website technically
- To ensure proper value of money as well as appropriate functionality of the website
- To enable the National archives for gathering various types of user contributed photographic collection
- Technical upgradation of the website
- Wireframe and visual design
- CMS implementation
- Front-end and back-end development
Out scope: Out scope includes
- Exclusion of trainings needs
- Exclusion of project supplies details
- The entire resources that are needed will be quite easily available
- The technical upgradation of the website will be completed within 118 days
- Technical upgradation will be completed within 118 days
- The upgradation must be finished within the budget $267,520
It is identified that agile project methodology is mainly utilized in order to upgrade the website successfully. It is identified that the steps or stages that are used for implementing the website are listed below:
WBS |
Task Name |
0 |
Technical upgradation of the website |
1 |
Initiation phase |
1.1 |
Business case development |
1.2 |
Cost benefit analysis |
1.3 |
Project charter establishment |
1.4 |
Team members appointment |
1.5 |
Milestone 1: Completion of initiation phase |
2 |
Planning phase |
2.1 |
Project plan development |
2.2 |
Resource plan development |
2.3 |
Financial plan development |
2.4 |
Development of quality plan |
2.5 |
Development of risk plan |
2.6 |
Development of acceptance plan |
2.7 |
Development of communication plan |
2.8 |
Milestone 2: Completion of planning phase |
3 |
Design Phase |
3.1 |
Wireframe Design |
3.2 |
Visual design |
3.3 |
Prototype design |
3.4 |
Milestone 3: Completion of design phase |
4 |
Development phase |
4.1 |
CMS implementation |
4.2 |
Front-end development |
4.3 |
Back-end development |
4.4 |
Database development |
4.5 |
Milestone 4: Completion of development phase |
5 |
Testing phase |
5.1 |
Black box testing |
5.2 |
User acceptance testing |
5.3 |
Compatibility testing |
5.4 |
Milestone 5: Completion of testing phase |
6 |
Closure phase |
6.1 |
Hosting of the website |
6.2 |
Post-project review |
6.3 |
Stakeholder analysis |
6.4 |
Documentation |
6.5 |
Milestone 6: Completion of closure phase |
Name |
Title |
Authority level |
Project manager |
Tell |
|
Project planner |
Tell |
|
Supervisor |
Advice, Inquire |
|
Technical engineer |
Tell, Advice |
|
Developer |
Consult |
|
Financial manager |
Delegate |
|
System analyst |
Consult |
|
Risk analyst |
Inquire |
Risk No |
Category |
Risk description |
Likelihood |
Impact |
1 |
Technical risk |
If the design for the website is not created properly then it will quite difficult to work within the project. |
High |
Very High |
2 |
Financial risk |
Inappropriate budget estimation can lead to shortage of budget |
Very high |
High |
3 |
Resourcing |
Absence of proper resources can cause obstruction in project progress. |
High |
Medium |
Milestones |
Completion date |
Dependencies |
Milestone 1: Completion of initiation phase |
Fri 15-06-18 |
5 |
Milestone 2: Completion of planning phase |
Fri 13-07-18 |
13 |
Milestone 3: Completion of design phase |
Fri 03-08-18 |
19 |
Milestone 4: Completion of development phase |
Mon 24-09-18 |
25 |
Milestone 5: Completion of testing phase |
Wed 24-10-18 |
30 |
Milestone 6: Completion of closure phase |
Tue 06-11-18 |
36 |
Task Name |
Duration |
Cost |
Technical upgradation of the website |
118 days |
$267,520.00 |
Initiation phase |
16 days |
$21,680.00 |
Business case development |
4 days |
$8,000.00 |
Cost benefit analysis |
3 days |
$2,880.00 |
Project charter establishment |
4 days |
$4,800.00 |
Team members appointment |
5 days |
$6,000.00 |
Milestone 1: Completion of initiation phase |
0 days |
$0.00 |
Planning phase |
20 days |
$68,320.00 |
Project plan development |
5 days |
$17,600.00 |
Resource plan development |
4 days |
$8,000.00 |
Financial plan development |
5 days |
$3,600.00 |
Development of quality plan |
6 days |
$11,520.00 |
Development of risk plan |
4 days |
$8,640.00 |
Development of acceptance plan |
5 days |
$13,200.00 |
Development of communication plan |
6 days |
$5,760.00 |
Milestone 2: Completion of planning phase |
0 days |
$0.00 |
Design Phase |
15 days |
$39,680.00 |
Wireframe Design |
5 days |
$8,000.00 |
Visual design |
4 days |
$13,440.00 |
Prototype design |
6 days |
$18,240.00 |
Milestone 3: Completion of design phase |
0 days |
$0.00 |
Development phase |
36 days |
$68,240.00 |
CMS implementation |
7 days |
$12,320.00 |
Front-end development |
8 days |
$23,040.00 |
Back-end development |
9 days |
$7,920.00 |
Database development |
12 days |
$24,960.00 |
Milestone 4: Completion of development phase |
0 days |
$0.00 |
Testing phase |
22 days |
$48,800.00 |
Black box testing |
5 days |
$10,000.00 |
User acceptance testing |
8 days |
$29,440.00 |
Compatibility testing |
9 days |
$9,360.00 |
Milestone 5: Completion of testing phase |
0 days |
$0.00 |
Closure phase |
9 days |
$20,800.00 |
Hosting of the website |
3 days |
$8,160.00 |
Post-project review |
2 days |
$4,000.00 |
Stakeholder analysis |
2 days |
$3,360.00 |
Documentation |
2 days |
$5,280.00 |
Milestone 6: Completion of closure phase |
0 days |
$0.00 |
The tools and techniques that are generally required for developing the management plan are as follows:
- Gantt chart
- Critical path method
- Pert Chart
The project can be executed successfully for accomplishing the objectives by using the plan that is provided below along with the project dependencies.
Task Name |
Duration |
Start |
Finish |
Dependencies |
Technical upgradation of the website |
118 days |
Fri 25-05-18 |
Tue 06-11-18 |
|
Initiation phase |
16 days |
Fri 25-05-18 |
Fri 15-06-18 |
|
Business case development |
4 days |
Fri 25-05-18 |
Wed 30-05-18 |
|
Cost benefit analysis |
3 days |
Thu 31-05-18 |
Mon 04-06-18 |
2 |
Project charter establishment |
4 days |
Tue 05-06-18 |
Fri 08-06-18 |
3 |
Team members appointment |
5 days |
Mon 11-06-18 |
Fri 15-06-18 |
4 |
Milestone 1: Completion of initiation phase |
0 days |
Fri 15-06-18 |
Fri 15-06-18 |
5 |
Planning phase |
20 days |
Mon 18-06-18 |
Fri 13-07-18 |
|
Project plan development |
5 days |
Mon 18-06-18 |
Fri 22-06-18 |
5 |
Resource plan development |
4 days |
Mon 25-06-18 |
Thu 28-06-18 |
6 |
Financial plan development |
5 days |
Mon 25-06-18 |
Fri 29-06-18 |
8 |
Development of quality plan |
6 days |
Fri 29-06-18 |
Fri 06-07-18 |
9 |
Development of risk plan |
4 days |
Mon 02-07-18 |
Thu 05-07-18 |
10 |
Development of acceptance plan |
5 days |
Mon 09-07-18 |
Fri 13-07-18 |
11 |
Development of communication plan |
6 days |
Fri 06-07-18 |
Fri 13-07-18 |
12 |
Milestone 2: Completion of planning phase |
0 days |
Fri 13-07-18 |
Fri 13-07-18 |
13 |
Design Phase |
15 days |
Mon 16-07-18 |
Fri 03-08-18 |
|
Wireframe Design |
5 days |
Mon 16-07-18 |
Fri 20-07-18 |
14 |
Visual design |
4 days |
Mon 23-07-18 |
Thu 26-07-18 |
17 |
Prototype design |
6 days |
Fri 27-07-18 |
Fri 03-08-18 |
18 |
Milestone 3: Completion of design phase |
0 days |
Fri 03-08-18 |
Fri 03-08-18 |
19 |
Development phase |
36 days |
Mon 06-08-18 |
Mon 24-09-18 |
|
CMS implementation |
7 days |
Mon 06-08-18 |
Tue 14-08-18 |
19 |
Front-end development |
8 days |
Wed 15-08-18 |
Fri 24-08-18 |
22 |
Back-end development |
9 days |
Mon 27-08-18 |
Thu 06-09-18 |
23 |
Database development |
12 days |
Fri 07-09-18 |
Mon 24-09-18 |
24 |
Milestone 4: Completion of development phase |
0 days |
Mon 24-09-18 |
Mon 24-09-18 |
25 |
Testing phase |
22 days |
Tue 25-09-18 |
Wed 24-10-18 |
|
Black box testing |
5 days |
Tue 25-09-18 |
Mon 01-10-18 |
26 |
User acceptance testing |
8 days |
Tue 02-10-18 |
Thu 11-10-18 |
28 |
Compatibility testing |
9 days |
Fri 12-10-18 |
Wed 24-10-18 |
29 |
Milestone 5: Completion of testing phase |
0 days |
Wed 24-10-18 |
Wed 24-10-18 |
30 |
Closure phase |
9 days |
Thu 25-10-18 |
Tue 06-11-18 |
|
Hosting of the website |
3 days |
Thu 25-10-18 |
Mon 29-10-18 |
30 |
Post-project review |
2 days |
Tue 30-10-18 |
Wed 31-10-18 |
33 |
Stakeholder analysis |
2 days |
Thu 01-11-18 |
Fri 02-11-18 |
34 |
Documentation |
2 days |
Mon 05-11-18 |
Tue 06-11-18 |
35 |
Milestone 6: Completion of closure phase |
0 days |
Tue 06-11-18 |
Tue 06-11-18 |
36 |
The organization’s environmental factors that are generally required for planning as well as delivering the project are listed below:
Economic landscapes: The economic landscape must be considered properly while planning as well as delivering the project.
Consumer needs: It is quite necessary to reflect on the needs and demands of the customers while planning the project.
Regulatory environment: The regulatory environment must be followed properly while delivering and planning the project.
The organizational processes that are required for developing the project management plan are listed below:
Standard guidelines: Proper standard guidelines would be helpful in developing the plan for project management.
Change control processes: It is necessary to follow proper change control processes for the project while implementing the plan
Performance measurement criteria: The performance measurement criteria must be properly followed while implementing the project management plan.
The integrity of the project baseline is mainly maintained by tracking the schedule of the project on a regular basis for ensuring that the entire project is on the project and it will be completed on time.
It is identified that the project manager is mainly responsible of maintaining the integrity of the project baseline.
The approval for the project management plan will be achieved from the higher authorities of the organization when they will make sure that the website upgradation will be advantageous for them it will be helpful in bringing some return value from the investment.
Project Purpose and Justification
The triple constraint can be applied by utilizing steps that are as follows:
Time: The required time for the completion of the project will be around 11 days.
Cost: The entire project must be completed within the budget of around $267,520
Quality: Proper quality of the project must be maintained within the entire lifecycle of the project.
It is analyzed that the entire activities of the project are successfully completed for upgrading the website while determining performance data in the closure phase of the project.
It is identified that if the project gets delayed then the entire cost that is associated with the project gets increased and as result the project will face financial crisis. In order to resolve this issue, proper management budget is done so that the budget can be properly used for completing the project.
The tools ad techniques that are used for analyzing status include:
- Pert chart
- Risk management plan
- Financial plan
- Resource analysis plan
2) Need for updating and managing project work
Project status log must be utilized in order to update as well as manage the project work effectively.
It is identified that they generally changes due to the progress within the project.
Activities |
Status |
Handover |
Completed |
Financial, legal and contractual documentation |
Completed |
Report finalization |
Completed |
Organization knowledge management |
Completed |
Badewi, A., 2016. The impact of project management (PM) and benefits management (BM) practices on project success: Towards developing a project benefits governance framework. International Journal of Project Management, 34(4), pp.761-778.
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.
Costantino, F., Di Gravio, G. and Nonino, F., 2015. Project selection in project portfolio management: An artificial neural network model based on critical success factors. International Journal of Project Management, 33(8), pp.1744-1754.
Fernandes, G., Ward, S. and Araújo, M., 2015. Improving and embedding project management practice in organisations—A qualitative study. International Journal of Project Management, 33(5), pp.1052-1067.
Heldman, K., 2018. PMP: project management professional exam study guide. John Wiley & Sons.
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.
Ika, L.A., 2015. Opening the black box of project management: Does World Bank project supervision influence project impact?. International Journal of Project Management, 33(5), pp.1111-1123.
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.
Marcelino-Sádaba, S., González-Jaen, L.F. and Pérez-Ezcurdia, A., 2015. Using project management as a way to sustainability. From a comprehensive review to a framework definition. Journal of cleaner production, 99, pp.1-16.
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.