Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum. Why do we use it? It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout. The point of using Lorem Ipsum is that it has a more-or-less normal distribution of letters, as opposed to using 'Content here, content here', making it look like readable English. Many desktop publishing packages and web page editors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in their infancy. Various versions have evolved over the years, sometimes by accident, sometimes on purpose (injected humour and the like).

1. SOFTWARE PROJECT
MANAGEMENT
CSPE 318/ITPE318
Dr. Sweeti Sah
Assistant Professor
Department of Computer Engineering

2. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 2
Problems with software projects
Software projects often face various challenges and problems that can hinder their success. These
issues arise from technical, managerial, or organizational factors and can impact the project's
cost, schedule, scope, and quality.

3. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 3
1. Poor Requirement Gathering
•Problem: Incomplete, ambiguous, or changing requirements.
•Impact: Leads to scope creep, rework, and project delays.
•Example: A customer does not clearly define the desired features, leading to misunderstandings
in the development phase.
Scope creep occurs when a project's scope changes after it has started. This can include adding new features or
functionality, or changing the project's budget, timeline, or resources.

4. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 4
2. Unrealistic Deadlines
•Problem: Overly aggressive timelines for project delivery.
•Impact: Results in rushed development, lower quality, and burnout of team members.
•Example: Promising to deliver a fully functional system in half the time required for proper
development.

5. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 5
3. Lack of Proper Planning
•Problem: Poorly defined milestones, deliverables, and risk management.
•Impact: Projects may run over budget, fall behind schedule, or fail to meet objectives.
•Example: Starting development without accounting for integration testing or resource
availability.

6. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 6
4. Inadequate Risk Management
•Problem: Failure to identify, assess, or mitigate risks.
•Impact: Unanticipated issues disrupt the project timeline and outcomes.
•Example: Ignoring the possibility of key technology becoming obsolete mid-project.

7. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 7
5. Scope Creep
•Problem: Continuous addition of new features beyond the original scope.
•Impact: Increased complexity, delays, and budget overruns.
•Example: Stakeholders demand extra functionalities after the development phase has begun.

8. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 8
6. Poor Communication
•Problem: Ineffective communication among team members, stakeholders, or clients.
•Impact: Misunderstandings, delays, and a lack of clarity in objectives.
•Example: Developers not understanding client feedback due to vague or incomplete
communication.

9. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 9
7. Insufficient Budget
•Problem: Underestimating project costs or allocating insufficient funds.
•Impact: Project stagnation, cutting corners, or inability to complete the project.
•Example: Running out of funds for critical testing phases due to poor cost estimation.

10. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 10
8. Technical Challenges
•Problem: Using outdated, incompatible, or immature technologies.
•Impact: Delays, increased maintenance costs, or failure to meet requirements.
•Example: Choosing a technology stack that lacks community support or necessary tools.

11. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 11
9. Low Team Morale
•Problem: Overburdened, underappreciated, or poorly trained team members.
•Impact: Reduced productivity, increased turnover, and missed deadlines.
•Example: Developers feeling demotivated due to lack of recognition for their work.

12. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 12
10. Poor Quality Assurance
•Problem: Insufficient testing or ignoring defects.
•Impact: Deployment of buggy or insecure software.
•Example: Skipping security testing, leading to vulnerabilities in the final product.

13. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 13
11. Lack of Skilled Resources
•Problem: Inadequate technical expertise or experience in the team.
•Impact: Poor design, inefficient code, or delays in completing tasks.
•Example: Assigning a critical database design task to a team member unfamiliar with database
technologies.

14. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 14
12. Over-Reliance on Tools
•Problem: Over-dependence on tools without proper understanding or process alignment.
•Impact: Mismanagement or inefficiencies when tools fail to meet project needs.
•Example: Using project management software without customizing it to the team's workflow.

15. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 15
13. Stakeholder Conflicts
•Problem: Misaligned goals or priorities among stakeholders.
•Impact: Delays, frequent changes, and decision-making bottlenecks.
•Example: A marketing team demanding a feature that contradicts the technical feasibility agreed
upon by developers.

16. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 16
14. Failure to Adapt to Changes
•Problem: Inflexibility in accommodating new requirements or market trends.
•Impact: Software becomes obsolete or irrelevant upon release.
•Example: A project designed for desktop platforms only, ignoring the shift to mobile-first
applications.

17. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 17
15. Inadequate Documentation
•Problem: Lack of clear and comprehensive documentation for the project.
•Impact: Difficulties in maintenance, troubleshooting, or onboarding new team members.
•Example: A project delivered without proper API documentation, making future integration
cumbersome.

18. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 18
16. Project Abandonment
•Problem: Projects halted due to lack of interest, funding, or technical feasibility.
•Impact: Wasted resources and unmet objectives.
•Example: A startup running out of funds mid-way through a software product development
cycle.

19. 04/05/2025 DR. SWEETI SAH, ASSISTANT PROFESSOR, DEPT. OF COMPUTER ENG. 19
THANK YOU