The “Backstage” view in Microsoft Project

Revision suggestion:

2. Use the file Properties from the “Backstage” view in Microsoft Project to enter a brief description of the project objectives in the Comments field. Remember, project objectives must be SMART. Complete the other Properties as appropriate. (Hint: Go to File>Info>Project Information>Advanced Properties>Comments). (1/2 points) Project objectives should be more complete and “SMARTer”.
3. From the Gantt chart view, with the Entry Table applied, enter 20 deliverables for your project in the Task Name column, including project management. Remember, typically, a deliverable is a component part of the project and is expressed as a noun/adjective – NOT a verb (Hint: see PMBOK ® fifth edition pages 158, 159, and 160 as examples). It is acceptable to break down your project into phases, and then deliverables and sub-deliverables. (6/7 points). You should always start with the overall project as the top line/level 1 in your WBS in MS Project.
4. Breakdown the work packages into project activities. Note that unlike deliverables, activities are the actual actions you need to perform to complete the deliverables/work packages or phases. Activities are expressed as verb phrases. If you need a hint, review the lecture on schedule management. (2/5 points You did not include activities (verb noun) in all deliverables. For example, these are activities that you should have included: ”Install Electrical”, “Paint Walls”, “Cure Roofing”, “Plaster Interior” etc.
5. Use the “Indent/Outdent Task” command from the Task tab in Microsoft Project to create a hierarchy of deliverables/work packages/activities. This hierarchy will help you plan better your project. (1 point) 7. Use the default WBS coding system in MS Project to code your WBS. (Hint: From the Format tab> Outline Number). (.5/1 point). You did not include the default MS Project coding (insert column for WBS) – instead, you typed WBS codes into major deliverables.
6. Make all revisions as suggested when I reviewed your previous lab submission. Do not re-submit your file with the same mistakes as this will affect your score.
7. Set the start date of your project to coincide with the start date of the class and switch all your project activities to Auto Schedule (1point).
8. Estimate and enter durations for all your project activities. As you are estimating activity duration, keep in mind the skill level required to perform the task and resource availability (2points).
9. Add task notes to at least 2 of your project activities to document your estimating techniques. For example, did you use PERT estimate, learning curve, expert judgment, or historical data? Why? (Hint: you can enter and review task notes on the Notes tab in the Task Information dialog box). (2points).
10. Add at least 3 milestones to your project wherever you feel they are most appropriate. (Hint: a milestone is an activity with zero cost and zero duration used in the schedule to indicate significant events reached within the plan or imposed on the plan – e.g., design complete or permit received. (4points).
11. Add task relationships to all of your project activities and milestones. If you did not add milestones to your schedule, it is now time to do so. Do not link summary task or work packages – only activities and milestones. However, if you did not breakdown a work package into activities, then it should have a predecessor and a successor. Make sure that all activities have a predecessor, except the first one; and make sure that all activities have a successor, except the last one (4 points).
12. Add a start-to-start relationship between any 2 pairs of project activities that you think should be planned with a start-to-start relationship (e.g., activities 6 and 7; and activities 15 and 16). Add a Task note to explain why you believe these activities should be done in parallel instead of in sequence. Add a finish-to-finish relationship to two project activities. Add a Task note to explain why you believe these activities should be planned this way (1point).
13. Add lead-time to at least one task relationship. (Hint: in MS Project, a lead-time is entered as a negative lag) (1point).
14. Add lag time to at least one task relationship. (1point)
15. Add a constraint to one activity - for any task that has been constrained, add a comment to explain why it is constrained. (1point)
16. Add a deadline reminder to at least one task or milestone. (1point)
17. Display the critical path of your project schedule and make sure that some of your activities have slack time – that is, not all your activities are in the critical path. (1points)
18. Display your project in a Network Diagram view and save it so that it automatically opens in that view (1point)