JAWAHARLAL NEHRU TECHNOLOGICAL UNIVERSITY HYDERABAD B.Tech IV SOFTWARE PROJECT MANAGEMENT Previous Question Paper (March - 2021 - R15)

Software Project Management (SPM) involves the planning, monitoring, and control of the software development process to deliver a quality product within time and budget. The core activities include:

• Project Planning: Defining the project scope, objectives, and deliverables. This includes estimating effort, cost, and duration, and creating a schedule.
• Resource Management: Identifying and allocating the necessary human resources, hardware, and software tools required for the project.
• Risk Management: Identifying potential risks that could impact the project, assessing their probability and impact, and developing mitigation strategies.
• Monitoring and Control: Tracking the actual progress against the planned schedule and budget. If deviations occur, corrective actions are taken to bring the project back on track.
• Quality Management: Ensuring the software meets the specified requirements and adheres to quality standards through reviews, testing, and audits.
• Configuration Management: Managing changes to the software artifacts (code, documentation, requirements) throughout the project lifecycle to ensure consistency.
• Communication Management: Facilitating effective information flow between stakeholders, team members, and clients to ensure alignment.
• Project Closure: Formally closing the project, which involves final documentation, client sign-off, and performing a post-project review to capture lessons learned.

Software projects frequently encounter challenges that lead to failure or delays. Key problems include:

• Unclear or Changing Requirements: Often, stakeholders do not have a clear vision, or requirements evolve during development, leading to scope creep and rework.
• Inaccurate Estimation: Underestimating the complexity, effort, or time required for tasks often results in missed deadlines and budget overruns.
• Poor Communication: Lack of transparency between the development team and clients or within the team itself leads to misunderstandings, integration issues, and low morale.
• Technical Debt: Prioritizing speed over code quality can lead to a accumulation of technical debt, making future maintenance difficult and expensive.
• Inadequate Risk Management: Failing to anticipate technical or environmental risks means the team is often caught unprepared when issues arise, leading to reactive rather than proactive management.
• Resource Constraints: High turnover of skilled personnel or the unavailability of critical hardware/software tools can significantly stall project momentum.
• Testing and Quality Issues: Inadequate testing phases or poor quality assurance processes often result in software that is buggy or fails to meet user expectations upon delivery.