Project Objective
The purpose of the report is to prepare a business case for Warcraft Ltd App Project. Warcraft Ltd App is a project of Warcraft Ltd. which is a private limited company. The Application is aimed to provide a live action role playing game where the participants of the game will be physically portraying their characters. The main aim of this project is to provide a real life experience to the gamers. A website for the same is already there. Jack Johnson is the managing director of this company. However, the company has been experiencing a considerable reduction in the players along with the inability of retaining the players. Therefore, a project has been undertaken in order to redesign the website and develop an application or both apple and android users in order to increase the participation in the game (Tracy, 2012).
The main objective of the project is to redesign the existing website for enhancing the gaming experiences of the participants. This is a project that is needed to be implemented in a priority basis (Kerzner & Kerzner, 2017). The project aims in developing a mobile application as well (Joorabchi, Mesbah & Kruchten, 2013). The objective of the project is therefore to propose and develop a mobile application for Warcraft Ltd which will be optimized for both iphone and android users. The application will allow the clients to enroll and pay for lessons, booking tours and watch videos. The application should be designed in such a way that users should be able to subscribe to the warcraft newsletter.
Warcraft Ltd. has marked this project to be of a high priority. This is done in order to ensure that the project is completed within the time limit of 5 months. In order to successfully develop the business case for the project it is essential to evaluate the strengths, weakness, opportunities and the threats associated with the project.
The organization Warcraft Ltd aims at providing a real life gaming experiences to the participants, a concept which is very new. This would be an area of interest for the young gamers. Therefore, this application that will be developed is expected to attract a large number of young gamers. This is a major strength of the project.
There is an already existing website for the same where the gamers have not the interest which was expected. Furthermore, the website has experienced quite fall in the in number of participants as well. This results in a conflict among the stakeholders who are not quite happy with the marketing strategy of the company.
Project Strengths and Weaknesses
The plan of developing a smartphone application for the game gives an opportunity to the company to attract a large number of smartphone users (Heitkötter, Hanschke & Majchrzak, 2012). This will increase the reach of the game to a large number of users irrespective of any age group.
One of the major threats associated with this project is that, it will be implemented in a much less time and therefore, there are high chances of not getting the desired results. Furthermore, since an already existing idea will be modified, it has a threat from the other new gaming applications as well.
The project is declared to be a high priority project as it should be completed within five months. Waterfall project management approach will be undertaken in order to complete the project. In waterfall approach the testing is generally done at the end of the project and therefore it is very necessary to implement the project in a controlled environment. Another problem associated with the project is that since the previously designed website failed to attract the expected amount of participants, the stakeholders are not sure about the success of the project.
The assumptions and the constraints associated with Warcraft Ltd App Project are as follows-
Assumptions
- It is assumed that the resources estimated for the project will be enough for successful completion of the project (Bratton & Gold, 2012).
- The estimated budget will not need any revision during project implementation
- The budget takes into consideration the possible hike in the price of materials and the labourers.
- The identified resources will be easily available.
- The budget takes into consideration, the payment of the workers.
Constraints
- The project cannot be delayed and should be completed within 5 months with a budget of $170,000.
- The testing process is very important for this project
- There are certain anticipated changes in the project after the success of tender bid.
The proper implementation of the project is quite crucial. The options available for proper execution of the project are as follows-
- A proper leadership and team motivation is needed in order to implement the project within the limited time of five months (Yidong & Xinxin, 2013). This is because motivation is a key factor in management of a team.
- A proper project plan is needed to be prepared at the initiation stage of the project, which would be followed in the execution phase of the project.
The project will be following a waterfall approach of project implementation and therefore it is recommended to execute the project in a plan environment (Model, 2015). Since successful implementation of one phase is essential for proper project execution, it is recommended that the project plan should be strictly followed in project execution.
The initial investment in year 0 is $170,000 followed by $25000 in year 1 and 2 followed by $20000 in year 3. The discount rate is 10%. Based on this data, the NPV, ROI and payback is calculated.
The project is expected to make atleast 22% ROI. The calculated ROI therefore meets the expectation and therefore the project is feasible. The calculated NVP is 105100.
The preliminary project requirements are as follows (Kerzner, 2013)-
- The budget calculation should be completed at the initiation stage of the project
- The project manager will be paid at a rate of $100 p/hr for 2 days per week.
- The project is needed to be completed within five months.
The schedule of the project is represented in the following table (Larson & Gray, 2013)-
WBS |
Task Name |
Duration |
Start |
Finish |
0 |
Warcraft Ltd App Project |
112 days |
Fri 01-06-18 |
Mon 05-11-18 |
1 |
Project starts |
0 days |
Fri 01-06-18 |
Fri 01-06-18 |
2 |
Requirement Analysis |
14 days |
Fri 01-06-18 |
Wed 20-06-18 |
2.1 |
Understanding the requirements |
4 days |
Fri 01-06-18 |
Wed 06-06-18 |
2.2 |
Identification of the application features |
4 days |
Thu 07-06-18 |
Tue 12-06-18 |
2.3 |
Feasibility study |
5 days |
Wed 13-06-18 |
Tue 19-06-18 |
2.4 |
Documenting the findings |
1 day |
Wed 20-06-18 |
Wed 20-06-18 |
3 |
Design/Operation |
14 days |
Thu 21-06-18 |
Tue 10-07-18 |
3.1 |
Modification of website and designing the application |
5 days |
Thu 21-06-18 |
Wed 27-06-18 |
3.2 |
Project Team allocation |
2 days |
Thu 28-06-18 |
Fri 29-06-18 |
3.3 |
Identifying the required resources |
4 days |
Mon 02-07-18 |
Thu 05-07-18 |
3.4 |
Scheduling the works |
3 days |
Fri 06-07-18 |
Tue 10-07-18 |
4 |
Implementation |
21 days |
Wed 11-07-18 |
Wed 08-08-18 |
4.1 |
Framework |
11 days |
Wed 11-07-18 |
Wed 25-07-18 |
4.1.1 |
Designing |
4 days |
Wed 11-07-18 |
Mon 16-07-18 |
4.1.2 |
Coding |
7 days |
Tue 17-07-18 |
Wed 25-07-18 |
4.2 |
Database |
10 days |
Thu 26-07-18 |
Wed 08-08-18 |
4.2.1 |
Designing |
3 days |
Thu 26-07-18 |
Mon 30-07-18 |
4.2.2 |
Coding |
5 days |
Tue 31-07-18 |
Mon 06-08-18 |
4.2.3 |
Linking with application |
2 days |
Tue 07-08-18 |
Wed 08-08-18 |
5 |
Testing |
21 days |
Thu 09-08-18 |
Thu 06-09-18 |
5.1 |
Unit testing |
5 days |
Thu 09-08-18 |
Wed 15-08-18 |
5.2 |
Alpha Testing |
3 days |
Thu 16-08-18 |
Mon 20-08-18 |
5.3 |
System testing |
3 days |
Tue 21-08-18 |
Thu 23-08-18 |
5.4 |
Beta testing |
3 days |
Fri 24-08-18 |
Tue 28-08-18 |
5.5 |
Usability testing |
3 days |
Wed 29-08-18 |
Fri 31-08-18 |
5.6 |
User acceptance testing |
2 days |
Mon 03-09-18 |
Tue 04-09-18 |
5.7 |
Debugging(if required) |
2 days |
Wed 05-09-18 |
Thu 06-09-18 |
6 |
Deployment |
21 days |
Fri 07-09-18 |
Fri 05-10-18 |
6.1 |
application demonstration |
7 days |
Fri 07-09-18 |
Mon 17-09-18 |
6.2 |
Training |
10 days |
Tue 18-09-18 |
Mon 01-10-18 |
6.3 |
Debugging |
4 days |
Tue 02-10-18 |
Fri 05-10-18 |
7 |
Project Handover/Maintenance |
21 days |
Mon 08-10-18 |
Mon 05-11-18 |
7.1 |
D |
5 days |
Mon 08-10-18 |
Fri 12-10-18 |
7.2 |
Payment completion |
3 days |
Mon 15-10-18 |
Wed 17-10-18 |
7.3 |
Resource release |
3 days |
Thu 18-10-18 |
Mon 22-10-18 |
7.4 |
Client feedback and maintenance |
10 days |
Tue 23-10-18 |
Mon 05-11-18 |
8 |
Project ends |
0 days |
Mon 05-11-18 |
Mon 05-11-18 |
Table 1: Representing the Schedule of the Project
(Source: Created by Author using MS project)
The potential risks associated with the project are as follows –
- The stakeholders’ conflict is a major risk associated with this project that might result in project delay.
- End users acceptance of this application is another significant risk associated with the project.
- Failure of the project being completed in schedule time is another risk associated with the project.
Conclusion
The report gives an overview of the business case analysis of Warcraft Ltd App Project. The detailed scope and problems associated with the project is discussed. The report calculated the cost estimate and the schedule of the project. The project is found to be feasible with an estimated ROI of 46% and payback between year 1 and year 2.
References
Bratton, J., & Gold, J. (2012). Human resource management: theory and practice. Palgrave Macmillan.
Heitkötter, H., Hanschke, S., & Majchrzak, T. A. (2012, April). Evaluating cross-platform development approaches for mobile applications. In International Conference on Web Information Systems and Technologies (pp. 120-138). Springer, Berlin, Heidelberg.
Joorabchi, M. E., Mesbah, A., & Kruchten, P. (2013, October). Real challenges in mobile app development. In Empirical Software Engineering and Measurement, 2013 ACM/IEEE International Symposium on (pp. 15-24). IEEE.
Kerzner, H. (2013). 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.
Larson, E. W., & Gray, C. (2013). Project management: The managerial process with MS project. McGraw-Hill.
Model, W. (2015). Waterfall model. Luettavissa: https://www. waterfall-model. com/. Luettu, 3.
Tracy, K. W. (2012). Mobile application development experiences on Apple’s iOS and Android OS. Ieee Potentials, 31(4), 30-34.
Yidong, T., & Xinxin, L. (2013). How ethical leadership influence employees’ innovative work behavior: A perspective of intrinsic motivation. Journal of Business Ethics, 116(2), 441-455.