Planning process part 2:

Outcome: project schedule + diagramize it

The Work Breakdown Structure is a deliverable oriented hierarchy that defines all the
work of the project. It is a tool that graphically display the deliverables in a
hierarchical fashion and organize the work of the project into logical groupings.
Scope creep: A phenomenon where the project scope changes over time due to lack
of agreement on original scope statement or not having a scope statement.
A work breakdown structure is similar to an organization chart, where you start with
the big picture and each successive level gets more and more detailed. The key is to
get the work breakdown structure to a point where the components in the lowest
level are easily estimated, scheduled and assigned. Level 1: name of project and
least level: Work package [The work package level is where time estimates, cost
estimates and resource estimates are determined.]
Each WBS element is uniquely identified by a code or number. These codes are
used to track the cost of each of element in the WBS, as well as serve as reference
numbers to other planning information.
For small projects we can do an outline instead of tree form.
Step 2: Define tasks and activities:

- Activities are a single piece of work that must be completed to satisfy

the requirement of a project deliverable. [work package] the work is
subdivided into small units that are easily assigned to one team or a
group of team members.
- After defining the activities, you must sequence them in a logical order to
assist later in the preparation of the project schedule
Step 3: Milestones are markers along the way in a project that let you know that a
significant accomplishment has been reached. Seen on milestone chart or grant
chart
Step 4: A responsibility assignment matrix (RAM) is a chart that ties roles and
responsibilities to the work breakdown structure (WBS) elements. Other format is
RACI: R for Responsible for performing the work, A for Accountable, C for Consult
and I for Inform
Step 5: you will need to estimate the duration of each activity. There are several
techniques for determining duration estimates, including expert judgment and
parametric Estimating:
- Expert judgement: asking people with skill
- Parametric estimating: applying calculation on known values
Step 6: determine dependencies, put the tasks in logical order.
There are four types of dependency relationships: finish to start (finish indepen then
start dependent), finish to finish(indepen finish before dep finishes ), start to
start(independent start before dependent) and start to finish( indepen before
dependent finishes)
Step 7: A network diagram shows the activities of the project in the order they will
perform, and is a great graphic to hang in the project team meeting room to show
progress examples:
- Precedence diagramming links project activities according to their
dependency, using boxes or nodes to depict project activities, and arrows to
show dependencies. It takes into account when one task cannot be started
until a previous activity finishes.
- Activity on Node (AON) is a type of precedence diagramming method that
uses circles to depict tasks and uses arrows to show dependencies between
activities.