Project Management

Co-operative Society Management System

Project Management

2.1 Project Planning 2.2 Project Scheduling 2.3 Risk Management 2.4 Estimation

Hasmukh Goswami College of Engineering

Project Management

Co-operative Society Management System

PROJECT MANAGEMENT
2.1 Project Planning
2.1.1 Project development and justification

Chapter-2

Based on time frame, provided discussion with the project guide. From the discussion and the understanding cultivated by the Project guide, various functional issues have been identified, these issues or the areas of concern, are specifically highlighted to:

Understand the potential weakness and threats accompanying the functionality Develop a better grasp of the overall organizational need Prepare a preliminary ground to zero in on the various alternatives available for an overall organizations development strategy. Identify a road map to initiate action for implementing the strategic option chosen.

Spiral Model:

The spiral model, also known as the spiral lifecycle model, is a systems development lifecycle (SDLC) model used in information technology (IT). This model of development combines the features of the prototyping model and the Waterfall Model. The spiral model is favoured for large, expensive, and complicated projects.

The steps in the spiral model can be generalized as follows: The new system requirements are defined in as much detail as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.

A preliminary design is created for the new system.

Hasmukh Goswami College of Engineering

Project Management

Co-operative Society Management System

A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.

A second prototype is evolved by a fourfold procedure: (1) evaluating the first prototype in terms of its strengths, weaknesses, and risks; (2) defining the requirements of the second prototype; (3) planning and designing the second prototype; (4) constructing and testing the second prototype.

Fig. 2(a) :- Spiral lifecycle

Hasmukh Goswami College of Engineering

Project Management

Co-operative Society Management System

At the customer's option, the entire project can be aborted if the risk is deemed too great. Risk factors might involve development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer's judgment, result in a less-than-satisfactory final product.

The existing prototype is evaluated in the same manner as was the previous prototype, and, if necessary, another prototype is developed from it according to the fourfold procedure outlined above.

The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.

The final system is constructed, based on the refined prototype.

The final system is thoroughly evaluated and tested. Routine maintenance is carried out on a continuing basis to prevent large-scale failures and to minimize downtime.

Advantages:

The key is continual development; it is intended to help manage risks. You should not define the entire system in detail at first. The developers should only define the highest- priority features. This type of development relies on developing prototypes and then giving them back to the user for trial. With this feedback the next prototype is created. Define and implement this, then get feedback from users / customers (such feedback distinguishes 'evolutionary' from 'incremental' development). With this knowledge, you should then go

Hasmukh Goswami College of Engineering

Project Management

Co-operative Society Management System

back to define and implement more features in smaller chunks, until an acceptable system is delivered.

The advantages of using the spiral model are varied: its design flexibility allows changes to be implemented at several stages of the project; the process of building up large systems in small segments makes it easier to do cost calculations; and the client, who will be involved in the development of each segment, retains control over the direction and implementation of the project. In addition, the client's knowledge of the project grows as the project grows, so that they can interface effectively with management.

As the model continues towards final phase, the customer's expertise on new system grows, enabling smooth development of the product meeting client's needs.

Disadvantages:

Spiral models work best for large projects only, where the costs involved are much higher and system pre requisites involves higher level of complexity.

Spiral model needs extensive skill in evaluating uncertainties or risks associated with the project and their abatement.

Spiral models work on a protocol, which needs to be followed strictly for its smooth operation. Sometimes it becomes difficult to follow this protocol.

Evaluating the risks involved in the project can shoot up the cost and it may be higher than the cost for building the system.

Hasmukh Goswami College of Engineering

Project Management

Co-operative Society Management System

There is a requirement for further explanation of the steps involved in the project such as breakthrough, blueprint, checkpoints and standard procedure.

Why I used this model?

The Spiral Model is used as the developing strategy of this project .Reason behind this is that after once the requirement are specified from the end user if the end user want to changes the requirement then it is useful.

Adaptability in the design of spiral model in software engineering accommodates any number of changes, which may happen, during any phase of the project.

2.1.2

ROLES AND RESPONSIBILITIES

Master Administrator

The master administrator keeps a track on the overall working of all societies. The master administrator checks the requests for adding a society. He verifies the requests and accepts if it is authentic, else rejects the request.

Remote-Administrator

Give all details regarding expenditure of occasional functions and events to the society members. Issue notice regarding any event, etc. Collect all complains from the members and take proper actions.

Hasmukh Goswami College of Engineering

Project Management

Co-operative Society Management System

Keeps a record of total number of society members. Keeps check whether the rent is paid on time or not. If not paid on time then he gives them suitable notice.

Registered-Members They can check the updates on the current events. They can take a look at the expenditure. They can even update their profiles. They can post their complaints if they have any.

Guest-User

Guest can see the advertisements and contact the members

Hasmukh Goswami College of Engineering

Project Management

Co-operative Society Management System

2.2 Project Scheduling

The following is the schedule for the project:

TABLE 2.1 PROJECT SCHEDULE Activity Project Assignment Requirement Gathering System Analysis System Design System Implementation System Testing and Modification Schedule time 23rd July 1 hour per day for 3 weeks 1 hour per day for 3 weeks 1 hour per day for 3 weeks 1 hour per day for 3 weeks 1 hour per day for 4 weeks

2.3 Risk Management

Major risks for this software development are 1) Increase of workload on developers and hence divided attention on project. 2) Insufficient guidance in the fields of the project. 3) Inexperience in project software environment. 4) Requirements have been finalized but continue to change. 5) Overly optimistic schedules.

Hasmukh Goswami College of Engineering

Project Management

Co-operative Society Management System

2.3.1

Risk identification

Our development team identified different potential risks to the project. These risks were analyzed and were classified into various categories depending upon the threat they posed to the project. Some of these risks were generic risks while others were product specific risks. A considerable amount of time was spent in analyzing the product specific risks

2.3.2

Risk analysis

We analyzed all the risks individually and we came up with a classification of risks on the basis of their impact on project schedule. These risks were rated as follows: Catastrophic Critical Marginal Negligible These were then reviewed and a consensus on the impact was reached

2.3.2.1 Types Of Risks

This project does face certain risks in its implementation, which have to be addressed through its architecture and the design of its incentives. Some of these risks include:

Hasmukh Goswami College of Engineering

Project Management Risks of scale:

Co-operative Society Management System

The project will have to handle large amount of records. This creates significant risks in biometric de-duplication as well as in administration, storage, and continued expansion of infrastructure.

Technology risks:

Technology is a key part of this program, and this is the first time in the world that storage, authentication and de-duplication of biometrics are being attempted on this scale.

Privacy and security risks:

The project will have to ensure that resident data is not shared or compromised.

Sustainability risks:

The economic model for the project will have to be designed to be sustainable in the longterm, and ensure that the project can adhere to the standards mandated by the Authority.

2.3.3

Risk planning

The risks have been tackled in a proactive manner. All the risks that could be foreseen were identified and an active plan to tackle them was developed.

Hasmukh Goswami College of Engineering

Project Management

Co-operative Society Management System

The other above mentioned risks were dealt with by meeting some experienced programmers and faculty of the college.

Development Environment risks was taken care of by the college faculty themselves by providing appropriate tools and required environment for our project.

2.4 Estimation

2.4.1

Effort Estimation Software project scheduling is an activity that distributes estimated efforts across the planned duration by allocating the effort to specific software engineering tasks. Program Evaluation and Review Technique (PERT) and Critical Path Method (CPM) are two most widely used techniques in project management. Historically speaking, PERT and CPM developed independently out of research studies conducted by U.S. Navy and DuPont Company. The PERT was applied to Research and Development tools, while CPM was used to construct the projects. These two project management & scheduling method that can be applied to software development. Both techniques are driven by information already developed in earlier project planning activities:

Estimation of effort. A decomposition of the product function. The selection of appropriate process model and task set. Decomposition of tasks.

Hasmukh Goswami College of Engineering

Project Management

Co-operative Society Management System

There are some differences between PERT and CPM for selecting it as project management technique like: In PERT total project duration is regarded as a random variable and therefore associated probabilities are calculated to characterize it. PERT is normally used for project involving activities of non- repetitive in nature which time estimates are uncertain. PERT helps in pin pointing critical areas in a project so that necessary adjustment can be made to meet the scheduled completion date of the project. While In CPM duration was known with certainty, therefore it is deterministic approach. It involves repetitive activities.

Hasmukh Goswami College of Engineering