MS Project Practical Checklist

This MS Project Practical Checklist outlines a series of tasks for students to complete using the MS Project software. The tasks are divided into three practical exercises, covering project information setup, adding duration and relationships, and resource management. Each exercise includes specific instructions and prompts for completing tasks, such as setting project titles, entering durations, defining predecessors, assigning resources, and analyzing critical paths and slack times. Students are required to demonstrate their understanding of MS Project features and functionality by providing screenshots of their network diagrams, answering questions about the project timeline, resource allocation, and critical path analysis.

MS-Project Practicals Checklist
Student ID: ___________ Student Name: _____________________________
Practical-1
Item Status Description
1 Project Information
i. Change the start date 
ii. Change Title & Author 
iii. Enter Holidays 
iv. WBS entered 
v. Set Project Title as 0
task

Practical-2
Item Status Description
2 Adding Duration & relationships
i. Durations entered 
ii. Predecessors entered 
iii. Inserting lags 
iv. What are the types of lags Positive lags
v. What do the different
types of relationships
mean?
The activities of the project are related to each
other in terms of duration. The relations of the
activities are Finish to Start , Earlier Start, Late
Start, Not before than, and After completion
vi. Milestones added  One milestone has been added
vii. Displaying Critical Path  It has been displayed as red in the schedule
viii. How many CP(s) in this
project
07
ix. What is the slack for non-
critical tasks
23
x. What does the CP suggest
about the sensitivity of the
network?
The CP suggest that the project can be completed
by following that path.
xi. Answered FS and TS 
xii. Screenshot of Network
diagram

Practical-3
Item Status Description
2 Adding Resources
i. Resource pool created 

ii. Resources assigned 
iii. End date of project
recorded
 Fri 04-05-18
iv. Total duration of project 90 days
v. Resource levelling
completed

vi. Answer ‘Slack for Database
design and changes’
 15
vii. What are tasks are critical 1.1 Information gathering
1.2 Define Requirements
3.2.1 Design Programs
3.2.2 Program A
3.2.2.1 Code program A
3.2.2.2 Unit test A
3.2.3 Program B
3.2.3.1 Code program B
3.2.3.2 Unit test B
3.2.4 Program C
3.2.4.1 Code program C
3.2.4.2 Unit test C
3.2.5 Program D
3.2.5.1 Code program D
3.2.5.2 Unit test D
3.2.6 Program R1
3.2.6.1 Code program R1
3.2.6.2 Unit test R1
4 Integration
4.1 Integrate
4.2 Test
viii. New end date and duration Fri 11-05-18 and 105 days
ix. Status of changes made  Completed
x. Resource Levelling options
changed and ‘Level All’
performed

xi. New changes after ‘Level
All’
The over allocation issue with resource “Analyst”
has been resolved.
xii. Is there still a resource
allocation problem?
Yes
xiii. Are they over-allocated “Programmer” and “Tester” is still over allocated.
xiv. Any change in Duration?
How much?
No
xv. What has happened to the
critical tasks?
Changed and decreased in number by 2
xvi. When does the project
finish now?
Fri 11-05-18
xvii. What the project start date
now?
Mon 08-01-18
xviii. What is the total cost
estimate?
$96,211.54
xix. What is the most
expensive task?
3. Software Modifications

xx. What is the total amount
estimated to be spent on
programming staff in this
project?
$24,615.38