TK3333Software Management

Topic 5:Topic 5:PlanningPlanning

ContentsContents Project Objective

Work Breakdown Structure (WBS)

Network Diagram

Project Management Methodology Systems Development Life Cycle (SDLC) for

Information Systems (IS) development projects

Real World ExampleReal World Example• Vignette: The Olympics • Athens, Greece received the award to host the 2004 Olympic Games in

1997 • Project work did not begin until 2000, after a warning was issued by the

International Olympic Committee. $1.19 billion was added to the project cost because of construction delays and the need for increased security

• Less than 100 days remained, and it appeared that most construction projects would not be complete until a few days before the games

• Olympic project team worked under a very tight time schedule, with little time for independent tasks. Network planning techniques are essential in these situations to define hierarchy of projects

• A project manager can help team members to stay on task with short-term goals to assure that the long-term goals are met on time

Real World ExampleReal World Example• Vignette: German Airlines • Lufthansa German Airlines is the first airline to offer high-speed Internet

access while flying in response to customer need. This would allow customers to check email, log onto company websites, and search for information on the Web. Pilots would benefit from Internet access with more precise weather forecasts

• Installation alone costs $400,000. Development, maintenance, and installation total in the “double digit millions”

• Corporations like Seimens, BASF, Software AG, and Boehringer Ingleheim were invited for trial runs

• Installation was scheduled to begin in January 2004. FlyNet should be available on Lufthansa’s trans-Atlantic flights by spring 2004

Project ObjectiveProject Objective

• Planning is an essential part of project management.

• In essence, the plan is a roadmap.

• The first step is to define the project objective.

• The objective must be clear, attainable, specific, and measurable.

• The objective is usually defined in terms of scope, schedule and cost.

Project ObjectiveProject Objective

From management view, all objectives should be SMART :

•Specific - Be precise about what we are going to achieve.

•Measurable - Quantify our objectives.

•Achievable - Are we attempting too much?

•Realistic - Do we have the resources to make the objective happen (manpower, money, materials, methods)?

•Timed – When will we achieve the objective (e.g. within a month? By February 2020?)

Work Breakdown Structure (WBS)Work Breakdown Structure (WBS)• The second step is to determine what activities need to be

performed.

• A list of all the activities must be developed.

• The WBS is a hierarchical tree of end items to be accomplished.

• A work item is one small piece of the project.

• A work package is the lowest-level item.

• WBS usually indicate the individual responsible for each work item.

Work Breakdown Structure (WBS)Work Breakdown Structure (WBS)

Activities within a workpackage

Work item

Work package (i.e. lowest level work item)

Source: pg. 129

Individual responsible

Responsibility MatrixResponsibility Matrix

• Displays in tabular format the individuals responsible for the work items.

• “X” can be used to indicate who is responsible.

• “P” indicates who has primary responsibility.

• “S” indicates who has secondary responsibility.

Responsibility MatrixResponsibility Matrix

Source: pg. 119

ActivitiesActivities• An activity is a piece of work that consumes time.

– It does not necessarily require the expenditure of effort by people e.g. waiting for suppliers to deliver goods.

• E.g. To conduct a Hari Raya “open house”

– Plan/set food arrangement with caterer– Plan/set venue– Invite guests– Wait guests to come– Entertain guests– “Close house” and collapse (so tired)!

Developing the Network PlanDeveloping the Network Plan

• After all activities have been defined, they are graphically portrayed in a network diagram.

• Two network planning techniques were developed in the 1950s:

– Program Evaluation and Review Technique (PERT)

– Critical Path Method (CPM)

Gantt ChartsGantt Charts

• Gantt charts, or bar charts, are popular due to their simplicity.

• Activities are listed down the left-hand side. A time scale is shown along the bottom.

• Do not display the interrelationships of activities.

• If one activity is delayed, it is not obvious how that will affect other activities.– But, most project management software can show

interdependencies with arrows.

Gantt ChartsGantt Charts

Source: pg. 122

Gantt ChartsGantt ChartsAn example of Gantt Chart using MS Project.

Diamonds: MilestonesArrows: DependenciesBlue bars: The length of an activityBlack bars: How much the task has been completed

Network PrinciplesNetwork Principles

• Different formats can be used to draw the diagram:– Activity in the box (AIB) a.k.a. activity on the node (AON)

– Activity on the arrow (AOA)

Arrange Food

1

Arrange Food

Activity in the Box (AIB)Activity in the Box (AIB)• Each activity is represented by a box.• The activity description is written in the box.• Each box is assigned a unique activity number.• Activities have a precedential relationship.• Some activities may be done concurrently.

Arrange Food

1

SetVenue

2

Invite Guests

3

....

Activity on the Arrow (AOA)Activity on the Arrow (AOA)

• Each activity is represented by an arrow.

• The activity description is written above the arrow.

• The tail of the arrow designates the start of the activity.

• The head of the arrow designates the completion of the activity.

Arrange Food

Start activity End activity

Activity on the Arrow (AOA)Activity on the Arrow (AOA)

• Activities are linked by circles called events.

• An event represents the finish of activities entering it and the start of activities leaving it.

• Each event is assigned a unique activity number.

Arrange Food1 3

Invite Guests

4

Set Venue2

event

Activity on the Arrow (AOA)Activity on the Arrow (AOA)

• 2 basic rules:– Each event must have a unique event number i.e. no two

events can have the same event number.

– Each activity must have a unique combination of predecessor and successor event numbers.

Arrange Food

21Arrange

Beverages

Not Allowed!Must use Dummy activities

Arrange Food

31 Arrange Beverages

2

Dummy ActivitiesDummy Activities

• Used in the AOA format.

• Consumes zero time.

• Represented by a dashed arrow.

• Needed for:

– Helping in the unique identification of activities.

– Showing certain precedential relationships.

Dummy ActivitiesDummy Activities

Arrange Food31

Arrange Beverages

2

Arrange Food21

Arrange Beverages

3

Dummy ActivitiesDummy ActivitiesAOA vs AIBAOA vs AIB

• Example (pg. 125):• Activities A & B can be done concurrently.• When A is finished, C can start.• When both A & B are finished, D can start.

AOA AIB

dummy

LoopsLoops• Not allowed because it portrays a path of activities

that perpetually repeats itself.

• Example (pg. 126)

LadderingLaddering• Used for projects

that have a set of activities that are repeated several times.

• Indicates concurrent activities.

• Example (pg.128)

Preparing the Network DiagramPreparing the Network Diagram

• Ask the following questions regarding each activity:

– Which activities must be finished immediately before this activity can be started?

– Which activities can be done concurrently with this activity?

– Which activities cannot be started until this activity is finished?

Preparing the Network DiagramPreparing the Network Diagram• Should flow from left to right.

• Not drawn to a time scale.– Focus on planning only. In contrast, Gantt chart caters both

planning and scheduling.

• Can vary in how detailed the diagram should be.

• AIB vs. AOA is a matter of personal preference.

• AIB is the most common in project management software packages.

• See example pg. 130-131.

Preparing the Network DiagramPreparing the Network Diagram• May start by having a table:Task/Activity Dependencies Role

T1 - AliT2 T1 SivaT3 T1,T2 TanT4 - AbuT5 - AliT6 T3,T4 SallyT7 T3 TanT8 T7 SivaT9 T6 …T10 T5,T9 …T11 T9 …T12 T10 …T13 T3,T4 …T14 T8,T9 …T15 T12,T14 …T16 T15 …

....

T1

1 Ali

T3

2 Tan

T2

2 Siva

T4

4 Abu

T6

6 Sally ....

Preparing the Network DiagramPreparing the Network DiagramHow detailed a network diagram should be?• Identify activities for each work package.

• Apply “stepwise refinement” (i.e. start with “the mothers” before “the children”). – Sometimes, identifying only “the mothers” can be sufficient (to avoid

microplanning).

• Break obvious cutting points:– Separate activities which are done by different people.– Break activities based on tangible outputs.

• Activities should not be longer than monitoring cut-off time.– If you plan to monitor progress every two weeks, an activity should not

take more than 10 days. Else, break it into two or more activities so that they can be < 10 days each.

Planning for Information Systems Planning for Information Systems DevelopmentDevelopment

• An information system (IS) is a computer-based system that accepts data as input, processes the data, and produces useful information for users.

• The systems development life cycle (SDLC) is used to help plan, execute and control IS development projects.– Similar to generic software development process models (i.e. waterfall

model)

• Many people view the SDLC as a classic problem-solving approach.

Steps of the SDLCSteps of the SDLC• Problem definition

– Gather data; define problems; Feasibility study: technical, economic, operational etc.

• System analysis– Define scope; interview users; study existing systems; defines user requirements.

• System design– Conceptual designs for inputs, outputs, processing, hardware, software, database etc.

• System development– Develop actual system using the purchased hardware. Software may be purchased,

customised or developed.

• System testing– Unit testing; Integration testing; user testing etc.

• System implementation– New system is put on run to replace the old one – installation/deployment ; train users;

conversion etc.

Read an IS example pg. 134-138

Project Management SoftwareProject Management Software• Allow the project manager and the project team to plan and

control projects interactively.

• Example: MS Project; Primavera …

• Contain many common features:– Create list of tasks– Track resources– Track budgets– Generate a variety of reports– Many more….

• Have a try with MS Project.

Some notes …Some notes …Mistakes in planning:

1. Not involve the people who must do the work.– People who must do the work should participate in planning.

2. People are convinced that they do not need a plan.– The more important the project deadline, the more important the plan.

3. Broad-brush planning.– Must identify the major tasks to be performed.

4. Microplanning.– Never plan in more detail than you can control.

5. Failing to plan for risks.– There is a higher probability that things will accidentally go wrong than they will

accidentally go right.

Some notes …Some notes …Rules for planning:

1. No task should have a duration greater than 4-6 weeks. – If more, break the task into several increments.

2. Engineering and programming task should have durations no greater than 1-3 weeks.

– Otherwise, it will 90% complete and stays there forever.

3. All tasks must have “markers” that enable everyone knows that the work is actually complete.

– Milestones e.g. reports, system documentation etc. or any indicators.

Some notes …Some notes …Guidelines for developing a WBS:

1. Up to 20 levels can be used. If more, “we are purposely killing ourselves”.

2. All paths do not have to go down the same level. – Stop at the points that you can manage. Do not force the structure to be

symmetrical.

3. WBS is not meant to show sequencing of work. Sequencing is determined during scheduling.

4. WBS should be developed before scheduling and resource allocation.– Identify “what” first before we could decide “who”, “when”, “how long”.

Some notes …Some notes …Guidelines for developing a WBS:

5. WBS should be developed by individuals knowledgeable about the work. – Different parts of WBS may be developed by various groups (who know best

about the part/task). Later, we combine.

6. Break down the tasks only to a level sufficient to produce an accurate estimate.– One good thing about WBS is that we can accurately estimate the cost and

time, as we have broken the project into meaningful chunks of work.

5. WBS is a list of activities, not a grocery list.– What we must do to complete the task, not what we must have/get.

Thank YouThank You

• Question?

• Group Project.

• Next (30/03) :– Scheduling