Assumptions
WBS |
Task Name |
0 |
Development of Social Media Research Centre Application |
1 |
Start of the project |
2 |
Project initiation phase |
2.1 |
Preparation of the project charter document |
2.2 |
Arrangement of meeting with the stakeholders |
2.3 |
Requesting project charter approval |
M1 |
Improvement of project charter |
4 |
Phase 1: Requirement analysis and specification |
4.1 |
Requirement gathering and analysis |
4.2 |
Preparation of requirement specification document |
M2 |
Completion of requirement specification document development |
6 |
Phase 2: Review phase |
6.1 |
Project charter review |
6.2 |
Review of the requirement identified |
6.3 |
Preparing technical document review |
M3 |
Completion of review of the technical document |
8 |
Phase 3: Planning Phase |
8.1 |
Development of the work break down structure |
8.2 |
Development of the project schedule |
8.3 |
Resource allocation |
8.4 |
Cost estimation |
8.5 |
Stakeholder analysis |
8.6 |
Preparation of the test plan |
8.7 |
Risk management plan preparation |
8.8 |
Change management plan development |
M4 |
Completing the WBS, project schedule and cost estimation |
10 |
Phase 4: Project design phase |
10.1 |
Requirement identification |
10.2 |
Preparation of a draft for providing a designing overview |
10.3 |
Analysis of the different features of the website |
10.4 |
Creation of the colouring schema for preparation of the design |
10.5 |
Identification of the contents to be included in the website |
10.6 |
Documentation of the overall layout of the website |
M5 |
Completion of the project design phase |
12 |
Phase 5: Project development phase |
12.1 |
Functional requirement analysis |
12.2 |
Development of the wireframes of the website |
12.3 |
Development of the modules for the website |
12.4 |
Coding program for the development of the modules |
12.5 |
Database designing |
M6 |
Completing the development of the website |
14 |
Phase 6: Testing phase |
14.1 |
Unit testing |
14.2 |
Integration testing |
14.3 |
System testing |
14.4 |
Usability testing |
M7 |
Completion of the testing phase |
16 |
Go-live phase |
16.1 |
Host the website |
16.2 |
Deployment of the website |
17 |
Project Closure |
Figure 1: Project schedule prepared for the project
(Source: Created by Author)
Figure 2: Time phased budget
(Source: Created by Author)
Assumptions and constraints considered for the development of the project budget
Assumptions
The assumptions made for the development of the budget of the project are listed as follows:
- The project development team works for 5 days in a week and for 8 hours per day.
- The raw materials required for the development of the project is available in market and would be available for the tenure of the development of the project.
- The errors and the problems generated during the course of development of the project would be resolved immediately by the project and it would not act as a barrier for the development of the project
- The daily wage of the labors an the development team would not increase during the course of development of the project
- The project would not be affected by the inflation or economic crisis arising during the development of the project.
Constraints
The constraints of the project act as a barrier for the development process are listed as follows:
- The project is required to be developed within the proposed budget of AUD 50,000
- The project is required to be completed within a duration of 7 months from the starting date of the project.
- The resources required is required to be available throughout the duration of the project development
- A 20 percent cost is required to be allocated for fringe for handling the risk arising during the development of the project
Examples of known knowns and known unknowns on the project
The examples of known knowns on the project that have been identified are as below:
- Requirement of additional members in project team thus increasing direct labor costs.
- Extension of the project due to changes in scope resulting into increase in project cost.
- Sudden inflation in the price of hardware and software materials required for development of website.
The examples of known unknowns on the project that have been identified are as below:
- Allocation of additional resources during progress of the project will incur additional budget.
- Request for changes in project scope may increase the budget.
- The resource costs may increase with time during the project.
Preparation of the budget for both known and unknowns
A bottom up cost estimation techniques is followed for the calculation of the cost for the known and the unknowns associated with the development of the project. The bottom up cost estimation technique is the most time consuming process and yet it provides the most accurate result for the calculation of the budget. It is the most appropriate technique for the project that has been done before by the development team and have idea about the development process. For the preparation of the project budget the whole development team is included and the cost for the completion of each of the activity involved in the development of the project is added for the calculation of the total cost.
For the preparation of the project budget a cost of about 10,000 is kept for fringe for handling the risk associated with the development of the project and thus the main project is required to be completed within AUD 40,000.
Risk ID |
Description and Cause |
Proximity |
Likelihood |
Consequence |
Level |
Treatment Response |
Treatment |
R01 |
Project charter approval delay |
Medium |
Likely |
Major |
High |
Reduce |
The project charter have to be distributed among the officials evenly and discussed with priority. |
R02 |
Over budgeting of the project |
High |
Possible |
Major |
High |
Avoid |
A proper cost estimation technique is required to be followed for the calculation of the budget |
R03 |
Changes in requirements and project scope |
Low |
Unlikely |
Minor |
Low |
Transfer |
A change management plan is required to be developed for handling the risk of change arising in the project |
R04 |
Changes in the design of website |
Medium |
Unlikely |
Major |
Medium |
Avoid |
The prototype design is required to be reviewed by the project stakeholders |
Team’s philosophy statement or objective
The team members involved in the project development mainly focuses on the requirement of the project and aligns the project with the requirement. The functionality for the website is required to be implemented after analyzing the requirement and the website is developed keeping the quality of the project in mind. Standard sized fonts are used such that the contents of the website is readable and the background colour of the website is kept light for making the front text readable.
Development and description of three quality issues
The quality issues associated with the development of the project are listed as follows:
- To develop the project within a realistic budget – This is one of the significant quality issues related with this venture as the improper estimation of spending plan may prompt low nature of work.
- Improper outline of the site – The site being created is not easy to use as the plan is mind boggling additionally the look and feel is not tasteful as it is not satisfying in setting to perspective of clients.
- Integration with database – The database association flops in the middle of the exchange by customers. The database engineers will outline the database with functionalities to restore it to past state in the event of disappointment or association is lost.
Development of Closure checklist
The checklist of the project closure that is required to be developed for the development of the website are listed as follows:
The task outlined in the work breakdown structure has been completed |
A risk mitigation plan has been created for the mitigation of the risk raised during the development of the project |
The project goals has been fulfilled |
A project document has been created with the feedback of the stakeholders associated with the project |
The success criteria for the project has been evaluated |
The team members of the project has been released clearing all the dues |
The expense cost has been released and invoice is reserved for future use |
Completion of the evaluation of the project |
Development of project evaluation
The evaluation of project’s Measurable Organizational Value will be conducted with the help of following:
Areas |
MOV of the project |
Client |
The important information are embedded in the home page of the website |
Economical |
The website is kept light and it consumes less data during navigation to different page |
Social |
Social application is integrated for sharing the content of the website in social media platform |
Connectivity |
The users can access the website from remote location from different platform and devices |
Conde, M. A., García-Peñalvo, F. J., Rodríguez-Conde, M. J., Alier, M., Casany, M. J., & Piguillem, J. (2014). An evolving Learning Management System for new educational environments using 2.0 tools. Interactive Learning Environments, 22(2), 188-204.
Kerzner, H. (2013). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.