Work Break Down Structure
The report depicts the importance of implementing website for Social media Research center, for managing large set of information regarding their employees and for the users of the organization. While developing an official website for the organization it is necessary to consider the security of the system. With the help of accessibility only the authenticated users will be able to access data from the data center. In this phase, the project manager will initiate the project plan by scheduling the project budget.
It will help the project manager to understand the actual budget needed for implementing the project in practical world. For the proposed web application the project manager is required to develop a Gantt chart, time phased budget as well. In addition to this, the project manager should also develop a quality management plan including the quality planning, quality assurance and quality control as well. Apart from the quality assurance the project manager should also built a closure checklist and a project evaluation plan as well.
|
WBS |
Task Name |
|
0 |
Time schedule for SMRC |
|
1 |
Project initiation phase |
|
1.1 |
Understanding the project requirement |
|
1.2 |
Project discussion with the project sponsor |
|
1.3 |
Delivering project proposal |
|
1.4 |
Singing the project agreements |
|
1.5 |
Project feasibility study |
|
1.6 |
Project risk assessment |
|
2 |
Project planning |
|
2.1 |
Developing initial project design concept |
|
2.2 |
Collecting client review |
|
2.3 |
Project prototype development |
|
2.4 |
Modelling |
|
2.5 |
Unit testing |
|
2.6 |
Integrated testing |
|
2.7 |
Final design approval |
|
2.8 |
Coding |
|
2.8.1 |
Template development |
|
2.8.2 |
Database development |
|
2.8.3 |
Code validation |
|
2.8.4 |
Browser testing |
|
2.8.5 |
Optimization |
|
3 |
Project execution |
|
3.1 |
Content building |
|
3.2 |
Site content pages |
|
3.3 |
Navigation structure |
|
3.4 |
Risk management plan development |
|
4 |
Project closure |
|
4.1 |
Secured relationship development |
|
4.2 |
Stakeholder signoff |
|
Task Name |
Duration |
Start |
Finish |
Predecessors |
|
Time schedule for Social Media Research Center |
44 days |
Fri 5/19/17 |
Wed 7/19/17 |
|
|
Project initiation phase |
16 days |
Fri 5/19/17 |
Fri 6/9/17 |
|
|
Project milestone preparation |
2 days |
Fri 5/19/17 |
Mon 5/22/17 |
|
|
Feasibility study |
2 days |
Tue 5/23/17 |
Wed 5/24/17 |
2 |
|
Risk assessment |
2 days |
Thu 5/25/17 |
Fri 5/26/17 |
3 |
|
Selection of project sponsor |
3 days |
Thu 5/25/17 |
Mon 5/29/17 |
2,3 |
|
Requirement inclusion for the expected project outcome |
4 days |
Tue 5/30/17 |
Fri 6/2/17 |
5 |
|
Requirement gathering |
3 days |
Mon 6/5/17 |
Wed 6/7/17 |
6 |
|
Requirement analysis |
2 days |
Thu 6/8/17 |
Fri 6/9/17 |
7 |
|
Project planning phase |
14 days |
Mon 6/12/17 |
Thu 6/29/17 |
|
|
Project verification |
5 days |
Mon 6/12/17 |
Fri 6/16/17 |
7,8 |
|
Project plan verification |
2 days |
Mon 6/19/17 |
Tue 6/20/17 |
10 |
|
Change management planning |
2 days |
Wed 6/21/17 |
Thu 6/22/17 |
11 |
|
Time schedule development |
2 days |
Fri 6/23/17 |
Mon 6/26/17 |
12 |
|
Risk management strategy development |
3 days |
Tue 6/27/17 |
Thu 6/29/17 |
13 |
|
Project execution phase |
15 days |
Tue 6/27/17 |
Mon 7/17/17 |
|
|
Stakeholder’s role allocation |
2 days |
Tue 6/27/17 |
Wed 6/28/17 |
13 |
|
Developers recruitment |
2 days |
Thu 6/29/17 |
Fri 6/30/17 |
16 |
|
Project designing |
3 days |
Mon 7/3/17 |
Wed 7/5/17 |
17 |
|
Project modeling |
2 days |
Thu 7/6/17 |
Fri 7/7/17 |
18,12 |
|
Coding |
2 days |
Mon 7/10/17 |
Tue 7/11/17 |
19 |
|
Unit testing |
2 days |
Wed 7/12/17 |
Thu 7/13/17 |
20 |
|
Integrated testing |
2 days |
Fri 7/14/17 |
Mon 7/17/17 |
21 |
|
Project closure phase |
4 days |
Fri 7/14/17 |
Wed 7/19/17 |
|
|
Establishing secured relationship between the service providers and users |
2 days |
Fri 7/14/17 |
Mon 7/17/17 |
21 |
|
Stakeholder’s signoff |
2 days |
Tue 7/18/17 |
Wed 7/19/17 |
24 |
Before the implementation of the project the project manager should consider different positive as well as negative risks and their impact on the project. The developed project risk register is as follows:
|
Name of the Risks |
Type of the risk |
Impact on the project |
Frequency of occurrence |
Mitigation strategies |
|
Exploitation |
Positive risk |
High |
High |
. In order to gain higher revenue from the competitive market, the project team members should use different new technologies, for adding quick process power. |
|
Virus attack |
Negative risk |
High |
High |
In order to keep the website secured from the external attackers the project manager is needed to adopt encryption algorithm. In this approach the users who have the decryption keys can only access information from the data server. Even it will increase the processing power of the website. |
|
Transfer risk |
Negative risk |
Moderate |
Medium |
During the transfer of date from one server to other, on the transmission channel information might get lost. In order to combat this issues the transmission channel is needed tp be secured from the external attackers. |
|
Software license oriented risk |
Negative risk |
Lower |
Lower |
The chance of occurrence of these issues is quite lower than the others. In order to run the website and its application properly the project manager should the license for different relevant software. If the project manager fails to do so then the entire application of the website will be a failure. |
From different research it has been found in order to gain competitive advantages and measurable revenue structure the best quality website should be delivered to the users. The main goal of the project is to deliver a quality, user friendly and secured website as well to its clients. Most of the measurable qualities include the user friendliness of the website, security and all the desired elements are needed to be associated to the website. The website must support the standards of the Graphical User Interface (GUI) and the content must have the basic objects of the website development. Not only is this but also from the external digital assaults the website required to be protected.
The quality management plan is strictly related to the quality of the project it means that the project manager of the project should focus on the quality of the project. If the PM fails to meet the requirement of the project then, the entire project will be a failure and none of the users will be satisfied with the project plan. The higher management authority and the developers of the project team must furnish and monitor this quality management phase. Considering the project standards the manager should make the quality assurance plan. The quality management team is responsible if any kind of fault occurs. Thus, in the initial phase the project manager should focus of the best quality website including all the standard features.
Gantt Chart
In this phase, the administrative team of the project should keep the project objectives and the end project goal in mind. The revenue of any business organization is dependent upon the project quality and their demand towards the consumers. Similarly, for Social media research centre also the quality of the website will measure the number of consumers they will be able to grab. Though, best quality planning needs extra budget and time thus, for gaining commercial benefit the administration team of the project should focus on the features of the websites developed for social media research center.
For successful completion of the project the project manager should develop a closure checklist and the closure checklist ought to contain the below components:
- Proper maintenance of the project time schedule for successful completion and implementation of the project
- The budget estimated for the project should not be exceeded
- The project quality must cross the preliminary settled standard
- Proper payment estimation is required to be done by all the members of the project team
- After successful completion of the project the team members should signoff from all the project aspects.
- Before implementation the project the project manager should signature on the closing documents.
Conclusion
From the overall discussion it can be concluded that for developing the project for social media research centre, the project manager has estimated a project budget and also for reducing the overall work burden, a project time schedule is also developed for social media research centre. In addition to the project budget and project schedule a quality assurance and risk register is also developed for social media research centre as the project success is dependent on the demand of the website among the consumers of the project.
Brunswicker, S., & Vanhaverbeke, W. (2015). Open innovation in small and medium?sized enterprises (SMEs): External knowledge sourcing strategies and internal organizational facilitators. Journal of Small Business Management, 53(4), 1241-1263.
Chang, W. J. A., Wang, Y. S., & Huang, T. C. (2013). Work design–related antecedents of turnover intention: A multilevel approach. Human Resource Management, 52(1), 1-26.
Du Plessis, H., & Van Niekerk, A. (2014). A new GISc framework and competency set for curricula development at South African universities. South African Journal of Geomatics, 3(1), 1-12.
Dunlap, J. C., & Lowenthal, P. R. (2013). Learning, Unlearning, and Relearning: Using Web 2.0 Technologies to Support the. IT Policy and Ethics: Concepts, Methodologies, Tools, and Applications: Concepts, Methodologies, Tools, and Applications, 170.
Dwivedi, Y. K., Wastell, D., Laumer, S., Henriksen, H. Z., Myers, M. D., Bunker, D., … & Srivastava, S. C. (2015). Research on information systems failures and successes: Status update and future directions. Information Systems Frontiers, 17(1), 143-157.
Elbanna, S. (2015). Intuition in project management and missing links: Analyzing the predicating effects of environment and the mediating role of reflexivity. International Journal of Project Management, 33(6), 1236-1248.
Flyvbjerg, B. (2014). What you should know about megaprojects and why: An overview. Project Management Journal, 45(2), 6-19.
Gustavsson, T. K., & Hallin, A. (2014). Rethinking dichotomization: A critical perspective on the use of “hard” and “soft” in project management research. International Journal of Project Management, 32(4), 568-577.
Risk Register
Heldman, K. (2015). PMP Project Management Professional Exam Deluxe Study Guide: Updated for the 2015 Exam. John Wiley & Sons.
Krajewski, L. J., Ritzman, L. P., & Malhotra, M. K. (2013). Operations management: Processes and supply chains (Vol. 1). New York: Pearson.
Kruchten, P. (2013). Contextualizing agile software development. Journal of Software: Evolution and Process, 25(4), 351-361.
Laporte, C. Y., Houde, R., & Marvin, J. (2014, July). 6.4. 2 Systems Engineering International Standards and Support Tools for Very Small Enterprises. In INCOSE International Symposium (Vol. 24, No. 1, pp. 551-569).
Maniak, R., Midler, C., Lenfle, S., & Pellec?Dairon, M. L. (2014). Value management for exploration projects. Project Management Journal, 45(4), 55-66.
Minden, S. L., Feinstein, A., Kalb, R. C., Miller, D., Mohr, D. C., Patten, S. B., … & Narayanaswami, P. (2014). Evidence-based guideline: Assessment and management of psychiatric disorders in individuals with MS Report of the Guideline Development Subcommittee of the American Academy of Neurology. Neurology, 82(2), 174-181.
Mir, F. A., & Pinnington, A. H. (2014). Exploring the value of project management: linking project management performance and project success. International Journal of Project Management, 32(2), 202-217.
Muller, R., Glückler, J., & Aubry, M. (2013). A relational typology of project management offices. Project Management Journal, 44(1), 59-76.
Orchard, S., Ammari, M., Aranda, B., Breuza, L., Briganti, L., Broackes-Carter, F., … & Duesbury, M. (2013). The MIntAct project—IntAct as a common curation platform for 11 molecular interaction databases. Nucleic acids research, gkt1115.
Parsons, M. A., & Fox, P. A. (2013). Is data publication the right metaphor?. Data Science Journal, 12, WDS32-WDS46.
Paternoster, N., Giardino, C., Unterkalmsteiner, M., Gorschek, T., & Abrahamsson, P. (2014). Software development in startup companies: A systematic mapping study. Information and Software Technology, 56(10), 1200-1218.
Phillips, J. (2013). PMP, Project Management Professional (Certification Study Guides). McGraw-Hill Osborne Media.
Robinson, S. (2014). Simulation: the practice of model development and use. Palgrave Macmillan.
Rosemann, M., & vom Brocke, J. (2015). The six core elements of business process management. In Handbook on business process management 1 (pp. 105-122). Springer Berlin Heidelberg.
Sakas, D., Vlachos, D., & Nasiopoulos, D. (2014). Modelling strategic management for the development of competitive advantage, based on technology. Journal of Systems and Information Technology, 16(3), 187-209.
Salameh, H. (2014). A framework to establish a project management office. European Journal of Business and Management, 6(9), 19-26.
Succar, B., Sher, W., & Williams, A. (2013). An integrated approach to BIM competency assessment, acquisition and application. Automation in Construction, 35, 174-189.
Thamhain, H. (2013). Managing risks in complex projects. Project Management Journal, 44(2), 20-35.
Varajao, J., Dominguez, C., Ribeiro, P., & Paiva, A. (2014). Critical success aspects in project management: similarities and differences between the construction and software industry. Tehni?ki vjesnik, 21(3), 583-589.
Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons.
Vitolo, C., Elkhatib, Y., Reusser, D., Macleod, C. J., & Buytaert, W. (2015). Web technologies for environmental Big Data. Environmental Modelling & Software, 63, 185-198.
vom Brocke, J., & Lippe, S. (2015). Managing collaborative research projects: A synthesis of project management literature and directives for future research. International Journal of Project Management, 33(5), 1022-1039.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
