For this project you may choose one that is
of interest to you or you may choose to begin planning for your senior project.
When selecting a project, avoid picking one that is either too big or too
small. For example, do not decide to build a new stadium for your local sports
team (too big) or to plant your summer garden (too small).
“The opening of a coffee shop” is my topic
Due Week 2: Project Charter
Due Week 3: Scope Statement
Due Week 4: Work Breakdown Structure and
Network Diagram
Due Week 5: Risk Management Plan
Due Week 6: Resource Management Plan
Due Week 7: Communication Plan
Due Week 8: Final Project Package
Deliverables
Back to Top
Due Week 2: Project Charter
Provide a project charter of your selected
project in accordance with the charter template found in Doc Sharing. The
project will be the project your team will use for the remainder of this
course.
For your new project, please develop a
project team (citing names, e-mail addresses, and telephone numbers).
Be certain to include the following.
Project Objectives
Project Statement of Work
Milestones
All other sections as required in the
project charter
Please put this in proper business writing
format. Consider me to be your boss.
If working in a group, include a statement
of participation, describing how each person contributed to this project
deliverable. Please have each person sign the statement.
Deliverables:
Project charter (in MS Word)
Due Week 3: Scope Statement
Prepare a scope statement using either the
model on pages 144-145 in the text as a template or the scope template in Doc
Sharing. Remember to be tangible, measurable, and specific. Be sure to include
all sections required in the Practitioner section of the Week 2 Lecture.
Deliverables:
Project scope statement (in MS Word)
If working in a group, include a statement
of participation, describing how each person contributed to this project
deliverable. Please have each person sign the statement.
Due Week 4: Work Breakdown Structure and
Network Diagram
According to the PMBOK® Guide, "the
WBS is a deliverable-oriented hierarchical decomposition of the work to be
executed by the project team, to accomplish the project objectives and create
the required deliverables." In other words, it lists the project's tasks,
the subtasks, the sub-subtasks, and so on.
For this phase, you will create a work
breakdown structure (WBS) for the project you selected during phase one.
Remember that the WBS starts with your major deliverables (that you stated in
your scope management plan) at the highest level. The lower levels have the
tasks required to complete those deliverables. You should have at least three
tasks under each deliverable, but you may have as many tasks as needed to
ensure that the deliverables are complete. Review the textbook (and the PMBOK®
Guide, if you have it) for some suggestions on how best to create a WBS. From
your work breakdown structure, develop a project task list with dependencies,
add durations, and then submit a network diagram (using MS Project) and a
project schedule.
Develop the Work Breakdown Structure
Your WBS should have a minimum of 25–30
tasks and be three subtasks deep.
Make sure to use verb-object task names
(for example, "Develop software").
Enter tasks in MS Project.
Create the predecessor relationships to
create a network diagram.
DO NOT LINK SUMMARY TASKS!
In the Gantt Chart Tools tab, check the box
marked Outline Number in the Show/Hide group.
Deliverables:
In MS Project, print the following.
Gantt Chart Entry Table on no more than
three pages [View > Tables > Entry]
Include Task Name, Duration, Start, Finish,
and Predecessor columns with Gantt Chart.
Schedule Table on one page [View >
Tables > Schedule]
Include only the default columns (Task
Mode, Task Name, Start, Finish, Late Start, Late Finish, Free Slack, Total
Slack) and do not include the Gantt Chart. Make sure that all columns are wide
enough to read completely.
Network Diagram on one page [Task tab >
View group > Network Diagram]
Highlight Critical Path and Circle
Milestones.
Justify why you chose your milestones.
(Hint: use milestones from the scope statement or look for key merge or burst
activities.)
Also print out the network diagram on two
to three pages so that task information can be read.
Using the Resource Sheet (View >
Resource Sheet), develop and print a list of resources required for your
project. Include Max.Units and Costs (Std. Rate, Ovt. Rate, Cost/Use).
If working in a group, include a statement
of participation, describing how each person contributed to this project
deliverable. Please have each person sign the statement.
DO NOT ASSIGN RESOURCES AT THIS TIME!
Due Week 5: Risk Management Plan
Establish the project's priority matrix
(constrain, enhance, accept).
Identify a minimum of 10 project risks and
when each will occur in the project life cycle, and then determine their impact
and probability of occurrence.
Create a matrix similar to the one from the
your text (Pinto, Figure 7.5 Classifying Project Risk on page 222), making sure
that it is consistent with your priority matrix, or use the risk management
process in the Practitioner section of Week 3.
Justify the use of your risk scoring matrix
or use the risk management process in the Practitioner section of Week 3.
Assess your risks according to your matrix.
Rank the risks according to their total
risk score.
Prepare the Risk Response Matrix for each
risk—Risk, Response, Contingency, Trigger, Responsible Person—Using the Risk
Management Analysis Template in doc shr
Deliverables:
Use the Risk Management Analysis Template
spreadsheet (risk management analysis template.xls) found in Doc Sharing (there
is a separate tab for each portion of the risk management plan) or use the risk
management process in the Practitioner section of Week 3.
If working in a team, include a statement
of participation, describing how each person contributed to this project
deliverable. Please have each person sign the statement.
Due Week 6: Resource Management Plan
A project plan cannot be considered
complete until the resources have been assigned (including the bottom-up cost
estimate) and leveled, ensuring that the resources are available to complete
the work.
Tasks:
Assign resources to tasks.
Print out the resource sheet.
Identify resources that are over-allocated.
Print the Gantt chart and entry table.
Print reports (or tables) showing the costs
of the resources and the cost by work package. Is this an acceptable cost for
your project? That is, is it within the budget proposed in the scope statement?
Level the project within available slack.
Print the new entry table (do not include
the Gantt chart).
Identify resources that remain
over-allocated.
If resources are still over allocated,
clear leveling and then re-level without the slack constraint.
Identify how this has affected the project
duration (the number of days and the new completion date).
Assume that no other resources are
available. What will your team do to complete the project on time? Instead of
assigning overtime, add a new resource for a cost 1.5 times the normal labor
cost. What is the cost for the additional resource and the total project? Is
this revised cost within the amount developed in the scope statement? If you
choose not to add a resource, your project completion may be delayed. Is a
delay in the project due date acceptable? Why or why not? Submit supporting
documentation from MS Project as needed.
Deliverables:
A journal of project activity. Describe
what you did on each step, and the results of your actions.
MS Project printouts (as above). Please
indicate on the printouts which step they support.
Final time and cost results. Describe how
these meet the needs as defined in the scope statement. If your team believes
that the original scope statement needs to change, describe the changes, why the
changes were necessary, and include the modified scope statement in the
deliverables.
Include a copy of your original (and
revised, if necessary) scope statement with the deliverables.
If working in a team, include a statement
of participation, describing how each person contributed to this project
deliverable. Please have each person sign the statement.
Due Week 7: Communication Plan
According to the PMBOK® Guide, "the
Communications Planning process determines the information and communications
needs of the stakeholders; for example, who needs what information, when they
will need it, how it will be given to them, and by whom." In other words,
it lists the general communication requirements for the project.
This week, you will create a simple communication
plan for the execution of your project. This plan should have the following
information: contact information for all affected parties, major deliverables
and how progress on the deliverables will be communicated to the affected
parties (as well as who the affected parties are and when communication will
take place), and any other miscellaneous information about communication on the
project (see the Communications Plan template in Doc Sharing).
Deliverables:
Business memo summarizing the submission for
the week
Communication plan
If working in a team, include a statement
of participation, describing how each person contributed to this project
deliverable. Please have each person sign the statement.
Due Week 8: Final Project Package
You will need to create a project plan.
This plan should be completely integrated and presented in a logical order. It
should be written professionally and should be mistake-free in terms of
spelling and grammar. The final project plan should incorporate any changes that
occurred along the way, including corrections and advice given by colleagues or
your professor.
Any tables and/or graphs should be labeled
correctly. Your final project plan should consist of the following items.
Table of contents
Project charter
Scope statement
Work breakdown structure
Network diagram
Risk management plan
Resource management plan
Communication management plan
Deliverables:
Project plan consisting of the following
items
Business memo summarizing the submission
for the week
Complete project plan, including the
project charter
Lessons learned document (to be completed
individually, even if the balance of the project was performed as part of a
team)
1. What went well in the project? What
could have gone better?
2. If working in a group
What did you learn from working in a
project group? How did the interpersonal dynamics affect your participation?
If there were conflicts, how were they
resolved?
3. What did you learn in completing this
project about yourself and how you work in a team environment?
4. What could have made this project a
better learning experience?
No comments:
Post a Comment