Assignment for the ITP-3 Project Deliverables

Posted by:. Posted on:Jul 12,2016

Assignment for the ITP-3 Project Deliverables

<img src=”http://adobehub.com/wp-content/uploads/2016/07/stars-desktop.png” alt=”some_text”>

[su_button url=”https://coursefortune.com/order”]ORDER THIS PAPER[/su_button]

Review your previous assignment deliverables before proceeding with this assignment. This assignment has two parts – an MS Project file (.mpp) and an MS Word file.

Adding dependencies to the WBS – Part 1

  • The team will determine the appropriate method for consolidating the individual WBSes into a single WBS.  For instance, after review of all team members’ WBSs, the best WBS could be adopted, portions of different team members’ WBSs could be used, the best features of different team members’ WBSs could be used, it could all be scrapped and collaboratively re-built from scratch, or any number of other methods could be used.
  • The team’s WBS should be fleshed out (meaning enough decomposition to be able to see a major task and all the work associated with it).  As a team, make any corrections and updates necessary to the consolidated/integrated team WBS before adding the dependency links.  The schedule should include time/duration for all lowest level leaf-node tasks (sub-sub tasks or work packages).  MS Project will roll-up the durations and calculate them automatically for summary roll-up groups.  Durations should include hours, days, and weeks of time posted in the Gantt view.
  • Then, the team members will add predecessor-successor linkages for all tasks within the consolidated team WBS.  This is the ORDER in which tasks must be performed. Every task should have a dependency “relationship” (either a predecessor or a successor) to another task.
    • The default in Microsoft Project is a “finish-to-start” relationship (task A must be completed before task B can start)
    • Not all tasks have to be 100% completed before another task can start (task A only needs to be 25% completed when task B could start; or task A and task B could start at the same time).
    • For example, to use our previous example, we could be selecting paint colors at the same time we are preparing the bathroom.  We could be taping the edges and then filling holes at the same time we are buying paint. But we CAN’T paint the walls without purchasing the paint – so purchasing the paint is a predecessor to painting the walls.
  • Again, each member of the team should go through the WBS as a whole to flesh out areas that may not be addressed with tasks.  For example, if one member is assigned the major task of purchasing paint and supplies, but another member notices that tarps and furniture covers are not included, that member would work with the team to add the associated tasks, durations and predecessors.
  • As a team, look at the NETWORK View in Microsoft Project.  All tasks should have some linkage to other tasks.  There should be no tasks “standing alone.”  There should be no tasks without predecessors or successors except for the project start task.  There should be multiple paths and the paths should flow generally from left to right toward the final task, which should be the last task to the right with no subsequent tasks.  The final task should be the defined end of the project.
  • As with previous ITP deliverables, DO NOT enter hard-coded dates.  Just enter durations at the lowest level tasks and let MS Project calculate the dates. If your “I” column has a little calendar – you have not done this correctly.
  • Do not use “manually scheduled” tasks.  Rather, use “automatically scheduled” tasks.  When manually scheduled, the dates are essentially hard-coded and not allowed to automatically adjust when the task durations and critical paths change.
  • The higher level tasks are group summary “roll up” tasks and should have no work themselves.  Don’t enter a duration for these tasks.  Their timespan will be automatically calculated by MS Project as the sum of the timespans of their component sub-tasks based on the algorithm.
  • When done, save a baselined project schedule as described in the textbook, or the various MSP tutorials, or
  • The Gantt Chart View and the Network View should not look like waterfalls, wherein each task has only one predecessor and only one successor.  That is not only unrealistic, but is problematic for most projects.  There should be parallelism.  This means that typical tasks should have multiple successors and/or predecessors.

 

  • Please ensure that your MS Project (.mpp) file includes at least the following fields (columns) visible in the left-hand table portion of the Gantt chart view or the Tracking Gantt view:

 

    • All fields from ITP-2i
    • Start date  [a default field]
    • Finish date  [a default field]
    • Predecessors [a default field]
    • Successors
    • Additionally, please ensure that the Critical Tasks box in the Format tab is checked.

 

When done, save a baselined project schedule as described in the various MSP tutorials. Submit the MS Project (.mpp) file with your name in the file name.

 

Text document – Part 2

http://polaris.umuc.edu/~kschank/MS-Project-Skills-Baselining.htm.

In a Word document, include a cover sheet that includes contributors, the executive summary, and text that describes your team efforts and decisions made.  Answer the following questions in a text document:

  1. Did your team discuss and/or divide up the major tasks before completing the INDIVIDUAL WBSes?
  2. How did your team “merge” the WBSes of individual teammates?
  3. Were some teammates’ WBSes more thorough or complete than others?
  4. What was the most difficult part of this assignment?
  5. Did every teammate contribute to this WBS effort?
  6. Is your team still following the day-to-day schedule provided in the TPP-1?

Approximate breakdown by areas include:

  • General: Structure, Format, Mechanics, Style (~4%)
  • Schedule WBS (~10%)
  • Schedule linkages (~60%)
  • Network view (~26%)

 

Rubrics and Grading for the ITP-3 Project Deliverable

To earn 90-100% of the points available for this assignment –

The project has a title line.  The start of the project is a lowest-level leaf node task (work package) with no sub-tasks and no predecessors.  The end of the project is a lowest-level leaf node task (work package) with no sub-tasks and no successor.  The TEAM WBS should have predecessors for all tasks (work packages) (except the project start task), and should have successors for all lowest-level leaf node tasks (work packages) (except the project end task).  Several tasks are types of predecessors different from the finish-to-start default. Working times/durations have been assigned to ALL of the tasks, Notes is used to address extra information that will be used by the team during the project, and at least two other features of Microsoft Project have been used and discussed in the text document.  There are no hard-coded or manually-scheduled dates.  Summary roll-up groups should have predecessors or successors and no hard-coded durations; all summary group durations should be calculated by MS Project.  More than 5 milestones/decision points are included and at least 3 recurring tasks are included.  No unusual date constraints or linkage types are used.

The NETWORK VIEW should show tasks in multiple paths (meaning tasks are not limited to being done sequentially), and all of the paths should flow from left to right with all paths ending at or leading to the final task, which is on the far right of the Network View.   Most of the paths are blue (non-critical); one or more paths from start to finish are red (critical paths).  No tasks stand alone in the Network View.

The textbook and at least 2 additional (credible) sources are used to help develop the project, references are from academically credible; a Reference Page and discussion of how the sources and/or were used to add to the textbook and WBS are included as a Reference Page with the cover page.  “Dangerous” MS Project features are not used.

To earn 80-89% of the points available for this assignment –

The project has a title line.  The start of the project is a lowest-level leaf node task (work package) with no sub-tasks and no predecessors.  The end of the project is a lowest-level leaf node task (work package) with no sub-tasks and no successor.  The TEAM WBS should have predecessors for all leaf node tasks (except the project start task), and should have successors for all tasks (except the project end task).    Working times/durations have been assigned to ALL tasks, Notes is used to address extra information that will be used by the team during the project, and at least one other feature of Microsoft Project has been used and discussed in the text document. There are no more than 3 hard-coded or manually-scheduled dates.  Summary roll-up groups should have predecessors or successors and no hard-coded durations; all summary group durations should be calculated by MS Project.  More than 2 two milestones/decision points are included and at least 2 recurring tasks are included.  No more than 3 unusual date constraints or linkage types are used.

The NETWORK VIEW should show tasks in multiple paths (meaning tasks are not limited to being done sequentially), and all of the paths should flow from left to right with all paths ending at or leading to the final task, which is on the far right of the Network View.   Most of the paths are blue (non-critical); one or more paths from start to finish are red (critical paths).  No more than 3 tasks stand alone or lack predecessors or successors in the Network View.

In addition, at least two sources are used (the textbook and 1 credible source) to help develop the project. References are from academically credible sources and/or the textbook and include text, explaining how the textbook was used, with a Reference Page and the cover page.  “Dangerous” MS Project features are not used.

To earn 70-79% of the points available for this assignment –

The start of the project is a lowest-level leaf node task (work package) with no sub-tasks and no predecessors.  The end of the project is a lowest-level leaf node task (work package) with no sub-tasks and no successor.  The TEAM WBS should have predecessors for at most 7 lowest-level leaf node tasks (work packages) (except the project start task), and should have successors for all tasks (work packages) (except the project start task), and should have successors for at most 7 lowest-level leaf node tasks (work packages) (except the project end task). 7 or fewer tasks have no relationships.  Working times have been assigned to the tasks.  There are no more than 7 hard-coded or manually-scheduled dates.  Summary roll-up groups should have predecessors or successors and no hard-coded durations; all summary group durations should be calculated by MS Project.  At least 1 milestones (milestone/decision point) is included and at least 1 recurring task is included.  No more than 7 unusual date constraints or linkage types are used.

The NETWORK VIEW should show tasks in multiple paths (meaning tasks are not limited to being done sequentially), and all but a single or almost single horizontal path flowing from left to right is acceptable.  The paths should flow from left to right with all paths ending at or leading to the final task, which is on the far right of the Network View.   Most of the paths are blue (non-critical); at least one path is red (critical paths).  No tasks stand alone in the Network View.  No more than 7 tasks stand alone or lack predecessors or successors in the Network View.  The textbook is used and cited.

To earn 60-69% of the points available for this assignment –

The group WBS should have predecessors for ALL tasks (except the first major task) at ALL levels. Predecessors are assigned to ALL tasks (except the first major task) at all levels.  In the Network View, the paths flow toward the final task which is at the far right of the Network View.  Most paths are blue.  No major tasks stand alone and no more than 10 lower level tasks stand alone.

Less than 60% –

Team efforts that do not meet the requirements will earn a zero.  Team efforts that are not original work will earn a zero.  Team efforts that do not have proper APA references and citations to any included or quoted work will earn at most 50%.

Please notice that there is a STRONG incentive for ALL team members to carefully proofread team documents before submitting.  This incentive will continue through the semester.

[su_button url=”https://coursefortune.com/order”]ORDER THIS PAPER[/su_button]


.

No description.Please update your profile.