Limited Time OfferFLAT 20% off & $20 bonus sign up. Order Now
New! Hire Essay Assignment Writer Online and Get Flat 20% Discount!!Order Now
The report discusses the project proposal of Golden Golf Club, which is planning to develop a smart phone app optimized for iphone and Android devices. This app will allow the golfers, tourists and golf enthusiastic to subscribe and pay for accessing the database that includes golfing tips and detailed explanation of golfing approaches. The approach proposed to develop this app is waterfall model (Balaji & Murugaiyan, 2012). The report thoroughly describes the background of the project, project objectives, the strength, weakness, opportunity and threats of the project and problem statement. A project manager is chosen for the project. The budget, schedule estimate and the risks associated with the project are elaborated in the following paragraphs.
The Cobden Golf club is a premier community facility in Corangamite Shire. Recently the club purchased more lands to set about a transition to 18 golf hole form 9 holes. The Cobden Club is however promoted via community website, community notice boards and advertising in the local newspaper, which has a limited reach. Adam Scott the pro golfer wishes to reach a wider market and thus planning to create a mobile app dedicated for the club. This report focuses on the business plan of this project.
Sports Software Inc. has applied for a tender to develop the app for the club with all the specifications set by the club. This project has been made a priority by the CEO due to its utmost importance. The specified project is expected to make a ROI of 28% at least. The time allocated for the developing the app is not more than three months with a budget of $105,000 and therefore the project becomes a top priority for the company. The time frame of the project cannot be altered or increased and therefore, Royce’s waterfall model of project development approach is chosen for this project (Model, 2015).
The objectives identified for the project are listed below (Kerzner, 2013)-
1) The app will allow the golfers, tourists and golf enthusiast to subscribe and pay for accessing the database. This would be beneficial for the Club in business point of view and the tourist as well in learning different golfing strategies and tips.
2) The project is expected to make an ROI of 28%
3) The app will enable the users in booking individual or group golfing clinics and lessons.
4) The reader should be able to subscribe and access the newsletter and the know about the upcoming events with the help of the app.
5) The app should also contain charts detailing the course and green. Videos should be present as well that will display all modern golfing techniques.
6) The app should contain a feedback path, which will allow the user to rank the Cobden Golf Club in terms of quality and services.
Cobden Golf Club provides a wonderful club experience and atmosphere for patrons of all ages. The club recently purchased more set of land to set a transition of about 18 hole layout. The club thus needs a wide advertising strategy to reach wider audience. The SWOT analysis of the Cobden Golf Club is elaborated in the following paragraphs-
The strengths of Cobden Golf Course are listed below-
1) Beautiful and well-maintained course
2) Good Equipment including golf carts
3) Friendly atmosphere
4) Loyal membership
5) Lowest membership cost of the area
6) Excellent reputation
The weaknesses of Cobden Golf Course are listed below-
1) Less promotion and advertising
2) Lack of participation in tournaments
3) Membership is aging and there are not enough golfers
4) Not enough outreach
5) High green fees and cart fees
6) Less business income
The opportunities of Cobden golf Club is listed below-
1) Green fees can be lowered to encourage participation
2) Subscription fee of the app can be lowed to engage more users
3) GPS can be installed in the golf carts to prevent misuse
4) Advertising can be improved using a Smartphone app
5) Training session can be arranged for tournament volunteer
6) All the publications and the newsletter should be accompanied small advertisement.
7) Incentives can be offered to the visitors to increase the engagement.
8) Participation fees can be reduced considerably if the app is successfully implemented
9) The member should get discounted rates on carts. This will increase the number of members.
10) Gaining wider audience with proper advertising of the features and advantages offered in the golf club.
The threats associated with the Cobden Golf club is listed below-
1) Cost of membership is high, which can work against the club
2) With the increasing in the size of the track and golf course with addition of 8 more holes, the cost of maintenance and supplies also increases.
3) Absence of Infrastructure funding
4) Considerable downturn in tourism and economy
5) Old equipments breakdown
6) Huge competition with the other area of activities
The director of the Cobden Golf Club has decided to built and implement a Smartphone app in order to reach a wider market, which includes the great ocean road tourists. The app will help to promote the club and will help in growth of membership, clubroom facility hire and other services, which includes golfing lessons, mentoring, membership and sales of golfing apparels in their pro store (Burke, 2013). The proposed project will increase the business opportunities of the project and will also help the club in reaching wider audience and attract more tourists. This will furthermore help in decreasing the membership cost of the Club, and will therefore help in attracting more members.
From the above picture, it can be seen that ROI is almost 28% as estimated by the club and the breakeven is occurring between year 2 and 3.
The scope of the project is development of an app optimized for iphone and Android devices. The allocated schedule for the app is 3 months. The development and implementation of the app should therefore take not more than 12 weeks and the allocated budget should not undergo revision (Schwalbe, 2015).
The requirements of the project includes, appointed of a well-experienced project manager and an efficient product development team. Waterfall project approach is to be chosen in order to complete the project within schedule time. The task requires a complete project plan along with a proper feasibility study for initiating the project (Martinelli & Milosevic, 2016).
The Cost Model of the proposed project is elaborated in following table-
Task Name | Duration | Cost |
SmartPhone App | 90 days | $104,428.00 |
Project Starts | 0 days | $0.00 |
Initiation | 15 days | $9,840.00 |
Economic Feasibility | 3 days | $1,800.00 |
Technical feasibility | 3 days | $1,800.00 |
Operational Feasibility | 3 days | $1,800.00 |
Meeting with client | 2 days | $1,280.00 |
Knowing the basic requirement | 1 day | $1,240.00 |
Documenting the requirements | 2 days | $1,280.00 |
Sharing documents with client | 1 day | $640.00 |
Planning | 6 days | $4,512.00 |
Technical requirement | 2 days | $2,112.00 |
resources to be used | 4 days | $2,400.00 |
Execution | 39 days | $81,848.00 |
Designing | 4 days | $73,640.00 |
Coding | 14 days | $6,384.00 |
Developing | 3 days | $1,368.00 |
Client's Approval | 1 day | $0.00 |
Implementing Changes according to the requirements | 1 day | $456.00 |
Testing | 15 days | $4,096.00 |
Unit Testing | 2 days | $480.00 |
White-box Testing | 2 days | $480.00 |
Black-box testing | 1 day | $240.00 |
System Testing | 2 days | $480.00 |
Performance Testing | 1 day | $240.00 |
Integration Testing | 1 day | $240.00 |
usability Testing | 2 days | $480.00 |
User Acceptance testing | 1 day | $240.00 |
Debugging ( if required) | 1 day | $456.00 |
Documentation | 1 day | $120.00 |
Share documents with Client | 1 day | $640.00 |
Go-Live | 15 days | $4,132.00 |
Demonstration of App | 2 days | $1,280.00 |
Training the users | 1 day | $640.00 |
project execution by client | 1 day | $0.00 |
Debugging | 2 days | $912.00 |
Documents Handover | 1 day | $640.00 |
Archieve Documents | 1 day | $20.00 |
Payment Completion | 3 days | $0.00 |
releasing resources | 1 day | $640.00 |
Client Signoff | 1 day | $0.00 |
Client's feedback | 2 days | $0.00 |
Project ends | 0 days | $0.00 |
% Complete | WBS | Task Name | Duration | Start | Finish |
96% | 0 | SmartPhone App | 90 days | Mon 02-10-17 | Fri 02-02-18 |
100% | 1 | Project Starts | 0 days | Mon 02-10-17 | Mon 02-10-17 |
100% | 2 | Initiation | 15 days | Mon 02-10-17 | Fri 20-10-17 |
100% | 2.1 | Economic Feasibility | 3 days | Mon 02-10-17 | Wed 04-10-17 |
100% | 2.2 | Technical feasibility | 3 days | Thu 05-10-17 | Mon 09-10-17 |
100% | 2.3 | Operational Feasibility | 3 days | Tue 10-10-17 | Thu 12-10-17 |
100% | 2.4 | Meeting with client | 2 days | Fri 13-10-17 | Mon 16-10-17 |
100% | 2.5 | Knowing the basic requirement | 1 day | Tue 17-10-17 | Tue 17-10-17 |
100% | 2.6 | Documenting the requirements | 2 days | Wed 18-10-17 | Thu 19-10-17 |
100% | 2.7 | Sharing documents with client | 1 day | Fri 20-10-17 | Fri 20-10-17 |
100% | 3 | Planning | 6 days | Mon 23-10-17 | Mon 30-10-17 |
100% | 3.1 | Technical requirement | 2 days | Mon 23-10-17 | Tue 24-10-17 |
100% | 3.2 | resources to be used | 4 days | Wed 25-10-17 | Mon 30-10-17 |
99% | 4 | Execution | 39 days | Tue 31-10-17 | Fri 22-12-17 |
99% | 4.1 | Designing | 4 days | Tue 31-10-17 | Fri 03-11-17 |
100% | 4.2 | Coding | 14 days | Mon 06-11-17 | Thu 23-11-17 |
100% | 4.3 | Developing | 3 days | Fri 24-11-17 | Tue 28-11-17 |
100% | 4.4 | Client's Approval | 1 day | Thu 21-12-17 | Thu 21-12-17 |
100% | 4.5 | Implementing Changes according to the requirements | 1 day | Fri 22-12-17 | Fri 22-12-17 |
100% | 5 | Testing | 15 days | Mon 25-12-17 | Fri 12-01-18 |
100% | 5.1 | Unit Testing | 2 days | Mon 25-12-17 | Tue 26-12-17 |
100% | 5.2 | White-box Testing | 2 days | Wed 27-12-17 | Thu 28-12-17 |
100% | 5.3 | Black-box testing | 1 day | Fri 29-12-17 | Fri 29-12-17 |
100% | 5.4 | System Testing | 2 days | Mon 01-01-18 | Tue 02-01-18 |
100% | 5.5 | Performance Testing | 1 day | Wed 03-01-18 | Wed 03-01-18 |
100% | 5.6 | Integration Testing | 1 day | Thu 04-01-18 | Thu 04-01-18 |
100% | 5.7 | usability Testing | 2 days | Fri 05-01-18 | Mon 08-01-18 |
100% | 5.8 | User Acceptance testing | 1 day | Tue 09-01-18 | Tue 09-01-18 |
100% | 5.9 | Debugging ( if required) | 1 day | Wed 10-01-18 | Wed 10-01-18 |
100% | 5.10 | Documentation | 1 day | Thu 11-01-18 | Thu 11-01-18 |
100% | 5.11 | Share documents with Client | 1 day | Fri 12-01-18 | Fri 12-01-18 |
80% | 6 | Go-Live | 15 days | Mon 15-01-18 | Fri 02-02-18 |
100% | 6.1 | Demonstration of App | 2 days | Mon 15-01-18 | Tue 16-01-18 |
100% | 6.2 | Training the users | 1 day | Wed 17-01-18 | Wed 17-01-18 |
100% | 6.3 | project execution by client | 1 day | Thu 18-01-18 | Thu 18-01-18 |
100% | 6.4 | Debugging | 2 days | Fri 19-01-18 | Mon 22-01-18 |
100% | 6.5 | Documents Handover | 1 day | Tue 23-01-18 | Tue 23-01-18 |
100% | 6.6 | Archive Documents | 1 day | Wed 24-01-18 | Wed 24-01-18 |
100% | 6.7 | Payment Completion | 3 days | Thu 25-01-18 | Mon 29-01-18 |
100% | 6.8 | releasing resources | 1 day | Tue 30-01-18 | Tue 30-01-18 |
0% | 6.9 | Client Signoff | 1 day | Wed 31-01-18 | Wed 31-01-18 |
0% | 6.10 | Client's feedback | 2 days | Thu 01-02-18 | Fri 02-02-18 |
0% | 7 | Project ends | 0 days | Fri 02-02-18 | Fri 02-02-18 |
Task Name | Duration | Start | Finish |
SmartPhone App | 90 days | Mon 02-10-17 | Fri 02-02-18 |
Project Starts | 0 days | Mon 02-10-17 | Mon 02-10-17 |
Initiation | 15 days | Mon 02-10-17 | Fri 20-10-17 |
Planning | 6 days | Mon 23-10-17 | Mon 30-10-17 |
Execution | 39 days | Tue 31-10-17 | Fri 22-12-17 |
Testing | 15 days | Mon 25-12-17 | Fri 12-01-18 |
Go-Live | 15 days | Mon 15-01-18 | Fri 02-02-18 |
Project ends | 0 days | Fri 02-02-18 | Fri 02-02-18 |
WBS | Task Name | Duration | Start | Finish |
0 | SmartPhone App | 90 days | Mon 02-10-17 | Fri 02-02-18 |
1 | Project Starts | 0 days | Mon 02-10-17 | Mon 02-10-17 |
2 | Initiation | 15 days | Mon 02-10-17 | Fri 20-10-17 |
2.1 | Economic Feasibility | 3 days | Mon 02-10-17 | Wed 04-10-17 |
2.2 | Technical feasibility | 3 days | Thu 05-10-17 | Mon 09-10-17 |
2.3 | Operational Feasibility | 3 days | Tue 10-10-17 | Thu 12-10-17 |
2.4 | Meeting with client | 2 days | Fri 13-10-17 | Mon 16-10-17 |
2.5 | Knowing the basic requirement | 1 day | Tue 17-10-17 | Tue 17-10-17 |
2.6 | Documenting the requirements | 2 days | Wed 18-10-17 | Thu 19-10-17 |
2.7 | Sharing documents with client | 1 day | Fri 20-10-17 | Fri 20-10-17 |
3 | Planning | 6 days | Mon 23-10-17 | Mon 30-10-17 |
3.1 | Technical requirement | 2 days | Mon 23-10-17 | Tue 24-10-17 |
3.2 | resources to be used | 4 days | Wed 25-10-17 | Mon 30-10-17 |
4 | Execution | 39 days | Tue 31-10-17 | Fri 22-12-17 |
4.1 | Designing | 4 days | Tue 31-10-17 | Fri 03-11-17 |
4.2 | Coding | 14 days | Mon 06-11-17 | Thu 23-11-17 |
4.3 | Developing | 3 days | Fri 24-11-17 | Tue 28-11-17 |
4.4 | Client's Approval | 0 days | Thu 21-12-17 | Thu 21-12-17 |
4.5 | Implementing Changes according to the requirements | 1 day | Fri 22-12-17 | Fri 22-12-17 |
5 | Testing | 15 days | Mon 25-12-17 | Fri 12-01-18 |
5.1 | Unit Testing | 2 days | Mon 25-12-17 | Tue 26-12-17 |
5.2 | White-box Testing | 2 days | Wed 27-12-17 | Thu 28-12-17 |
5.3 | Black-box testing | 1 day | Fri 29-12-17 | Fri 29-12-17 |
5.4 | System Testing | 2 days | Mon 01-01-18 | Tue 02-01-18 |
5.5 | Performance Testing | 1 day | Wed 03-01-18 | Wed 03-01-18 |
5.6 | Integration Testing | 1 day | Thu 04-01-18 | Thu 04-01-18 |
5.7 | usability Testing | 2 days | Fri 05-01-18 | Mon 08-01-18 |
5.8 | User Acceptance testing | 1 day | Tue 09-01-18 | Tue 09-01-18 |
5.9 | Debugging ( if required) | 1 day | Wed 10-01-18 | Wed 10-01-18 |
5.10 | Documentation | 1 day | Thu 11-01-18 | Thu 11-01-18 |
5.11 | Share documents with Client | 1 day | Fri 12-01-18 | Fri 12-01-18 |
6 | Go-Live | 15 days | Mon 15-01-18 | Fri 02-02-18 |
6.1 | Demonstration of App | 2 days | Mon 15-01-18 | Tue 16-01-18 |
6.2 | Training the users | 1 day | Wed 17-01-18 | Wed 17-01-18 |
6.3 | project execution by client | 1 day | Thu 18-01-18 | Thu 18-01-18 |
6.4 | Debugging | 2 days | Fri 19-01-18 | Mon 22-01-18 |
6.5 | Documents Handover | 1 day | Tue 23-01-18 | Tue 23-01-18 |
6.6 | Archieve Documents | 1 day | Wed 24-01-18 | Wed 24-01-18 |
6.7 | Payment Completion | 3 days | Thu 25-01-18 | Mon 29-01-18 |
6.8 | releasing resources | 1 day | Tue 30-01-18 | Tue 30-01-18 |
6.9 | Client Signoff | 1 day | Wed 31-01-18 | Wed 31-01-18 |
6.10 | Client's feedback | 2 days | Thu 01-02-18 | Fri 02-02-18 |
7 | Project ends | 0 days | Fri 02-02-18 | Fri 02-02-18 |
The risks identified for the project are listed below (Artto & Kahkonen, 2013)-
1) Financial Risk- The club may face a huge financial risk if the project is not able to be implemented in the schedule time.
2) Changing requirements- If the requirements of the project changes while the implementation of the project, the project may suffer considerable time loss and loss of capital as well.
3) Incomplete requirements – having clear requirements of the project is essential for implementing a project in Waterfall approach. This is because in waterfall methodology, the whole project is divided into a number of phases and initiation of each phase depends on the completion of the previous phase. Therefore, change in requirements in one phase may result in considerable delay in other phase and ultimately the whole project.
4) Scope risk- This risk includes integration issues, hardware and software defects and change in dependencies (Thamhain, 2013).
List of prioritized risks are elaborated in the following table-
Therefore, from the above discussion, it can be concluded that, the project that deals with the implementation of a Smartphone app has a very clear scope and requirement. The project is set to be completed within 3 months and an experienced project manager is appointed for the project. The report elaborates the business plan of the project, which includes financial analysis and budget estimation. The report identifies the associated risk in the project, which is needed to be eliminated with a proper risk management plan. The successful implementation of the project will increase the business profit of the organization and will help the organization in reaching wider audience. Therefore, the project is feasible to be implement and the initiation of the project should be done as soon as possible.
Artto, K. A., & Kahkonen, K. (2013). Managing risks in projects. Routledge.
Balaji, S., & Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A comparative study on SDLC. International Journal of Information Technology and Business Management, 2(1), 26-30.
Burke, R. (2013). Project management: planning and control techniques. New Jersey, USA.
Kerzner, H. (2013). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Martinelli, R. J., & Milosevic, D. Z. (2016). Project management toolbox: tools and techniques for the practicing project manager. John Wiley & Sons.
Model, W. (2015). Waterfall model. Luettavissa: http://www. waterfall-model. com/. Luettu, 3.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
Thamhain, H. (2013). Managing risks in complex projects. Project Management Journal, 44(2), 20-35.
No matter how close the deadline is, you will find quick solutions for your urgent assignments.
All assessments are written by experts based on research and credible sources. It also quality-approved by editors and proofreaders.
Our team consists of writers and PhD scholars with profound knowledge in their subject of study and deliver A+ quality solution.
We offer academic help services for a wide array of subjects.
We care about our students and guarantee the best price in the market to help them avail top academic services that fit any budget.
15,000+ happy customers and counting!