Chapter 5: Project Planing -> Schedule & cost management Flashcards
Project Schedule Management Processes (Predictive Approach)
1) Planning schedule management: (What do we need to do here?)
2) Defining the activities: (What is it relating to?)
3) Sequencing the activities: (In which order?)
4) Estimating activity resources: (What do we need to get it done?)
5) Estimating activity duration: (How long will it take?)
6) Developing the schedule: (How does it look over time?)
7) Controlling the schedule: (Recurringly: Are we still good to go?)
Defining activities
-Activity list
-Activity attributes
-Milestone list
-Change requests
-Project management plan updates
Creating the Activity List and Attributes
*The activity list is a tabulation of activities to be included on a project schedule
*It should include the activity name, an activity identifier or number, and a brief description of the activity
*The activity attributes provide schedule-related information about each activity, such as predecessors, successors, logical relationships, leads and lags, resource requirements, constraints, imposed dates, and assumptions related to the activity
*Both should be in agreement with the WBS and WBS dictionary and be reviewed by key project stakeholders
Milestones
*A milestone is a significant point or event in a project
*It often takes several activities and a lot of work to complete a milestone, but the milestone itself is like a marker to help identify necessary activities
*There is usually no cost or duration for a milestone
*Project sponsors and senior managers often focus on major milestones when reviewing projects
*Sample milestones for many key projects include
-Sign-off key documents
-Completion of specific products
-Completion of important process-related
work, such as awarding a contract to a
supplier
Sequencing activities
*Sequencing activities involve evaluating the dependencies (or relationships) between activities, for example:
-Does a certain activity have to be finished
before another can start?
-Can the project team do several activities in
parallel?
-Can some activities overlap?
*You must determine dependencies in order to use critical path analysis
Activities on Arrow Network Diagram (AOA)
*Activities are represented by arrows
*Circles are the starting and ending points of
activities
*Network diagram represents activities that
must be done to complete the project
*Every activity on the network diagram must be
completed for the project to finish
*Not every items on the WBS needs to be on
the network diagram; only activities with
dependencies need to be shown on the
diagram
Precedence Diagramming Method (PDM)
*Activities are represented by boxes
*Arrows show relationships between activities
*More popular than AOA method and used by
project management software
*Better at showing different types of
depedencies
Precedence Diagramming Method (PDM)
*Activities are represented by boxes
*Arrows show relationships between activities
*More popular than the AOA method and used
by project management software
*Better at showing different types of
dependencies
Task dependencies
*Finish-to-start dependency: Task B cannot
start until task A finishes
*Start-to-start dependency: Task B cannot start
until task A starts
*Finish-to-finish dependency: Task B cannot
finish until A finishes
*Start-to-finish dependency: Task A cannot
finish until task A starts
Finish-to-start dependency
*A relationship in which the “from” activity or predecessor must finish before the “to”
activity or successor can start.
*For example, you cannot provide user training until after software or a new system has been installed. Finish-to-start is the most common type of relationship or dependency, and AOA network diagrams use only finish-to-start dependencies
Start-to-start dependency
*A relationship in which the “from” activity cannot start until the “to” activity or successor is started.
*For example, in a media campaign, a group of activities might start simultaneously, such as Social Media / Internet postings, TV adds and Radio commercials
Finish-to-finish dependency
*A relationship in which the “from” activity must be finished before the “to” activity can
be finished. One task cannot finish before another finishes.
*For example, quality control efforts cannot finish before
production finishes, although the two activities can be performed at the same time.
Start-to-finish dependency
*A relationship in which the “from” activity must start before the “to” activity can be
finished. This type of relationship is rarely used, but it is appropriate in some cases.
*For example, an organization might strive to stock raw materials just in time for the manufacturing process to begin. A delay in starting the manufacturing process should delay completion of stocking the raw materials. Another example would be a babysitter who wants to finish watching a young child but is dependent on the parent’s arrival. The parent must show up or “start” before the babysitter can finish the task
Estimating activity resources
*Before estimating activity durations, you must have a good idea of the quantity and type of resources that will be assigned to each activity; resources are people, equipment & materials.
*Consider important issues in estimating resources
-How difficult will it be to do specific activities
on this project?
-What is the organization’s history in doing
similar activities?
-Are the required resources available?
*A resource breakdown structure is a
hierarchical structure that identifies the
project’s resources by category and type
Estimating activity duration
*Duration includes the actual amount of time worked on an activity plus elapsed time
*Effort is the number of workdays or work hours required to complete a task
*Effort does not normally equal duration
*Example: I will spend 20 hours reading a book (effort) spread over a period of 2 months (duration)
*People doing the work should help creates estimates and an expert should review them