Description
Hello Buddy. The peer post is due on Friday, while the assignment is due on monday
Unformatted Attachment Preview
Carlos Pinto
Based on my limited experience running programs and projects, I define
a successful project as one that is delivered on time, on budget and
meets all stakeholder expectations, (Watt, Project Management
Overview). Achieving these results is only possible through setting clear
expectations, heavy planning (traditional approaches), flexibility to
change and strong teamwork.
When speaking about project failures, there are many things that can
lead to a project’s demise. By nature, I am an up-front planner and riskassessment person. Starting off the project with the right knowledge,
information and confidence can be a determining factor to success as
well; if the team smells uncertainty, they will lose confidence in the PM
causing a shift in focus and ultimately resulting in failure. Unclear
expectations, unrealistic timelines, poor scheduling, and financial
resource management are also sure-fire ways to make a project fail.
As it relates to HUGE project failures, the P-36 oil platform owned by
Petrobras in Brazil resulted in the loss of eleven lives and environmental
damage: costing over $515M worth of damage. Petrobras company
decided to overlook quality and safety assurance measures in an effort
to increase production, (Watt, Project Management Overview). This
project/event was more than a huge failure. What started out as a
project to increase efficiency and production turned into a catastrophic
event changing the lives of the families who lost their loved ones, but
also of those who lived through the incident and had injuries and
trauma thereafter. Beyond poor project planning and execution, it really
speaks to the culture of the leadership at Petrobras.
Kelly Snead
Since I am being asked to use my one experiences for this week’s
discussion, my experience is as a foreman of a fire protection company
for the last 17 out of 24 years I have been running job sites. I have seen
how a project can be successful and fail from the point of view from the
field personal on the job site. A successful project is defined as a project
that meets its goals and who’s output is a value to the client. Its semes
the success or failure of any project is primarily a faction of its goals.
There are many things that can make or break a project design can
destroy a project there has to be a good design team that makes since if
the drawings are not coronated with the whole project and there has to
have field changes then the job will lose money every time. In this type
of project if there are things left out of the contract like a lift or
scaffolding that’s a failure because if the salesperson does not set some
money aside for things like that and have to get a lift then the job is
already losing money that way. To have a successful running jobsite
there has to have a good plan infect and meet the weekly goals that are
set by the general contractor of the job. Another success point of any
jobsite is ordering material and having that material brought the jobsite
in a timely manner so the work can begin on time. One of the main
unsuccessful or failures of any project is when there are unexpected
changes and the work for that phase has been completed and the
change has been made the work has to be redone that will set a project
on the wrong track.
Vreeland Chambers
In my perspective, a successful project can be defined as one that
adeptly attains its predetermined objectives while adhering to
established constraints. Effective communication, meticulous planning,
and aligning with stakeholder expectations stand out as pivotal
elements contributing to the triumph of a project. Conversely,
unsuccessful projects often emanate from deficient communication
channels, inadequate planning, or a misalignment between project goals
and stakeholder needs. Indicators such as budget overruns, scope
creep, and missed deadlines frequently signal project shortcomings.
Regarding monumental failures, they do indeed merit the label of
unequivocal failures. Consider the example of the Chernobyl nuclear
disaster, which not only represented a technical failure but also resulted
in a catastrophic event with profound implications for human lives and
the environment. Such instances underscore the notion that certain
failures extend beyond mere project management challenges,
encompassing systemic failures, ethical lapses, or inadequacies in risk
assessments. Recognizing these nuances is imperative for deriving
lessons from failures and enhancing overall project management
practices.
Work Breakdown Structure for a Wedding
(Individual project)
Overview
The purpose of this Individual assignment is to develop a WBS (Work Breakdown Structure). NOTE: You
will need Microsoft Project for this assignment. Since this will be an introduction to Microsoft Project,
the scope of the WBS is relatively small.
Assignment for the Wedding WBS
The scenario is this – Your best friend asked you to help plan a wedding in another city. You have no
concern for schedule or budget at the moment, only defining the work that needs to be done for the
wedding to start on time and to be successful. There will be up to 100 guests.
As there are different ways to organize a WBS, you should choose one of the patterns below. This WBS
can be organized by functions or by physical locations, choose just one. Of course, there are other
patterns that could be used but these look like logical choices for this project.
WBS Organized by Location
Level
WBS Organized by Function
WBS Element
Level
WBS Element
0
The wedding project
0
The wedding project
1
Airport arrangements
1
Event programming
1
Guest hotels
1
Guest arrangements
1
Church arrangements
1
Catering
1
Reception arrangements
1
Musical entertainment
1
Wedding outfits
1
Floral displays
1
Going away outfits
1
Wedding outfitting
1
Honeymoon arrangements
1
Transportation
Things to remember:
•
First, change the MS-Project default configuration settings, see the Project Configuration
Settings section in “Project Tutorials” (Course Resources → Microsoft Project).
•
Don’t go overboard on details, i.e., do not go deeper than WBS Level 3.
•
Even though this is a small project, make sure you have enough details, i.e., enough sub-tasks to
show how you will complete the Summary Task deliverable.
•
Do indent sub-tasks, see the Adding Tasks to the Schedule section in “Project Tutorials” (Course
Resources → Microsoft Project).
•
Show the WBS column, see Show the Project WBS Numbers section in “Project Tutorials”
(Course Resources → Microsoft Project).
WBS for a Wedding Spring 2024
Page 1 of 2
Work Breakdown Structure for a Wedding
(Individual project)
•
Follow task naming conventions, see the Week 1 Readings, “How to Build Work Breakdown
Structures”, and “What NOT to do in a WBS”.
o
A sub-task should be named using verb, adjective and noun – there is action performed.
o
A Summary task should be named using noun / adjective structure (NO VERBS) – it
describes what will be delivered instead of what work will be done.
•
No blank rows, i.e.,
•
Summary tasks and sub-tasks should address only one (not multiple) deliverable (or action).
•
Never use full sentences in the Task Name column of the schedule.
IMPORTANT: Submit this file named as “[LastnameFirstname] [Deliverable] Week 1”
EXAMPLE: RowleyGarrett WBS Week 1
Grading Rubric
90-100%
80-89%
70-79%
60-69%
< 60%
Far Above Standards
Above Standards
Meets Standards
Below Standards
Well Below Standards
Criteria
Configuration Settings
Needed for producing
consistent results in the
project schedule
WBS Structure
Includes appropriate level of
decomposition, uses
Project's WBS numbering,
requires indenting sub-tasks,
and continuous rows
Summary Tasks
Uses a specific naming
convention, refers to a single
deliverable, does not read like
a sentence
Sub-Tasks
Uses a specific naming
convention, refers to a single
action, does not read like a
sentence
12 Points
All configuration settings
correct
10.7 Points
9.5 Points
Missed 1-2 configuration
settings
12 Points
10.7 Points
Correctly decomposed the
schedule to Outline Level 3;
Did not leave blank rows in
the schedule; Did not
manually enter WBS numbers
Decomposed too little (to
Outline Level 2), or too much
(to Outline Level 4)
Missed 3-4 configuration
settings
9.5 Points
Over-decomposition (to
Outline Level 5)
8.3 Points
Missed 4-5 configuration
settings
7.1 Points
8.3 Points
7.1 Points
Far too much decomposition,
beyond Outline Level 5
No decomposition at all,
stopped at Outline Level 1;
Left blank rows in the
schedule; Manually entered
WBS numbers
18 Points
16 Points
14.2 Points
12.4 Points
10.6 Points
At least two sources are 1-2
Summary Tasks do not follow
correct naming structure; 1-2
Summary Tasks use full
sentences in the Task Name
column; 1-2 Summary Tasks
encompass multiple
deliverables (should only be
one)
3-4 Summary Tasks do not
follow correct naming
structure; 3-4 Summary
Tasks use full sentences in
the Task Name column; 3-4
Summary Tasks encompass
multiple deliverables (should
only be one)
5-6 Summary Tasks do not
follow correct naming
structure; 5-6 Summary
Tasks use full sentences in
the Task Name column; 5-6
Summary Tasks encompass
multiple deliverables (should
only be one)
7 or more Summary Tasks do
not follow correct naming
structure; 7 or more Summary
Tasks use full sentences in
the Task Name column; 7 or
more Summary Tasks
encompass multiple
deliverables (should only be
one)
18 Points
16 Points
14.2 Points
12.4 Points
10.6 Points
All sub-tasks follow correct
naming structure; Sub-tasks
do not use full sentences in
the Task Name column; Subtasks do not encompass
multiple actions
1-2 sub-tasks do not follow
correct naming structure; 1-2
sub-tasks use full sentences
in the Task Name column; 1-2
sub-tasks encompass
multiple actions (should only
be one)
3-4 sub-tasks do not follow
correct naming structure; 3-4
sub-tasks use full sentences
in the Task Name column; 3-4
sub-tasks encompass
multiple actions (should only
be one)
5-6 sub-tasks do not follow
correct naming structure; 5-6
sub-tasks use full sentences
in the Task Name column; 5-6
sub-tasks encompass
multiple actions (should only
be one)
7 or more sub-tasks do not
follow correct naming
structure; 7 or more subtasks use full sentences in
the Task Name column; 7 or
more sub-tasks encompass
multiple actions (should only
be one)
Page 2 of 2
12
Missed 5 or more
configuration settings
All Summary Tasks follow the
correct naming structure;
Summary Tasks do not use
full sentences in the Task
Name column; Summary
Tasks do not encompass
multiple deliverables
WBS for a Wedding Spring 2024
Possible
Points
12
18
18
Purchase answer to see full
attachment
