Software Project Management (SPM) is a sub-field of Project Management in which software projects are planned, implemented, monitored and controlled.
It consists of three terms: Software, Project and Management. So, let us understand each term separately. Software includes a set of programs, documentation and user manual for a particular software project. So, it is basically the complete procedure of the software development starting from the requirement gathering phase and extending to testing and maintenance. Project means a planned activity which consists of several well defined tasks. Management makes sure that the product comes out as planned.
There are many constraints of the software projects but the main and fundamental constraints includes: Time, Cost and Quality. Any one of the twp factors can severely affect the third one. Therefore, Software Project Management is essential to develop software projects within time and the specified budget and that too of good quality.
Software Project Manager:
Software Project Manager is generally never directly involved in producing the end product but he controls and manages the activities involved in the production. He is aware of all the phases of Software Development Life Cycle that the software would go through.
Responsibilities of software project manager:
- Managing people:
- Acts as a project leader
- Communication with stakeholders
- Manages human resources
- Managing project:
- Monitors progress and performance
- Risk analysis at every phase
- Manages time and budget constraint
Categorizing Software Projects:
- Compulsory Vs Voluntary systems (projects):
- Compulsory systems are the systems which the staff of an organisation have to use if they want to do a task.
- Voluntary systems are the systems which are voluntarily used by the users eg. computer gaming, school project, etc.
- Information Vs Embedded systems (projects):
- Information systems are used by staff to carry out office processes and tasks eg. stock control system.
- Embedded systems are used to control machines eg. a system controlling equipment in a building.
- Objective-based Vs Product-based systems (projects):
- Project whose requirement is to meet certain objectives which could be met in a number of ways, is objective-based project.
- Project whose requirement is to create a product, the details of which have been specified by the client, is product-based project.
- Software Engineering | Project size estimation techniques
- Types of Software Testing
- Software Testing | Basics
- Software Engineering | Architectural Design
- Software Engineering | Halstead’s Software Metrics
- Beta Testing | Software Testing
- Software Engineering | Debugging Approaches
- Pairwise Software Testing
- Software Engineering | COCOMO Model
- Software Engineering | Classification of Software Requirements
- Software Engineering | Classical Waterfall Model
- Software Engineering | Iterative Waterfall Model
- Software Engineering | Spiral Model
- Software Engineering | Requirements Engineering Process
- Software Engineering | Requirements Elicitation
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.