MELJUN CORTES JEDI Slides-7.4 Project Scheduling

7/29/2019 MELJUN CORTES JEDI Slides-7.4 Project Scheduling

1/16

Software Engineering 1

Basic Software Project

Management

ProjectScheduling

TOPIC FOUR


2/16


It enumerates phases and stages of the projects, breakseach into discrete tasks or activities to be done, portrays theinteractions among these pieces of work and estimates thetime that each task or activity will take.

It is a time-phased sequencing of activities subject toprecedence relationships, time constraints, and resourcelimitations to accomplish specific goals or objectives.

Project Scheduling


3/16


Project Scheduling Principles

Compartmentalization.

The product and process are decomposed into manageableactivities and tasks.

Interdependency. The interdependency of each compartmentalized activity or task

must be determined. Tasks can occur in sequence or parallel.Tasks can occur independently.

Time Allocation.

Each task should be allocated some number of work unit (person-days or man-days of effort). Each task must have a start and enddate subject to interdependency and people responsible for the task(part-time or full-time).


4/16


Project Scheduling Principles

Effort Validation.

No more than the allocated number of people has been allocated atany given time.

Define Responsibility. Each task must have an owner. It should be a team member.

Define Outcome.

Each task must have a defined outcome. Work products arecombined in deliverables.

Define Milestones.

Each task or group of tasks should be associated with a projectmilestone. Project milestones are reviewed for quality andapproved by project sponsor.


5/16


Project Scheduling

Activities or Task Set.

It is a collection of software engineering work tasks, milestones anddeliverables that must be accomplished to complete a particularproject. It is part of a project that takes place over a period of time.

It is written as a verb-noun phrase. Milestones.

It is an indication that something has been completed. It references aparticular moment of time. It signifies points of accomplishments withinthe project schedule. It is not duration of work. Examples of project

milestones are user sign-off, approved system design, and systemturnover.


6/16


Project Scheduling

Deliverables.

It is a list of items that a customer expects to see during thedevelopment of the project. It can include documents,demonstrations of functions, demonstrations of subsystems,

demonstrations of accuracy and demonstration of reliability, securityor speed.


7/16


Project Work Breakdown

Structure It is a tool that allows project managers to define task sets,

milestones and deliverables.

It is a systematic analysis approach of depicting a project as

a set of discrete pieces of work. Two Methods

Work Breakdown Analysis

WBS Top-down and Bottom-up Integration Process


8/16



Break the project into blocks of related activities.

Arrange the blocks into a logical hierarchy.

Analysis starts by identifying the major phases and the major

deliverables that each produces. For each activity, break them to define sub-activities and the work

products produced by these sub-activities.

Continue to subdivide an activity until you get to an activity thatcannot be subdivided anymore. This atomic activity is called thework unit or package.


9/16



Define the Work Unit or Package. The work unit orpackage is the responsibility of one person. It should beexecuted until it finishes without any interruption. Itsduration and cost can be measured, and requires the

continuous use of a resource group.


10/16


WBS Top-down and Bottom-

up Integration Process Top-down Decomposition Identify 4-7 major components of work. Do not worry about the

sequence.

Identify intermediate and final deliverables for each grouping.

Perform functional decomposition until a task has one owner, cleardeliverables, credible estimates and can be tracked.

Use verb-object at lowest task level. Recommended number oflevels is four (4).

Multiple iterations are required.


11/16


WBS Top-down and Bottom-

up Integration Process Bottom-up Integration Brainstorm all possible tasks.

Organize task into 4-7 major groupings reflecting how the project willbe managed.


12/16


WBS Format

Graphical or Hierarchical

Outline

GANTT Chart


13/16


Graphical or HierarchicalPre-jointMeeting

Write the

productrequest.

Set pre-

jointMeeting.

Invite

participants.

Distribute

productrequest to allparticipants.

Set Timeand Date

Set Place. IdentifyFacilitator andParticipants.


14/16


Outline

I. Pre-joint Meeting Task

I. Write product request.

II.Set pre-joint meeting.

a)Set time and date.b)Set place.

III.Identify facilitator and participants

IV.Invite participants

V.Distribute product request to all pa


15/16


GANTT Chart

1 2 3 4 5 6

1. Pre-joint Meeting Task

1.1 Write product request.

1.2 Set pre-joint meeting.

1.2.1 Set time and date.

1.2.2 Set place.

1.2.3 Identify facilitator and participants.

1.3 Invite participants.

1.4 Distribute product request.


16/16


Summary

Project Scheduling Scheduling Principles

Project Work Breakdown Structure


WBS Top-down and Bottom-up Integration Process WBS Format

Hierarchy

Outline

GANTT Chart

Documents

MELJUN CORTES JEDI Slides-7.4 Project Scheduling