Download - Activity Planning,software project management

7/31/2019 Activity Planning,software project management

1/15

By

Darwin v Tomy

(713511421001)


2/15

INTRODUCTION Ensure that the appropriate resources will be available

precisely when required. Avoid different activities competing for the same resour

the same time.

Produce a detailed schedule showing which staff carry ou

activity.

Produce a detailed plan against which actual achievementbe measured.

Produce a timed cash flow forecast.

Replan the project during its life to correct drift from

target.


3/15

THE OBJECTIVES OF ACTIVITY

PLANNING

FEASIBILITY ASSESSMENT

RESOURCE ALLOCATION

DETAILED COSTING

MOTIVATION PROVIDING

COORDINATION


4/15

WHEN TO PLAN

Planning is an ongoing process ofrefinement, each iteration becoming

more detailed and more accurate than

the last. Over successive iterations,the emphasis and purpose of planning

will shift.


5/15

PROJECT SCHEDULES

Before work commences on a project orpossibly, a stage of a larger project,

the project plan must be developed to

the level of showing dates when eachactivity should start and finish and

when and how much of each resources

will be required. Once the plan has

been refined to this level of detail wcall it a project schedule


6/15

Creating a project schedulecomprises four main stages.

Ideal activity plan

Activity risk analysis

Resource allocation

Schedule production


7/15

PROJECTS AND ACTIVITIES A project is composed of a number of interrelated activiti

A project may start when at least one of its activities is

ready to start.

A project will be completed when all of the activities itencompasses have been completed.

If an activity must have a clearly defined start and a cledefined end-point, normally marked by the production of atangible deliverable.

An activity requires a resource (as most do) then that resrequirement must be forecastable and is assumed to be requat constant level throughout the duration of the activity.

The duration of an activity must be forecastable assuminnormal circumstances, and the reasonable availability ofresources.

Some activities might require that others are completed be

they can begin (these are known as precedence requirements


8/15

IDENTIFYING ACTIVITES

Activity-based approach.

Product-based approach.

Hybrid approach.


9/15

THE ACTIVITY-BASED

APPROACHCreating a list of all the activitiesthat the project is thought to involve.This might involve a brainstorming sessioinvolving the whole team or it might stemfrom an analysis of similar past projectWhen listing activities, Particularly fora large project, it might be helpful tosub-divide the project into the main lifestyle stages and consider each of theseseparately.


10/15

THE ACTIVITY-BASED

APPROACHProject

Analyse Design Build

Datadesign

Processdesign

Physicaldesign

Relationaldata

analysis

Logicaldata

design


11/15

THE PRODUCT-BASED APPROAC

It consists of producing a ProductBreakdown Structure and a flow diagram.The PFD indicates, for each product, whiother products are required as inputs. ThPFD can therefore be easily transformed

into an ordered list of activities byidentifying the transformations that turnsome products into others .Proponents ofthis approach claim that it is less likelthat a product will be left out of a PBSthan that an activity might be omittedfrom an unstructured activity list.


12/15

THE PRODUCT-BASED APPROACRequirementsSpecification

Data catalogueRequirements

catalogue

Processingspecification

Attribute/ data

itemdescriptions

Grouped domaindescriptions

User role/function matrix

Functiondefinitions

Required systemlogical data

model

Entity lifehistories

Effectcorrespondence

diagrams

I/O structuresEnquiry access

paths

Elementaryprocess

descriptions

Logical datastructure

Entitydescriptions


13/15

THE HYBRID APPROACH

Level 1 : Project Level 2 : Deliverables such as software,

manuals and training courses.

Level 3 : Components which are the key woritems needed to produce deliverables, suchas the modules and tests required to produthe system software .

Level 4 : Work-packages which are major woitems, or collections of related tasks,required to produce a component.

Level 5 : Tasks which are tasks that will

normally be the responsibility of a singleperson.


14/15

THE HYBRID APPROACH

Installed SystemSoftware

ComponentsUser manuals Training course

Project

Analyserequirements

Reviewrequirements

Analyserequirements

Analyserequirements

Outline design Outline design Design manual Design course

Detailed designDetailed design Write test

Write manual

Integratesystem

Code software Capture screens Print handouts

Test system Test software Do page layout Deliver course

Deliver system Print manuals

User testing


15/15