BUSI 681
Proposed Project Model: Project File Assignment Instructions
Overview
Part 1 of your Proposed Project Model presented essential planning elements for your selected project. Part 2 will build upon these initial plans, allowing you the opportunity to use project management software to build a task list, create a Gantt Chart, input resources, develop a schedule, and plan for certain particulars that are common on many projects. This aspect of the Case Study will help develop your develop your software skills and provide practical application of the concepts we study.
Instructions
The following will be submitted in one MS Project document.
1. Open a new project in Microsoft Project. Save the file in this format: LastName_Project_Name
2. Have the entire project as the first task you input (that is, input the name of your project on the first line). Provide some overarching information about your project. In the Notes file, describe the project and list the key deliverables. Include any other information that may be helpful to your project.
3. Establish a project start date. In the Notes section, explain why you selected this date.
4. Create a work
eakdown structure (WBS) by decomposing the scope for your project into deliverables and enter these as “tasks” in your project file. You must have at least 5 deliverables.
5. Decompose the deliverables further into work packages (tasks) and enter them under your deliverables. It is helpful to keep your deliverables as nouns, and to use ve
s for each task. Include enough detail to have 20–25 unique tasks.
6. Use the “Indent Task” button to create a hierarchy that delineates deliverables and tasks.
7. Code the project following the 1.1, 1.1.1, 1.2 format.
8. Establish the project schedule by estimating time durations for all of your individual tasks. Enter the duration (in days) for each task.
9. Using a task’s Notes feature, justify the time estimates for at least 5 tasks. For example, you might make the following note: “This will take 3 days to allow the paint to dry before applying the trim.”
10. Enter at least 3 milestones for your project. Milestones typically use passive ve
s (i.e. Phase 1 completed) and do not have any duration assigned to them (0 days).
11. Link all of your individual tasks and milestones. You can use the “link” button (appears as a chain link) after selecting the 2 tasks to be linked. Note that there are numerous ways to link tasks. Vary your linkages by including at least 2 relationships that are not Microsoft Project’s default (Finish-to-Start) relationships.
12. Not all tasks start immediately after a task ends (they “lag”) or wait until a task is completely finished before starting (they “lead”). Therefore, have at least 1 task include lead time or lag time. In the Notes section for this task, indicate why there would be a lead/lag for that particular task.
13. Next, begin to assign workers and estimate your resource costs. Enter at least 6 human resources on the Resource Sheet.
14. Add comments to at least half of your resources to provide information about those resources. Note things such as why they were selected, potential scheduling issues, a potential back-up, or other information that a project manager might find helpful.
15. In order to determine the budget for your project, you must input your labor costs. After your resources are entered, include wage rates for each individual resource.
16. For every task, assign the appropriate resource(s). Do not assign resources to summary tasks (your deliverables) or milestones (event markers).
17. If Microsoft Project displays a red human resource icon, the associated resource is over-allocated. Determine how best to address the problem and make the needed changes. If a resource can be over-allocated, justify the “why” in the task’s Notes.
18. When tasks, costs, and resources are entered co
ectly and you have double-checked for accuracy, set the project baseline. This sets the budget and schedule for the project.
19. Next, display the project as a network diagram to show the critical path in your project.
20. Save and submit the document.
Note: Your assignment will be checked for originality via the Turnitin plagiarism tool.
Page 2 of 2
BUSI 681
Page
1
of
2
P
ROPOSED
P
ROJECT
M
ODEL
:
P
ROJECT
F
ILE
A
SSIGNMENT
I
NSTRUCTIONS
O
VERVIEW
Part 1 of your
Proposed Project Model
presented essential planning elements for your selected
project. Part 2 will build upon these initial plans, allowing you the opportunity to use project
management software to build a task list, create a Gantt Chart, input resources, develop a
schedule, a
nd plan for certain particulars that are common on many projects. This aspect of the
Case Study will help develop your
develop your
software skills
and provide practical application
of the concepts we study
.
I
NSTRUCTIONS
The following will be submitted in
one
MS Project document.
1.
Open a new project in Microsoft Project. Save the file in this format:
LastName_Project_Name
2.
Have the entire project as the first task you input (that is, input the name of your
project on the fi
st line). Provide some overarching information about your
project. In the Notes file, describe the project and list the key deliverables. Include
any other information that may be helpful to your project.
3.
Establish a project start date. In the Notes secti
on, explain why you selected this
date.
4.
Create a work
eakdown structure (WBS) by decomposing the scope for your
project into deliverables and enter these as “tasks” in your project file. You must
have at least 5 deliverables.
5.
Decompose the deliverables f
urther into work packages (tasks) and enter them
under your deliverables. It is helpful to keep your deliverables as nouns, and to
use ve
s for each task. Include enough detail to have 20
–
25 unique tasks.
6.
Use the “Indent Task” button to create a hierarchy
that delineates deliverables and
tasks.
7.
Code the project following the 1.1, 1.1.1, 1.2 format.
8.
Establish the project schedule by estimating time durations for all of your
individual tasks. Enter the duration (in days) for each task.
9.
Using a task’s Notes f
eature, justify the time estimates for at least 5 tasks. For
example, you might make the following note: “This will take 3 days to allow the
paint to dry before applying the trim.”
10.
Enter at least 3 milestones for your project. Milestones typically use pass
ive ve
s
(i.e. Phase 1 completed) and do not have any duration assigned to them (0 days).
11.
Link all of your individual tasks and milestones. You can use the “link” button
(appears as a chain link) after selecting the 2 tasks to be linked. Note that there a
e
numerous ways to link tasks. Vary your linkages by including at least 2
elationships that are not Microsoft Project’s default (Finish
-
to
-
Start)
elationships.
12.
Not all tasks start immediately after a task ends (they “lag”) or wait until a task is
comple
tely finished before starting (they “lead”). Therefore, have at least 1 task
include lead time or lag time. In the Notes section for this task, indicate why there
would be a lead/lag for that particular task.
BUSI 681
Page 1 of 2
PROPOSED PROJECT MODEL: PROJECT FILE ASSIGNMENT INSTRUCTIONS
OVERVIEW
Part 1 of your Proposed Project Model presented essential planning elements for your selected
project. Part 2 will build upon these initial plans, allowing you the opportunity to use project
management software to build a task list, create a Gantt Chart, input resources, develop a
schedule, and plan for certain particulars that are common on many projects. This aspect of the
Case Study will help develop your develop your software skills and provide practical application
of the concepts we study.
INSTRUCTIONS
The following will be submitted in one MS Project document.
1. Open a new project in Microsoft Project. Save the file in this format:
LastName_Project_Name
2. Have the entire project as the first task you input (that is, input the name of your
project on the first line). Provide some overarching information about your
project. In the Notes file, describe the project and list the key deliverables. Include
any other information that may be helpful to your project.
3. Establish a project start date. In the Notes section, explain why you selected this
date.
4. Create a work
eakdown structure (WBS) by decomposing the scope for your
project into deliverables and enter these as “tasks” in your project file. You must
have at least 5 deliverables.
5. Decompose the deliverables further into work packages (tasks) and enter them
under your deliverables. It is helpful to keep your deliverables as nouns, and to
use ve
s for each task. Include enough detail to have 20–25 unique tasks.
6. Use the “Indent Task” button to create a hierarchy that delineates deliverables and
tasks.
7. Code the project following the 1.1, 1.1.1, 1.2 format.
8. Establish the project schedule by estimating time durations for all of your
individual tasks. Enter the duration (in days) for each task.
9. Using a task’s Notes feature, justify the time estimates for at least 5 tasks. For
example, you might make the following note: “This will take 3 days to allow the
paint to dry before applying the trim.”
10. Enter at least 3 milestones for your project. Milestones typically use passive ve
s
(i.e. Phase 1 completed) and do not have any duration assigned to them (0 days).
11. Link all of your individual tasks and milestones. You can use the “link” button
(appears as a chain link) after selecting the 2 tasks to be linked. Note that there are
numerous ways to link tasks. Vary your linkages by including at least 2
elationships that are not Microsoft Project’s default (Finish-to-Start)
elationships.
12. Not all tasks start immediately after a task ends (they “lag”) or wait until a task is
completely finished before starting (they “lead”). Therefore, have at least 1 task
include lead time or lag time. In the Notes section for this task, indicate why there
would be a lead/lag for that particular task.