By

Submission date:

Department of Management Sciences

Table of Contents
Schedule Management Plan...................................................................................................................3
Introduction...........................................................................................................................................3
Purpose of the Schedule Management Plan.........................................................................................3
Scheduling Methodology........................................................................................................................3
Scheduling Software...............................................................................................................................3
Rules for how Schedule estimates should be stated...............................................................................4
Threshold for Acceptable Variance.........................................................................................................4
Schedule Baseline..................................................................................................................................4
Performance Measures Used.................................................................................................................5
Plan for managing Schedule Variance....................................................................................................5
A process for determining whether Variance must be acted upon.........................................................6
Identification of Schedule Change Control Procedure............................................................................6
Types of Reports....................................................................................................................................6
Project status report................................................................................................................................6
Variance report........................................................................................................................................7
Time tracking report................................................................................................................................7
Team availability reports.........................................................................................................................7
Formatting and Frequency of Reports....................................................................................................7
Contingency Reserves............................................................................................................................7
List of activities......................................................................................................................................8
Schedule Development..........................................................................................................................9
Pert Mean duration.................................................................................................................................9
Network Diagram.................................................................................................................................11
All Activities(Lead ,lag ,baseline)............................................................................................................13
Schedule Management Plan

Introduction

A detailed schedule management plan is an essential part of project management plan and it
helps in managing and achieving milestones as planned. We have made a thorough and detailed
schedule plan for our project i.e. IOT-based Fire Fighting Robot, the plan is being made
considering the project’s budget, available resources, expertise of team members and other
possible constraints.

Schedule Management Plan will also help in measuring progress, achieving goals and in the
generation of reports after the actual work is done on the project.

A schedule management plan is the base of all the project activities and tasks. It adds the start
and end date of the project and milestones needed to be accomplished for project completion.

Purpose of the Schedule Management Plan

The schedule management plan is made to achieve following purposes:

 To define and present Schedule of the Project.
 To help create Schedule baseline.
 Helps in linking activities and creating network Diagram.
 Helps to identify critical path and critical activities on the project.
 It differs w.r.t timeline, deliverables and resources.

Scheduling Methodology

The scheduling methodology that we would be using for our project is Program Evaluation and
Review Technique (PERT). This would be helpful in identifying three possible time periods
ranging from pessimistic, most likely and optimistic. The mean would be taken and time for each
activity would be estimated using this technique. This would help in defining critical path and
the duration of the project as well as the duration for each activity.

Scheduling Software
The software we are using for managing and scheduling our project is MS Project. This
software will help us in keeping the record of all the tasks and the resources assigned to those
tasks. Keeping in view the resources and their respective tasks, we would be able to efficiently
decide the timeline and schedule of the activities. This would also help to identify the relation
among activities and predecessor and successor activities would be managed and linked
carefully.
This software would help in generating visual representation of our schedule in Gantt Chart,
Network diagram and Schedule Baseline. This would also help in measuring progress and
variances as time passes on the project. Using MS Project, we can also generate cost, resource,
tasks and milestone related detailed reports.

Rules for how Schedule estimates should be stated

 The Project would be Scheduled from the start date of the Project.
 The calendar used on the project would be “Standard Calendar” having 8 working hours
per day and time 8am to 5pm.
 The schedule estimates for each activity should be stated in number of days.
 If there are any leads or lags on the activities, they should be mentioned in the the task
notes.
 The relationships of the activities must be clear and define, the relations among tasks like
start to start, finish to start, start to finish and finish to finish should be considered while
scheduling the activities.
 The whole schedule needs to be made in the initial planning phases as the project follows
the predictive lifecycle approach.

Threshold for Acceptable Variance

The threshold variance for scheduling would be decided based on the critical activities and other
factors such as risks, constraints, opportunities that might affect the schedule of the project. The
acceptable threshold variance would be +_12%, so that if our project gets delayed we have some
contingency to cater with the unforeseen events.

Schedule Baseline

The start date of our project is 1st January, 2022 and the end date is set to be 20th October, 2022.
The total duration of the project is 209 days in the baseline. The visual representation of the
schedule baseline would be made using MS Project.
Performance Measures Used

 Performance would be measured using the Performance measurement baseline and

schedule performance would be compared with the schedule baseline to see the
deviations.
 We would use Earned Value Management (EVM) and Earned Schedule
Management (ESM) to measure progress, we would be calculating the Schedule
variance in terms of cost as well as in terms of time, we would also estimate Schedule
Performance Index SPI to measure schedule performance.
 The milestones marked on the project in MS project task sheet will also help to measure
performance and checking whether the milestone was achieved on time or not.
 Conducting weekly reviews for the unplanned resources requirement as such unforeseen
necessities causes schedule slippage.
 Identification of new risks and managing already identified risks to avoid hurdles.
 Carrying out reviews to identify changes required in scope.
 Getting proper approval for changes so that the schedule can be adjusted accordingly.

Plan for managing Schedule Variance

The schedule would be compared with the baseline after every month to check if the project is
ongoing on time or not, if there is any variance in the project schedule, it would be checked by
the project manager and the root cause analysis would be undertaken and after that a corrective
action would be taken accordingly.
We would use the technique which allows us to estimate the schedule at completion according to
our pre-defined schedule baseline. So, we would have to take corrective measures and reschedule
the future activities in such a way that our end date does not get affected.
The following steps can be included in the plan:
 Tracking and managing the work on regular basis for critical work.
 Last tasks that are not on critical path method shall be completed as soon as possible.
 Keeping transparent communication among all the stakeholders and keeping them
 informed regarding the progress or hurdles being faced.
 Swapping of untrained resources with trained ones.
 Proper management of project, resolving all the hurdles and disagreements to deliver the
 product well within the schedule.
 Tracking, identification and drafting plans for any constraints on the resources or
 deadlines.
 Additional resources may be applied to critical activities for the project to be completed
well within the schedule.
  Clearly monitor, identify, and track technical dependencies.
 Hiring of trained resources and providing necessary training with time to avoid any
 technical hurdle.

A process for determining whether Variance must be acted upon

The Project Manager would look through the root causes and will see if this variance was caused
due to an event that would occur repeatedly or an event such as natural disaster, pandemic, that
was uncontrollable and there are less chance of it during the lifecycle of the project. If there are
chances of repetition of same delays, they must be acted upon.
The Project Manager would also consider the variance threshold while determining whether
variance should be acted upon or not. Stakeholder’s attitude will also be examined.

Identification of Schedule Change Control Procedure

As the Project is based on the Predictive Lifecycle approach, any changes after the baseline has
been set would have to be approved by the Change Control Board. After the Project Manager
would realize the need for change in schedule, a change request would be prepared by the the
team and PM and the reasoning and importance of the changes would be documented and
reviewed, the change request would be sent to the CCB and it would be approved or rejected by
the concerned officers. Depending upon the decision of CCB, the project schedule would be re
planned and the tasks would be done accordingly.

Types of Reports

Project status report

Project Status report will help show the stakeholders that how well a project is advancing
towards its targets. The project status report can be used to give a general update that’s designed
to keep stakeholders or project progress, emerging issues, and key points to note, all at a glance.
It would help to get an idea about the current status of project and its status.
Variance report
A variance report helps the project team and stakeholders to ensure that they stay on track and
does not deviate from their planned schedule, cost and scope. With the help of this report, we
would be able to track the target project milestones and objectives of the project along with the
work that’s getting done. We would also be able to track our tasks on the basis of schedule
variance.

Time tracking report

Time Tracking Report would help the project team & stakeholders see how much time is getting
spent by team members at every step of the project management process. A time tracking report
helps the team to see how much time overall is spent on specific tasks and how much individual
team members spend on tasks.

Team availability reports

The team availability report would act like a team calendar that shows every team member’s
schedule so it’s easy to see who’s occupied and when they are busy. It would help in determining
which resource is over allocated and which is free, so it would help to utilize resources according
to the schedule of the project.

Formatting and Frequency of Reports

The Formatting of Reports would be done according to the templates available in the
Organizational Process Assets OPAs, the Reports would be precise and clear and would be made
by the Checking and Controlling department.
These reports would be generated after 2 months to measure the progress of the project and to
see if the project is on schedule or not.

Contingency Reserves

 Contingencies would be under the control of Project Director and Project Manager would
be responsible for requesting contingencies.
  Application of contingency will remain transparent for all the stakeholders.
 Once the request is approved, contingency will be applied to deal with the schedule
slippage.

List of activities
1. IOT Based Fire Fighting Robot
2. Program Management
3. Data Gathering
4. Survey
5. Experiment
6. Archival research
7. Resource Allocation
8. Time Management Planning
9. Cost Planning
10. Defining Scope
11. Scheduling
12. Determine Dependencies
13. Determining activities duration
14. Monitoring
15. Meet Plan requirement
16. Continue as per Plan
17. Electronics & Control
18. Arduino Nano
19. Buying
20. Program
21. Fitting
22. ESp32 Cam
23. Buying
24. Program
25. Arrange
26. DC Motors
27. Selection
28. Fitting
29. Servo Motors
30. Selecting the right Motor
31. Test Run
32. Fuses
33. Choose the correct rating
34. Design and Manufacturing
35. 4wd Chassis
36. Decide the Chassis
37. Material to be used
38. Testing
 39. Wheels
40. Choose the right type
41. Make fire resistant
42. Test
43. Water tank
44. Size Selection
45. Fitting
46. Submersible Pump
47. Buying
48. Program
49. Test Run
50. Fire Proof Coating
51. System & Technologies
52. Flame Sensor
53. Select the right Sensor
54. Set the range
55. Testing
56. Obstacle Sensor
57. Install at right place
58. Program the sensor
59. Test
60. Mobile Application
61. Select the domain
62. Test
63. Gps Tracker
64. Server Selection
65. Ip setup
66. Program
67. Arduino IDE
68. Software Setup
69. Use to Code to ESP and Arduino
70. Upload code on ESP and Arduino
71. Wi-Fi Module
72. Program the Module
73. Set Range
74. Testing

Schedule Development
Pert Mean duration
Network Diagram
All Activities(Lead ,lag ,baseline)