Overview of Project Tasks
The main purpose of schedule management plan is to establish the activities as well as criteria that are generally necessary in order to develop monitor as well as control the schedule of the project that is mainly created for implementation of Rugby club App. The entire plan will be approved so that no schedule changes will be permitted unless proper request on the changes is being processed as per the procedures that are mainly set in the change management plan. It is identified that the project manager is the person who is mainly responsible of managing the entire schedule management plan.
It is identified that critical path method is mainly utilized as one the scheduling method within the project “Creation of Rugby Club App”. The critical path method is helpful in calculating the minimum duration of the project that generally helps in determining the scheduling flexibility on the logical path network within the entire schedule model. In addition to this, it is identified that critical path model is helpful in achieving the results of the project in order to deliver the project on proper time.
Work breakdown structure
Figure 1: WBS
(Source: Created by Author)
Task Name |
Idea of the Application |
Evaluation of the idea |
Business planning |
Evaluation of the Market |
Development of the market strategy |
Implementation of the market strategy |
testing and feasibility study of the market |
Coding |
Building the wireframe of the application |
Designing of the user interface |
Experiencing the user design |
Development of the user interface |
Development of the low fidelity prototype |
Testing of the prototype |
Debugging |
Development of the showcase |
Showcase prototype to the client |
Front-end development |
Backend development |
Creation of the test script |
Execution of the test script |
Debugging the issues |
Development of the high fidelity website |
Press release app to the client |
Application training for the administration |
Development of the application |
Feedback gathering |
Making the final changes |
Demonstrate to the investors |
Official launch |
Task Name |
Predecessors |
Idea of the Application |
|
Evaluation of the idea |
|
Business planning |
2 |
Evaluation of the Market |
2,3 |
Development of the market strategy |
3,4 |
Implementation of the market strategy |
|
testing and feasibility study of the market |
5 |
Coding |
7 |
Building the wireframe of the application |
7 |
Designing of the user interface |
7 |
Experiencing the user design |
7 |
Development of the user interface |
11 |
Development of the low fidelity prototype |
|
Testing of the prototype |
8 |
Debugging |
8 |
Development of the showcase |
|
Showcase prototype to the client |
15 |
Front-end development |
17 |
Backend development |
18 |
Creation of the test script |
17,14 |
Execution of the test script |
|
Debugging the issues |
20 |
Development of the high fidelity website |
8 |
Press release app to the client |
22 |
Application training for the administration |
24 |
Development of the application |
24,25 |
Feedback gathering |
|
Making the final changes |
8 |
Demonstrate to the investors |
26 |
Official launch |
29 |
Task Name |
Duration |
Start |
Finish |
Idea of the Application |
7 days |
Thu 22-02-18 |
Fri 02-03-18 |
Evaluation of the idea |
1 day |
Thu 22-02-18 |
Thu 22-02-18 |
Business planning |
2 days |
Fri 23-02-18 |
Mon 26-02-18 |
Evaluation of the Market |
2 days |
Tue 27-02-18 |
Wed 28-02-18 |
Development of the market strategy |
2 days |
Thu 01-03-18 |
Fri 02-03-18 |
Implementation of the market strategy |
9 days |
Mon 05-03-18 |
Thu 15-03-18 |
testing and feasibility study of the market |
1 day |
Mon 05-03-18 |
Mon 05-03-18 |
Coding |
5 days |
Tue 06-03-18 |
Mon 12-03-18 |
Building the wireframe of the application |
4 days |
Tue 06-03-18 |
Fri 09-03-18 |
Designing of the user interface |
8 days |
Tue 06-03-18 |
Thu 15-03-18 |
Experiencing the user design |
3 days |
Tue 06-03-18 |
Thu 08-03-18 |
Development of the user interface |
2 days |
Fri 09-03-18 |
Mon 12-03-18 |
Development of the low fidelity prototype |
2 days |
Tue 13-03-18 |
Wed 14-03-18 |
Testing of the prototype |
2 days |
Tue 13-03-18 |
Wed 14-03-18 |
Debugging |
2 days |
Tue 13-03-18 |
Wed 14-03-18 |
Development of the showcase |
4 days |
Thu 15-03-18 |
Tue 20-03-18 |
Showcase prototype to the client |
2 days |
Thu 15-03-18 |
Fri 16-03-18 |
Front-end development |
1 day |
Mon 19-03-18 |
Mon 19-03-18 |
Backend development |
1 day |
Tue 20-03-18 |
Tue 20-03-18 |
Creation of the test script |
1 day |
Mon 19-03-18 |
Mon 19-03-18 |
Execution of the test script |
14 days |
Tue 13-03-18 |
Fri 30-03-18 |
Debugging the issues |
5 days |
Tue 20-03-18 |
Mon 26-03-18 |
Development of the high fidelity website |
1 day |
Tue 13-03-18 |
Tue 13-03-18 |
Press release app to the client |
1 day |
Tue 27-03-18 |
Tue 27-03-18 |
Application training for the administration |
1 day |
Wed 28-03-18 |
Wed 28-03-18 |
Development of the application |
2 days |
Thu 29-03-18 |
Fri 30-03-18 |
Feedback gathering |
16 days |
Tue 13-03-18 |
Tue 03-04-18 |
Making the final changes |
1 day |
Tue 13-03-18 |
Tue 13-03-18 |
Demonstrate to the investors |
1 day |
Mon 02-04-18 |
Mon 02-04-18 |
Official launch |
1 day |
Tue 03-04-18 |
Tue 03-04-18 |
Controlling schedule mainly involves in monitoring the project status in order to update the progress of the project and for managing the changes within the schedule baseline in order to achieve the plan of the project. The schedule of the project is mainly controlled with the help of two methods that schedule baseline as well as variance threshold.
Figure 2: Network diagram
(Source: Created by Author)
Critical path method is defined as an algorithm that is mainly used for scheduling different set of project activities. It is also considered as one of the longest sequence of various activities in a project plan that is completed on time for the project. The work that is required to be done must be broken down. In order to analyze critical path, it is quite important to know the following terms:
Early start: The earliest time at which an activity can start as per the various logical constraints
Early Finish: It is analyzed as the earliest time with which an activity can finish as per the various logical constraints.
Late Start: The latest time at which, an activity can be initiated as per the logical constraints without affecting the entire duration of the project.
Late finish: It is the latest time, which is needed by an activity in order to finish as per the various logical constraints.
Joslin, R. and 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), pp.1377-1392.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Liberatore, M.J., 2016. A Counterexample to the Forward Recursion in Fuzzy Critical Path Analysis Under Discrete Fuzzy Sets. arXiv preprint arXiv:1607.04583.
MacCrimmon, K.R., 2016. Critical path analysis. The New Palgrave Dictionary of Economics, pp.1-3.
Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A.M.E. and Villanueva, P., 2014. Project risk management methodology for small firms. International journal of project management, 32(2), pp.327-340.
Mir, F.A. and Pinnington, A.H., 2014. Exploring the value of project management: linking project management performance and project success. International journal of project management, 32(2), pp.202-217.
Riol, H. and Thuillier, D., 2015. Project management for academic research projects: balancing structure and flexibility. International Journal of Project Organisation and Management, 7(3), pp.251-269.
Too, E.G. and Weaver, P., 2014. The management of project management: A conceptual framework for project governance. International Journal of Project Management, 32(8), pp.1382-1394.