PROJECT MANAGEMENT

E - Connect Solution Pvt. Ltd.

Submitted by: Batch:B1 PranjalGupta (9103407) AshimaAgrawal (9103408) Aakanksha Bansal(9103410) ShubhanganiMaheshwari(9103415) Amber Agarwal(9103421) Rohan Kataria(09103429)

Project Overview
The Online Sale Management System is a web-based application designed to study the Business Model of Urban Development Authority. The purpose of this project is to develop a Sale Management System which can be used for managing and maintaining various Sale related information i.e. new Sale Campaign entry, campaign property detail, reservation category entry, plot area details, income category, and current reserve price and authorized bank. It also offering the facility of raw plot entry with their sale mode, auction process detail entry for specific plots and lottery process system. Along with the provision for updating the new record integrated with Urban Development Authoritys day-to-day business processes. The brief work flow of the Project can be understood as follows: The core module of the system is Application Processing & Allotment Process Module which is used for maintaining and managing various Sale related information of Urban Development Authority. Once Online Sale Management System is running, any transaction /operation related to a property are executed through the system. The property record is automatically updated and reflected everywhere in the system.

Details requirements are defined in the following sections. Following is outline of requirements to be implemented:

 Sale Management System is the core module of the system which focuses on managing various scheme related information i.e. new scheme entry, development entry, reservation category entry, plot area details, income category, current reserve price and authorized bank. It also offering the facility of raw plot entry with their sale mode, auction process detail entry for specific plots and lottery process system. User Management System manages all the system utilities controlled by the system administrator. It comprises of defining modules, menu objects and forms/reports within these menu objects. User management section also focuses on defining user roles according to their objectives and functionality and thereby assigning rights/ privileges to them.

Project Objective
Planning, scheduling, controlling, monitoring, and analyzing a project based on an Online Sale Management System designed to study the Business Model of Urban Development Authority.

Life Cycle of the project

Project Planning
The following are the key members of the project team: 1. Business Analyst 2. Project Manager 3. Team Leader 4. Function Head 5. Function Executor

Work Breakdown Structure

Work Task
1. Project Planning 2. Application & Allotment Process 2.1 Requirement & conceptualization 2.1.1 BA (Business Analysis) 2.1.2 SRS 2.1.3 Product Backlog 2.2 Execution 2.2.1 Prototype Development 2.2.2 Prototype fine tuning 2.2.3 Final Development 2.2.4 Validation & Verification 2.3 Implementation 2.3.1 Deployment 2.3.2 Customization & configuration 2.3.3 User Acceptance 2.3.4 Application Conclusion 3. Online Application Workflow 3.1 Requirement & conceptualization 3.1.1 BA (Business Analysis) 3.1.2 SRS 3.1.3 Product Backlog 3.2 Execution 3.2.1 Prototype Development 3.2.2 Prototype fine tuning 3.2.3 Final Development 3.3 Validation & Verification 3.3.1 V&V 3.3.2 Stress Testing 3.4 Implementation 3.4.1 Deployment 3.4.2 Customization & configuration 3.4.3 User Acceptance 3.4.4 Application Conclusion 4. Banker workflow 4.1 Requirement & conceptualization 4.1.1 BA (Business Analysis) 4.1.2 SRS 4.1.3 Product Backlog 4.2 Execution 4.2.1 Prototype Development 4.2.2 Prototype fine tuning 4.2.3 Final Development 4.2.4 Validation & Verification 4.3 Implementation 4.3.1 Deployment 4.3.2 Customization & configuration

Labor days (Estimate)

2 40 8 3 2 3 21 6 3 12 4 6 2 2 2 1 37 7 3 2 2 16 6 3 7 8 4 4 4 1 2 1 1 22 4 1.5 1.5 1 10 3 2 5 3 4 1 2

4.3.3 User Acceptance 4.3.4 Application Conclusion

Responsibility Matrix
P B S P P P M A R B D F S T F V D C U A B S P P P D A C A R B D F & & S T V B A P P M T L F H B n R A F H V n V F E B n R A F E I n S F E D N D F E V n V F E B n R P P C P F V S D C U A B S P P P D & T A C A R B D F V & S T C P F V D C U A D A C & & V C

P P P P

P P P P

P P

P P P P

P P

P P

P P P

P P

P P

P P

P P

P P

P P

P P

P P

P P

P P

P P

Activities Purple- Application and Allotment Processing Blue- Online application workflow Green- Banker Workflow Abbreviations Used: BA- Business Analyst SRS- Software requirement specification PB- Product Backlog PD- Prototype Development PFT- Prototype Fine tuning FD- Final Development V & V- Validation and Verification D- Deployment C & C- Customization and configuration UA- User Acceptance AC- Application Conclusion ST- Stress Testing

Resource Allocation
Resources Used: 1. 2. 3. 4. 5. 6. 7. 8. PM Project Manager FE-BnRA- Business and Requirement Analysis , Function Executor FH-BnRA - Business and Requirement Analysis ,Function Head FE-Dnd Development and Delivery ,Function Executor TL-Dnd Team leader, Development and Delivery Executor FE-Vnv Verification and Validation , Function Executor FH-VnV- Function Head, Validation and Verification FE-InS Implementation and Support by Function Executor

Analysis
As we can see from the bar graphs few resources are leveled properly but some are not leveled. To level the resources we will have to shift the activities but as we can see from the activity diagram there is no slack in the activities so we cannot delay the activities without affecting the project time and hence, resources cannot be leveled. Using a different software model process could help to level the resources.

Budgeting and Cost Estimation

The brief budget of project is as follows:-

1. Cost per hour of each resource

2. Over budgeting resources

Analysis Looking at the over budgeting resource table it is clearly seen that there is a lot of deviation in the estimated cost and the actual cost. Financial analysis of potential problems was not done. If any person (resource) leaves the project/company then in that case either a new person is hired or the cost of each resource increases because in such a case the work load on each employee will increase. Hiring a new employee would add to cost and time of the project. Also the employee might have to be trained and would take time to understand the software in order to work on it. Analyzing all these factors would lead to better financial planning.

Scheduling
Activity ID Early Start Early Finish Late Start Late Finish Slack 3 0 2 0 2 11 2 5 2 5 12 5 7 5 7 13 7 10 7 10 15 10 16 10 16 16 16 19 16 19 17 19 31 19 31 18 31 35 31 35 20 35 37 35 37 21 37 39 37 39 22 39 41 39 41 23 41 42 41 42 27 42 45 42 45 28 45 47 45 47 29 47 49 47 49 31 49 55 49 55 32 55 58 55 58 33 58 65 58 65 35 65 69 65 69 36 69 72 69 72 38 72 73 72 73 39 73 74 73 74 40 74 75 74 75 41 75 76 75 76 45 76 77.5 76 77.5 46 77.5 79 77.5 79 47 79 80 79 80 49 80 83 80 83 50 83 85 83 85 51 85 90 85 90 52 90 93 90 93 54 93 94 93 94 55 94 96 94 96 56 96 97 96 97 57 97 99 97 99 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Project Completion Time: 99 Days.

Crashing
As we know that crashing is a tradeoff between cost and time, so while crashing a project or a given activity of a project both the factor need to be kept in mind. Our main aim is basically to complete the project in minimum possible number of days and incur the least cost with maximum utilization of resources. The critical path of our project is 99 days. As we can see from the data, in the activity Sale Campaign Definition under the sub activity final development, the execution process takes 12 days. If we crash this part of the project by employing one additional employee skilled in each resource, the project will be completed 6 days earlier but will lead to increase in costs from Rs 36480 to 54720. Hence the project execution time came down to 93 days. If we also crash the activity of prototype development which originally takes 6 days to complete, the project duration reduces further by 3 days. It results in an increase in costs from Rs 20,400 to 30600. Hence the overall cost of the project which was initially Rs 3, 19,400 increases to 3, 47,840 and also reducing the total time taken by project to complete to 90 days. Similarly we can crash other activities of the projects, taking into account the tradeoff between cost and time.

.00 3 60

Cost(Rupees * 1000)

3 50

.00

.00 3 40 3 30 .00

.00 3 20 3 10 .00

.00 3 00 85.0

90.0

95.0

100.0

Days

Project Monitoring and Control

In this project, the project team uses the Tracking Gantt Chart which allows them to constantly review the projects status and progress by linking task initiation and completion to the project schedule. The schedule is reviewed at the interval of every 15-20 Days. The progress review is focused on Percentage of work done and work remaining Bottlenecks of the remaining tasks Resource utilization: Utilization of resources according to schedule and in favor of all performance, cost and time. Resources re-shuffling due to escalation of task: sequence of tasks maybe changed in the schedule later at a stage due to changed priorities and therefore resource re-shuffling is needed. Possible risks which maybe encountered in the future and their solutions. Resource Utilization and resources re-shuffling due to escalation of task is monitored by resource allocation charts and graphs. By using these tools, the amount of resources used and available is monitored.

Analysis of Software Project Model

In this project the software development model used is waterfall model with incremental process. The whole project is divided into modules and each module is implemented separately. In this case there are four modules (3 main modules) and each module is executed using the waterfall approach. A waterfall development allows for departmentalization and managerial control. A schedule can be set with deadlines for each stage of development and a product can proceed through the development process like a car in a carwash, and theoretically, be delivered on time. Development moves from concept, through design, implementation, testing, installation, troubleshooting, and ends up at operation and maintenance. Each phase of development proceeds in strict order, without any overlapping or iterative steps. The major disadvantage of waterfall model is that it does not allow for much reflection or revision. Once an application is in the testing stage, it is very difficult to go back and change something that was not wellthought out in the concept stage. For example in the implementation of every module a report (BA, SRS) is made that specifies the requirements of the project. Now in the later stage during the development of the project (VnV) if it is found that some requirement is not fulfilled then no changes can be made in the report. Usually, customer requirements do change during the duration of the project, as requirements are not well understood to begin with. So using this process model of software development results in problems during the execution of the project.

The disadvantage of incremental approach is that each phase of an iteration is rigid and do not overlap each other. Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cycle. The activity diagram is linear that is each activity is completed one after another and there are no parallel activities. In this project since the activities dont overlap as clearly seen in the activity diagram with each other it takes more time to complete the project. If there would have been overlapping activities the project could have been completed in much lesser time. To overcome most of these problems, we suggest using the agile process of software development. This model ensures that changes in the software requirements can be incorporated relatively easily. Using this model reduces the time taken to develop the software and also results in higher customer satisfaction. Also, if more staff can be hired, all 3 modules of the project can be developed simultaneously, and duplication of work can be avoided. It would also result in drastically reducing the time for completion of the project, but would cost more.