1. Software Project Management
for
HMS
[Hospital Management System]
1 7/20/2012

2. What is
Software Project Management?
 Software Project Management is
the art and science of planning and
leading software projects.
 It is a sub-discipline of project
management in
which software projects are
planned, monitored and controlled.
2 7/20/2012

3. Good project management
cannot guarantee
success……
3 7/20/2012

4. But poor management on
significant projects always
leads to failure.
4 7/20/2012

5. Software Project
Management Phases :-
5 7/20/2012

6. 6 7/20/2012

7.  Project Initiating Process
 Project Planning Process
 Project Executing Process
 Project Closing Process
7 7/20/2012

8. Project Initiating Process
 Project Charter
The Project Charter is developed during the
initiation phase to formally authorize a project.
 It has details about the scope of the project, its
deliverable and what domain needs, problems or
opportunities the project addresses
8 7/20/2012

9. Sr Milestone Proposed Date Remark
No
1 Design of HMS 07/05/2012 First Prototype Shown
2 Basic Features 03/06/2012 Without Reports
3 Complete Project 30/06/2012 With Reports
9 7/20/2012

10.  Feasibility Study
A feasibility study has been conducted –
 Technical Feasibility
 As the proposed system is intranet based; We use
PHP and MySQL
 Legal Feasibility
 As the technology chosen is open source so there
may not be any legal issues of software.
10 7/20/2012

11.  SDLC Model Used
11 7/20/2012

12. The Iterative
Waterfall Model of the Software Life Cycle
Requirement
Gathering
Analysis
Design
Coding
Testing
Installation
Operation &
12 Support
7/20/2012

13. Cost Estimation
13 7/20/2012

14.  Business Case
 A Business Case helps to determine whether or not
a project justifies an organizations investment into a
project.
 Obviously as the in-house resources are readily
available, there is no need to hire additional
manpower; it justifies an organizations investment
into a project
14 7/20/2012

15. Project Planning Process
 Change Management Plan
Change will happen during our project, there's no
way to avoid it.
 We prepared for changes by developing our
system in such a way that it accept changes.
 We used MVC(Model-View-Controller)
architecture to build our system and hence we
separates database, web design and web
development.
15 7/20/2012

16.  Communications Management Plan
The Communications Management Plan defines
the communication requirements for the project
and how the information is to be distributed.
 Effective communications is critical to the success
of a project, for this reason we maintain proper
flow of information within a team.
 Project Manager fixes an appointment with the
client; accordingly system analysts visit the client
and communicate with development team.
16 7/20/2012

17.  Cost Management Plan
(REFER COCOMO FOR ESTIMATION OF EFFORTS AND
DURATION)
 The Cost Management Plan details how the
project costs will be measured and reported
upon.
 We estimated efforts and duration for our project
by using COCOMO Model.
17 7/20/2012

18.  Human Resource Plan
Project Managers 2
Team Members
 Programmer 2
 DBA 2
 System Analyst 2
18 7/20/2012

19.  Project Management Plan
The Project Management Plan states how the
project being executed.
 See Gantt Chart Next
 [Reference Tool –
https://secure.gantto.com/login/gantto.html#de
mo]
19 7/20/2012

20. TASK START DATE END DATE
1 Requirement Gathering 05-Apr-2012 10-Apr-2012
2 Analysis 11-Apr-2012 20-Apr-2012
3 Design of HMS 16-Apr-2012 07-May-2012
4 HMS [Basic Features] 08-May-2012 01-Jun-2012
5 HMS [Complete] 04-Jun-2012 13-Jul-2012
20 7/20/2012

21. 21 7/20/2012

22.  Work Breakdown Structure (WBS)
[Source Tool -
http://www.wbsplanner.com/free/wbsp36.php ]
22 7/20/2012

23. WBS for HMS
23 7/20/2012

24. Project Monitoring and Controlling
Process
 We used timesheet for monitoring various tasks.
 Completed tasks have been marked cross.
24 7/20/2012

25.  Project Acceptance
We will plan to prepare the Project Acceptance
document of the project by the Project Sponsor
(Client)
25 7/20/2012

26. COCOMO
Constructive Cost Model
 COCOMO applies to three classes of software
projects:
 Organic projects - "small" teams with "good"
experience working with "less than rigid"
requirements
 Semi-detached projects - "medium" teams
with mixed experience working with a mix of
rigid and less than rigid requirements
 Embedded projects - developed within a set of
"tight" constraints. It is also combination of
organic and semi-detached projects.
26 7/20/2012

27. 27 7/20/2012

28. 28 7/20/2012

29. 29 7/20/2012

30. 30 7/20/2012

31.  People required (P) = Effort Applied / Development
Time
 P = 16.69 / 7.29
= 2.29
 2.29 Persons for 7.29 Months
 5.56 Persons for 3 Months
( 6 Persons * 30,000 ) = Rs. 1,80,000
For 3 Months => Rs. 5,40,000
BACK TO ORIGIN
31 7/20/2012