Desired areas
Analyzing the Virtucon and Globex scenario it has been defined that the company is willing to arrange a 3 days event named as Riverina Agriculture and Lifetime Shows (RALS) for their consumers. The show mainly deals with the local businesses, suppliers of the agricultural equipment suppliers and other lifetime products. The most important components those are strictly required to be followed by the project developers include co –ordination for show stand, live program display, catering and volunteers. The volunteers have thought about this planning in the year of 2000 and the show is organizing by the organizers from 2000. With the number of passing days the numbers of participants are also increasing accordingly thus the queue for ticket booking is also increasing and the participants are losing their patients for this long queue. In order to reduce these issues the organizers have decided to develop an online ticket booking website for their consumers.
This report depicts the scope of the project including the project resources, allotted time and estimated cost as well. In addition to this, for reducing the work pressure from the consumers a work Breakdown structure is also developed by the program organizers. In order to implement the RALS project successfully it is necessary for the project manager to allot proper time and cost for the project. Apart from the time and cost management a quality management and risk management plan is also developed in this report. Even team philosophy must be set properly for the successful execution of the RALS project.
Desired areas |
Ranking |
Impact |
Strategies |
2 |
Proper business and project development strategies will help the project manager to gain measurable business success and even huge number of consumers throughout (Pemsel & Wiewiora, 2013). |
Customers |
3 |
Customers are referred to as the most important asset for any business thus they are needed to be satisfied properly by the services and products of any business. With user friendly online ticket booking website the number of participants will be increased accordingly. |
Operational |
4 |
With the help of functional and operational excellence the consumers will be able to get handle the online ticket booking system properly (Schwalbe, 2015). |
Financial |
1 |
Financial support is the most important thing for the development of RALS project. With the help of this capital invested the additional resources could be added to the system including the security and user friendly mechanism as well (Sanchez, 2015) |
Social |
5 |
The communication approach of between the project manager and the other project team members and even with the sponsors as well could be improved for adopting social components. |
Better: The online ticket booking system will help the project manager to serve better quality and user friendly service to their participants.
Faster: In the online ticket booking system the participants need not to wait in the queue for getting the tickets rather the entire system will become faster that the manual ticket booking system.
Cheaper: The number of manpower will get reduced after the implementation of online ticket booking system because computerized system does not required human power.
In order to implement the RALS project successfully, it is necessary for the project manager to contract with proper project stakeholders. For this project the identified project stakeholders are as follows:
Name of the stakeholders |
Expectation |
Project manager |
To complete the project on time within estimated budget |
Finance manager |
Expect to complete the project within the estimated budget even if additional resources are required. |
Operation manager |
To provide proper operational and functional excellence to the consumers |
Application programming manager |
Provide appreciable application of the website |
HR manager |
To manage the issues of the manpower and all project team members |
Project team members |
To complete the project on time |
WBS |
Task Name |
Duration |
Start |
Finish |
Predecessors |
Resource Names |
Cost Variance |
0 |
RALS timeframe development |
163 days |
Fri 10/6/17 |
Tue 5/22/18 |
$28,624.00 |
||
1 |
Project initiation phase |
51 days |
Fri 10/6/17 |
Fri 12/15/17 |
$9,664.00 |
||
1.1 |
Conceptualizing the details of RALS project |
5 days |
Fri 10/6/17 |
Thu 10/12/17 |
Project manager |
$800.00 |
|
1.2 |
Developing project charter |
18 days |
Fri 10/13/17 |
Tue 11/7/17 |
$3,744.00 |
||
1.2.1 |
Identification of business requirements |
6 days |
Fri 10/13/17 |
Fri 10/20/17 |
2 |
business analyst,project sponsor |
$1,584.00 |
1.2.2 |
Understanding project specification |
5 days |
Mon 10/23/17 |
Fri 10/27/17 |
4 |
business analyst,project sponsor |
$1,320.00 |
1.2.3 |
Arrangement of meeting between the project manager and project team members |
7 days |
Mon 10/30/17 |
Tue 11/7/17 |
5 |
business analyst |
$840.00 |
1.3 |
Vendor appointment |
10 days |
Wed 11/8/17 |
Tue 11/21/17 |
$1,440.00 |
||
1.3.1 |
Identification vendors |
4 days |
Wed 11/8/17 |
Mon 11/13/17 |
6 |
operation manager |
$576.00 |
1.3.2 |
Ability analysis of the vendors according to the budget |
6 days |
Tue 11/14/17 |
Tue 11/21/17 |
8 |
operation manager |
$864.00 |
1.4 |
Feasibility study |
10 days |
Wed 11/22/17 |
Tue 12/5/17 |
9 |
operation manager |
$1,440.00 |
1.5 |
Time management for RALS Project |
8 days |
Wed 12/6/17 |
Fri 12/15/17 |
10 |
finance manager,Project manager |
$2,240.00 |
1.6 |
Milestone 1: Completion of project initiation phase |
0 days |
Fri 12/15/17 |
Fri 12/15/17 |
11 |
Project manager |
$0.00 |
2 |
Project planning phase |
52 days |
Mon 12/18/17 |
Tue 2/27/18 |
$7,088.00 |
||
2.1 |
Understanding the website details for online ticketing system |
10 days |
Mon 12/18/17 |
Fri 12/29/17 |
12 |
application programming manager,operation manager |
$2,720.00 |
2.2 |
Prototyping |
11 days |
Mon 1/1/18 |
Mon 1/15/18 |
14 |
application programming manager |
$1,408.00 |
2.3 |
website testing |
10 days |
Tue 1/16/18 |
Mon 1/29/18 |
2,15 |
application programming manager |
$1,280.00 |
2.4 |
Customer requirement analysis |
9 days |
Tue 1/30/18 |
Fri 2/9/18 |
16 |
HR manager |
$720.00 |
2.5 |
Based on the feedback website development |
12 days |
Mon 2/12/18 |
Tue 2/27/18 |
17 |
HR manager |
$960.00 |
2.6 |
Milestone 2: Completion of project planning phase |
0 days |
Tue 2/27/18 |
Tue 2/27/18 |
18 |
Project manager |
$0.00 |
3 |
Project execution phase |
54 days |
Wed 2/28/18 |
Mon 5/14/18 |
$10,704.00 |
||
3.1 |
Final website development |
7 days |
Wed 2/28/18 |
Thu 3/8/18 |
19 |
application programming manager |
$896.00 |
3.2 |
website modeling |
6 days |
Fri 3/9/18 |
Fri 3/16/18 |
21 |
application programming manager,operation manager |
$1,632.00 |
3.3 |
Coding |
6 days |
Mon 3/19/18 |
Mon 3/26/18 |
22 |
application programming manager,operation manager |
$1,632.00 |
3.4 |
Unit testing |
7 days |
Tue 3/27/18 |
Wed 4/4/18 |
23 |
project tester |
$1,008.00 |
3.5 |
Integration testing |
5 days |
Thu 4/5/18 |
Wed 4/11/18 |
24 |
project tester |
$720.00 |
3.6 |
Final implementation |
6 days |
Thu 4/12/18 |
Thu 4/19/18 |
25 |
Project manager |
$960.00 |
3.7 |
Incorporating online payment options |
8 days |
Fri 4/20/18 |
Tue 5/1/18 |
26 |
finance manager,operation manager,application programming manager |
$3,136.00 |
3.8 |
Review final requirements |
9 days |
Wed 5/2/18 |
Mon 5/14/18 |
27 |
HR manager |
$720.00 |
3.9 |
Milestone 3: Completion of project execution phase |
0 days |
Mon 5/14/18 |
Mon 5/14/18 |
28 |
Project manager |
$0.00 |
4 |
Project closure phase |
6 days |
Tue 5/15/18 |
Tue 5/22/18 |
$1,168.00 |
||
4.1 |
Final documentation |
2 days |
Tue 5/15/18 |
Wed 5/16/18 |
29 |
Project manager |
$320.00 |
4.2 |
Post project evaluation |
2 days |
Thu 5/17/18 |
Fri 5/18/18 |
31 |
Project manager, business analyst |
$560.00 |
4.3 |
Stakeholder signoff |
2 days |
Mon 5/21/18 |
Tue 5/22/18 |
32 |
project sponsor |
$288.00 |
4.4 |
Milestone 4: Completion of project closure phase |
0 days |
Tue 5/22/18 |
Tue 5/22/18 |
33 |
Project manager |
$0.00 |
Figure 1: Gantt chart for RALS Project
(Source: created by author)
With the successful completion of the project the consumers will be able to get tickets online regardless of their location and time as well. They need not to wait in the queues additionally proper Measurable Organizational Values are needed to be utilized properly.
Better
For successful implementation of the project the project manager is required to develop proper scope of the project. For the RALS project the scopes are as follows:
- To give passes for either 1 day, 2 days or even for all the 3 days
- To complete the project within allotted time and estimated budget
- To implement a E- ticket booking system instead of the manual ticket booking system
- To develop risk register, quality management plan as well
The steps needed to implement the scope of the RALS project include the followings:
- Approach for the scope of the project (Kerzner, 2013)
- Roles and responsibilities for each scope
- Identification of scope definition
- RALS project statement
- Scope verification
- Scope control
- Scope change
Resource Name |
Type |
Material Label |
Initials |
Group |
Accrue At |
Base Calendar |
Project manager |
Work |
P |
Prorated |
Standard |
||
project sponsor |
Work |
p |
Prorated |
Standard |
||
finance manager |
Work |
f |
Prorated |
Standard |
||
application programming manager |
Work |
a |
Prorated |
Standard |
||
operation manager |
Work |
o |
Prorated |
Standard |
||
business analyst |
Work |
b |
Prorated |
Standard |
||
project tester |
Work |
p |
Prorated |
Standard |
||
HR manager |
Work |
H |
Prorated |
Standard |
People: The people engaged to the RALS project includes are project manager, operation manager. Finance manager, finance manager, HR manage, business analyst, project tester and other project development team members. The aims of all of these project team members are to provide quality service to the consumers of RALS show participants. If any of these components are missed then the execution of the RALS project will be interrupted completely.
Figure 2: Work Breakdown Structure for RALS Project
(Source: created by author)
WBS |
Task Name |
Duration |
0 |
RALS timeframe development |
163 days |
1 |
Project initiation phase |
51 days |
1.1 |
Conceptualizing the details of RALS project |
5 days |
1.2 |
Developing project charter |
18 days |
1.2.1 |
Identification of business requirements |
6 days |
1.2.2 |
Understanding project specification |
5 days |
1.2.3 |
Arrangement of meeting between the project manager and project team members |
7 days |
1.3 |
Vendor appointment |
10 days |
1.3.1 |
Identification vendors |
4 days |
1.3.2 |
Ability analysis of the vendors according to the budget |
6 days |
1.4 |
Feasibility study |
10 days |
1.5 |
Time management for RALS Project |
8 days |
1.6 |
Milestone 1: Completion of project initiation phase |
0 days |
2 |
Project planning phase |
52 days |
2.1 |
Understanding the website details for online ticketing system |
10 days |
2.2 |
Prototyping |
11 days |
2.3 |
website testing |
10 days |
2.4 |
Customer requirement analysis |
9 days |
2.5 |
Based on the feedback website development |
12 days |
2.6 |
Milestone 2: Completion of project planning phase |
0 days |
3 |
Project execution phase |
54 days |
3.1 |
Final website development |
7 days |
3.2 |
website modeling |
6 days |
3.3 |
Coding |
6 days |
3.4 |
Unit testing |
7 days |
3.5 |
Integration testing |
5 days |
3.6 |
Final implementation |
6 days |
3.7 |
Incorporating online payment options |
8 days |
3.8 |
Review final requirements |
9 days |
3.9 |
Milestone 3: Completion of project execution phase |
0 days |
4 |
Project closure phase |
6 days |
4.1 |
Final documentation |
2 days |
4.2 |
Post project evaluation |
2 days |
4.3 |
Stakeholder signoff |
2 days |
4.4 |
Milestone 4: Completion of project closure phase |
0 days |
Resource Name |
Type |
Material Label |
Initials |
Group |
Max. Units |
Std. Rate |
Ovt. Rate |
Cost/Use |
Accrue At |
Base Calendar |
Project manager |
Work |
P |
100% |
$20.00/hr |
$0.00/hr |
$0.00 |
Prorated |
Standard |
||
project sponsor |
Work |
p |
100% |
$18.00/hr |
$0.00/hr |
$0.00 |
Prorated |
Standard |
||
finance manager |
Work |
f |
100% |
$15.00/hr |
$0.00/hr |
$0.00 |
Prorated |
Standard |
||
application programming manager |
Work |
a |
100% |
$16.00/hr |
$0.00/hr |
$0.00 |
Prorated |
Standard |
||
operation manager |
Work |
o |
100% |
$18.00/hr |
$0.00/hr |
$0.00 |
Prorated |
Standard |
||
business analyst |
Work |
b |
100% |
$15.00/hr |
$0.00/hr |
$0.00 |
Prorated |
Standard |
||
project tester |
Work |
p |
100% |
$18.00/hr |
$0.00/hr |
$0.00 |
Prorated |
Standard |
||
HR manager |
Work |
H |
100% |
$10.00/hr |
$0.00/hr |
$0.00 |
Prorated |
Standard |
Figure 3: Cost estimation for RALS Project
(Source: created by author)
Task Name |
Duration |
RALS timeframe development |
163 days |
Project initiation phase |
51 days |
Project planning phase |
52 days |
Understanding the website details for online ticketing system |
10 days |
Prototyping |
11 days |
website testing |
10 days |
Customer requirement analysis |
9 days |
Based on the feedback website development |
12 days |
Milestone 2: Completion of project planning phase |
0 days |
Project execution phase |
54 days |
Final website development |
7 days |
website modeling |
6 days |
Coding |
6 days |
Unit testing |
7 days |
Integration testing |
5 days |
Final implementation |
6 days |
Incorporating online payment options |
8 days |
Review final requirements |
9 days |
Milestone 3: Completion of project execution phase |
0 days |
Project closure phase |
6 days |
Final documentation |
2 days |
Post project evaluation |
2 days |
Stakeholder signoff |
2 days |
Milestone 4: Completion of project closure phase |
0 days |
Development phase |
Risk of this phase |
Responsible person |
Impact |
Frequency |
Mitigation strategy |
Project initiation phase |
Incorrect cost estimation |
Finance manager |
High |
Frequent |
Proper feasibility study is required to be done at the project initiation phase to avoid the budget oriented issues |
Project planning phase |
Improper component selection |
Operation manager |
High |
Frequent |
In order to implement the RALS project successfully all the components needed for developing online ticket booking system must be selected on time and within the budget |
Project execution phase |
Testing error |
Project tester and application programmer |
Medium |
Frequent |
If the project is not tested properly then at the execution phase the project manager will fail to implement the expectation. Thus experts are needed to be hired for the project testing evaluation |
Project closure phase |
Maintenance error |
Project manager |
High |
Frequent |
In order to gain long term success post project maintenance and long term action plans are required to be developed by the project manager to avoid the post implementation issues (Hornstein, 2015). |
The main philosophy of the project from the team member’s point of view is to “convey quality, on time, reasonable and easy to understand administration to the members of RALS program”. With the assistance of appropriate online ticket booking framework the specialist organizations will be able to grab more number of new shoppers and the existing customers as well (Larson & Gray, 2013). At the same time, the segments those should be considered incorporate initiative and motivational approach of the undertaking project manager, cost administration design of the finance manager and the activities play by the project team members.
Name of the Phases |
Activities |
Verification |
Requirement gathering for website development |
Analyzing gathered data |
|
SLA |
|
Prototype of the website development |
|
Validation |
Prototype modeling and coding |
Unit testing and integration testing |
|
System control |
|
Final documentation of online ticket booking website for RALS project |
Project Activities |
Responsible person |
Signature |
Project initiation phase |
Project manager and project sponsors |
|
Project Planning |
Project manager and business analyst |
|
Project Scope management |
Project manager |
|
Project Budget estimation |
Finance manager |
|
Project Time management |
Project manager |
|
Project Prototype development |
Application programmer analyst |
|
website testing |
tester |
|
Change management |
Project manager |
The project checklist outlines are as follows:
- Passes for RALS show for either 1, 2 or 3 days or for all 3 days
- Family passes are available
- Passes are available for the stall holders, students and kids as well
- Details of ticket are available in the website
- Remaining tickets and details of the sits are also available in the online ticket booking website
- Both offline and online ticket selling options are present for the RALS show participants
The entire project Measurable Organizational Values (MOV) is effectively served by the project manager for meeting the requirement of the online ticket booking system. Due to the presence of the business strategies, consumers, operation, financial support and functional excellences and social support the online ticket booking system will surely get competitive advantages and long term success as well.
Ahern, T., Leavy, B., & Byrne, P. J. (2014). Complex project management as complex problem solving: A distributed knowledge management perspective. International Journal of Project Management, 32(8), 1371-1381.
Boud, D., Cohen, R., & Sampson, J. (Eds.). (2014). Peer learning in higher education: Learning from and with each other. Routledge.
Burke, R. (2013). Project management: planning and control techniques. New Jersey, USA.
Conforto, E. C., Salum, F., Amaral, D. C., da Silva, S. L., & de Almeida, L. F. M. (2014). Can agile project management be adopted by industries other than software development?. Project Management Journal, 45(3), 21-34.
Heldman, K. (2015). PMP project management professional exam deluxe study guide: updated for the 2015 Exam. 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), 291-298.
Joslin, R., & 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), 1377-1392.
Kerzner, H. (2013). 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.
Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A. M. E., & Villanueva, P. (2014). Project risk management methodology for small firms. International Journal of Project Management, 32(2), 327-340.
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.
Pemsel, S., & Wiewiora, A. (2013). Project management office a knowledge broker in project-based organisations. International Journal of Project Management, 31(1), 31-42.
Sanchez, M. A. (2015). Integrating sustainability issues into project management. Journal of Cleaner Production, 96, 319-330.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
Todorovic, M. L., Petrovi?, D. ?., Mihic, M. M., Obradovic, V. L., & Bushuyev, S. D. (2015). Project success analysis framework: A knowledge-based approach in project management. International Journal of Project Management, 33(4), 772-783.
Turner, R. (2016). Gower handbook of project management. Routledge.
Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons.
Walker, A. (2015). Project management in construction. John Wiley & Sons.