750 – 1000 words
Apply project scheduling methodologies, including Critical Path Method (CPM), Program Evaluation and Review Technique (PERT), and resource allocation including schedule compression techniques such as crashing, fast-tracking, and scope reduction.
Formulate approaches to control the project cost schedule and performance using Earned Value Management (EVM), scope control, and rebase-lining techniques.
Utilize a Work Breakdown Structure (WBS) and work in MS Project to complete resource assignments for the project schedule and enter cost estimates for all resources.
Your first presentation was excellent, and the project work is moving forward. No project can be managed without a WBS. The CIO now has decided that it is time for you to create the work breakdown structure (WBS) for the project.
This Weeks assignment is a group assignment. It consists of two group activities and two group deliverables. Youre to actively work with your project group to discuss, prepare, and deliver the two group deliverables that must be submitted to the Dropbox by the due date. Students who lag in group participation will be granted points based on their level of engagement with their group and may not earn the same grade as the rest of the group members who were very active.
Group Activity (Part 1)
Use the Small Group Discussion Board to determine the following:
The scope of the project
How is the WBS created? Do you use the PMBOK® Guide project life cycle phases (initiating, planning, executing, monitoring and control, and close out) as the noun or do you use the deliverable or project name as the noun? The noun in a WBS is the deliverable.
The work breakdown structure (WBS) that is representative of the project scope, which should include the following:
Products or services
All major tasks should be organized into work packages. A work-package is the lowest level of the WBS.
Do not decide on estimates for the activities or work-packages at this time.
Group Deliverables (Part 1)
Now that you have had the opportunity to discuss your project and somewhat build your WBS in the group discussion area and offline, use MS project software to complete the following:
Creating your WBS in MS Project. Using MS Project, enter all the WBS deliverables/outputs, activities, and tasks into a new MS Project file and save it with your group name and course #.
Sequence your activities. Now that you have defined your activities, ensure that they are listed in the order that they should be completed. If one activity is dependent on another, be sure to list that dependency in the Predecessor column.
Activity estimation. Assign an initial work effort to each of the activities from the WBS.
Provide an estimation framework for the WBS. This should be approximate. Youre allowed to make assumptions as long youre being realistic.
The framework should be estimated in days.
Duration estimation. Now that you have defined the WBS activities, sequenced them in a logical order and defined the dependency relationships between them, and estimated resources, add the activity duration for all activities then add a start date to each task. The finish date should automatically populate. If you have a conflict, review your predecessor relationships. Remember, you do not need to add anything to the summary tasks (the deliverable/output). The summary tasks will update automatically as soon as you link the activities to them. They summarize the duration and start/finish date for that entire deliverable. The screen shot below should provide you with an example of how your work will look before submitting this assignment. Many more examples are available in the Project Management Homepage in the Learning Center.
Assign resources. In the resource name column in your MS Project file, add a resource name to each task. You may use hypothetical names or your groups names.
Once the work is finalized, submit your estimation framework to your group by adding the finished file to the Small Group area so that everyone has a chance to review the final product. Ideally, the group should select a group leader to manage the groups communication and polish the final work. The group leader should be the one submitting the assignment.
Group Activity (Part 2)
Now that the finished product has been dropped into the group discussion area, each group member should once again review the finished WBS file and provide your insight.
Update the WBS file, if the group agreed changes needed to be made, and individually save the MS Project file on your personal computers because you might need to use it to complete IP4 on your own.
Group Deliverables (Part 2)
Based on your group deliverable (Part 1)
Apply the standard PERT estimating formula and calculate the expected estimate (Te) for each activity.
Download and use this table to complete the estimates.
Explain the purpose behind the PERT calculations.
Group Activity (Part 1)
Each individual member’s contribution to the group discussion for determining WBS essentials should be between 150200 words.
Group Deliverable (Part 1)
There is no length to how many tasks your WBS should be made up of, but it should be long enough to convince your CIO at a glance that this is all the work that needs to be completed for this project. Ideally, you shouldnt have less than 50 tasks. You can organize your tasks however you choose to use the noun. It is recommended that you use the PMBOK® Guide project management phases to organize your WBS.
Group Activity (Part 2)
Each individual member’s contribution to the group discussion for determining work effort and estimation calculations should be between 200300 words.
Group Deliverable (Part 2)
PERT estimate calculations and your explanation of them should be between 550700 words.
At the bottom of this write up document, please indicate the level of engagement for each of your group members. You can use the scale 1-10 where 1 is very low and 10 is very high. For example John Doe – 9. This will help your instructor determine the level of participation for each group member. Group members who did not actively participate in this work will receive zero points and those who contributed little or turned in poor quality work will receive a substantially lower grade from the rest of the group who were active.
MY PORTION OF THE PROJECTEmail Standards & ProtocolsTasks1. create code of conduct for email use2. Set work E-mail hours for employees3. Train users on common “phishing” emails4. train users on common virus emails5. Train users on attachments (when to trust attachments)6. Determine policy on personal email vs. work email7. Set read receipts (if an email is opened can the sender know?)8. Determine “signatures” for E-mailsScenario will be Attached