Software Project Management

Project:
A project is a temporary endeavor designed to produce a unique product, service, or result with a defined beginning and end undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value.

Project Management:
Project management is the application of processes, methods, skills, knowledge, and experience to achieve specific project objectives according to the project acceptance criteria within agreed parameters.

Project management has final deliverables that are constrained to a finite timescale and budget.

What is Software Project Management?
Software project management is a specialized discipline within the realm of project management that focuses on planning, executing, monitoring, controlling, and closing software development projects.

It encompasses the systematic management of resources, budget, and time to ensure the successful completion of a software project.

Project Management Triangle: (called also the triple constraint, the iron triangle, and the project triangle)
The project management triangle is a model of the constraints of project management. It is an essential part of software
organization to deliver quality product, keeping the cost within client’s budget constrain and deliver the project as per scheduled.

Factors that Affect Software Projects:
Internal and external factors affect every business decision that a company makes, and IT systems
projects are no exception. The below shows the main internal and external factors:

Internal Factors and External Factors

No	Project  Internal Factors	Project External Factors
01	Strategic plan	Technology
02	Top managers	Suppliers
03	User requests	Customers
04	Information technology department	Competitors
05	Existing systems and data	The economy
06	Risk Management	Government

 

 

Risk Analysis Life cycle

 

Some of most important risks in software engineering project:

1. software requirement risks
2. software cost risks
3. software scheduling risk
4. software quality risks

SOFTWARE REQUIREMENT RISKS

1.Lack of analysis for change of requirements.
2.Lack of report for requirements
3.Poor definition of requirements
4.Change of requirements
5.Impossible requirements

SOFTWARE COST RISKS

1.Lack of good estimation in projects
2.Human errors
3.Lack of testing
4. Lack of monitoring
5.Complexity of architecture

SOFTWARE SCHEDULING RISKS

1.Lack of enough skill
2.Change of requirements and extension of requirements
3.Inadequate knowledge about tools and techniques
4.Lack of employment of manager experience
5.Lack of good estimation in projects

SOFTWARE QUALITY RISKS

1.Lack of project standard
2.Lack of design documentations
3.Poor definition of requirements
4.Lack of testing and good estimation in projects
5.Poor knowledge about techniques, programming language, tools, and so on.

 

Thank You!