AIM: To study and perform Project Planning

Theory:

Project Planning

There are several reasons to use considerable care when planning projects:

The primary purpose of planning is to establish a set of directions in enough detail to tell the project team exactly what must be done

The purpose of planning is to facilitate later accomplishment

The Work Breakdown Structure

The Work Breakdown Structure (WBS) can take a variety of forms that serve a variety of purposes. The WBS often appears as an outline with Level I tasks on the left and successive levels appropriately indented. The WBS may also picture a project subdivided into hierarchical units of tasks, subtasks, work packages, etc.

The WBS is an important document and can be tailored for use in a number of different ways:

It may illustrate how each piece of the project contributes to the whole in terms of performance, responsibility, schedule, and budget

It may list the vendors or subcontractors associated with specific tasks It may serve as the basis for making cost estimates or estimates of task duration It may be used to document that all parties have signed off on their various commitments to the

project

General steps for designing and using the WBS:

1. Using information from the action plan, list the task breakdown in successively finer levels of detail. Continue until all meaningful tasks or work packages have been identified

2. For each such work package, identify the data relevant to the WBS. List the personnel and organizations responsible for each task.

3. All work package information should be reviewed with the individuals or organizations who have responsibility for doing or supporting the work in order to verify the accuracy of the WBS

4. The total project budget should consist of four elements: direct budgets from each task; an indirect cost budget for the project; a “contingency” reserve for unexpected emergencies; and any residual, which includes the profit derived from the project

5. The project master schedule integrates the many different schedules relevant to the various parts of the project

6. The project manager can examine actual resource use, by work element, work package, task, up to the full project level. The project manager can identify problems, harden the estimates of final cost, and make sure that relevant corrections have been designed and are ready to implement

7. The project schedule may be subjected to the same comparisons as the project budget. Actual progress is compared to scheduled and corrective action can be taken

DELIVERABL E DEFINITION TABLE

DELIVERABLE STRUCTURE STANDARDS APPROVAL NEEDED BY

RESOURCES REQUIRED

Problem Definition and

Scope

Document As defined in project

methodology

Project Manager Project team and Office tools

Feasibility Study Document AS defined in project

methodology

Project Manager Project team and Office tools

Project Charter Document As defined in project

methodology

Project Manager Project Manager, Project team and office

toolsResource and

budget assessment

Document As defined in project

methodology

Project sponsor and

Project Manager

Project Manager, Project team, Project sponsors and office

toolsRequirement

AnalysisDocument As defined in

project methodology

Project Manager Customer, System Analyst and

Office toolsRisk management

and SchedulingDocument As defined in

Project methodology

Project Manager System Analyst and Project Team

Physical and Technical Designs

Document As defined in Project

methodology

Project Manager Programmer, System Analyst and Case tools

User Interface Prototype As defined inUser Interface

Guidelines

Project Sponsor and Project

Manager

Programmer and Integrated

Development Environment(Netbeans)

Application System

Files and Database

As defined inProject

methodology

Project Sponsor and

Project Manager

Programmers, System Analyst, Networking

Specialist and Server(Xampp Server)

Testing Plan Document As defined inProject

Methodology

Project manager System Analyst and Office tools

Testing Results Document As defined inTest Plan

Project Manager Programmer, System Analyst and Office tools

Final Report and Presentation

Document As defined inProject

methodology

Project manager,External

examiner

Project Sponsor, Project Manager, System and

Project teamProject Evaluation

andLessons learned

Document As defined inProject

methodology

Project manager Project team and knowledge

management systemDELIVERABLE STRUCTURE CHART

InitializationInitialization

Work breakdown Structure

Define Project GoalDefine Project Goal

Work Package

Work Package for R-Tree Implementation:

1. Statement of Work:

Retrieval of images using content based retrieval and implementation of

r-tree algorithm.

2. Resource Requirement:

Labor 4 for 16 weeks 1 manager, 1 programmer, 1 database designer, 1 GUI

designer, 1 tester. Material

Software Requirement:XAMP server, Web host

Hardware Requirement:Computers

Facility: Internet, place.

3. Time: 16 weeks 24th August to 10th April

4. Cost: 1 Manager : 10hrs 5000 1 Programmer : 100hrs 10000 1 Database designer : 25hrs 2000 1 GUI designer : 15hrs 1000 1 tester :20hrs 1500

TOTAL 19500 10% TAX 1950

5. Responsibility:

Name Designation Responsibility

Roopali Lolage Manager To keep a track on project work and guide for changes to be made.

ShyamMahishi Programmer To code in ASP.netSagar Awasare Database designer To design database Rajesh Mothe GUIdesigner To design GUI

6. Output/Outcome:Fast retrieval of images on web.

7. Input:Design, Programming codes,Algorithms,Image

8. Quality Assurance:

The images are retrieved at a faster rate using r-tree algorithm in comparison to linear search of images.Content based retrieval of images helps retrieval of images with similar characteristics like color, structure etc.

9. Others:This project can be sold to clients on the contract basis.

RESPONSIBILITY MATRIX

Responsibility CodesP :- Primary ResponsibilityS :- Secondary ResponsibilityN :- Must be notifiedA :- Must give approval

PROJECT TASK OR ACTIVITY

PROJECT MANAGER(ROOPALI LOLAGE)

SHYAM MAHISHI SAGAR AWASARE RAJESH MOTHE

PROJECT COORDINATION

P

PROJECT DEVELOPMENT

A

PROJECT DESIGN A N S SGUI DESIGN N,A PDATABASE DESIGN

N,A P

DEFINING PROJECT GOAL

N,A P S

SOFTWARE PURCHASE

N P

RISK MANAGEMENT

A P S S

REQUIREMENT ANALYSIS

N P P P

FEASIBILITY STUDY

A S P

PROJECT CHARTER

N,A P P P

FINAL REPORT AND PRESENTATION

A,N P S