Software Project Management

 1. Define software project management

Software Project Management (SPM) is the process of planning, organizing, monitoring, and controlling software projects.
It ensures that software is delivered on time, within budget, and meets quality standards and user requirements.

 2. List the symptoms of the software crisis

The "software crisis" refers to chronic problems in software development. Symptoms include:

1. Projects running over time
   
   

2. Projects exceeding budget
   
   

3. Poor software quality
   
   

4. Failure to meet user requirements
   
   

5. Difficulties in maintenance and scalability
   
   

6. High defect rates
   
   

7. Low user satisfaction
   
   

8. Unclear specifications and frequent changes
   
   

3. Analyze the key factors that contribute to the software crisis

1. Rapidly changing technology
   
   

2. Poor project planning
   
   

3. Inadequate requirements gathering
   
   

4. Lack of user involvement
   
   

5. Poor communication among stakeholders
   
   

6. Underestimation of time and resources
   
   

7. Lack of skilled personnel
   
   

8. Ineffective project management practices
   
   

 4. List the conditions in which a project generally exhibits

A software project typically exhibits:

1. A clear start and end date
   
   

2. Defined goals and objectives
   
   

3. Specific deliverables
   
   

4. Constraints on time, cost, and scope
   
   

5. A team of resources (people, tools, technology)
   
   

6. A degree of risk and uncertainty
   
   

7. A unique product or service as an outcome
   
   

 5. Describe the two types of software projects

There are two main types:

1. Development Projects – Building new software systems from scratch.
   
   

2. Maintenance Projects – Modifying or enhancing existing software (bug fixes, upgrades, support).
   
   

 6. List the project management activities

Key SPM activities include:

1. Project planning
   
   

2. Effort estimation
   
   

3. Scheduling
   
   

4. Resource allocation
   
   

5. Risk management
   
   

6. Quality assurance
   
   

7. Monitoring and control
   
   

8. Communication and reporting
   
   

9. Configuration management
   
   

10. Project closure
    
    

 7. Analyze the responsibilities of a project manager

A software project manager is responsible for:

1. Planning and scheduling project tasks
   
   

2. Estimating cost, effort, and resources
   
   

3. Monitoring progress and managing risks
   
   

4. Leading the team and resolving conflicts
   
   

5. Communicating with stakeholders
   
   

6. Ensuring quality standards are met
   
   

7. Managing scope, time, and budget
   
   

8. Reporting on progress and issues
   
   

9. Adapting to change
   
   

10. Closing the project successfully
    
    

 8. Describe the difference between PRINCE2 and PMBOK

Aspect

PRINCE2

PMBOK

Origin

UK (Government Standard)

USA (Developed by PMI)

Focus

Process-based method

Knowledge-based guide

Structure

Prescriptive, with defined processes

Flexible, with knowledge areas and processes

Certification

PRINCE2 Foundation & Practitioner levels

PMP (Project Management Professional)

Usage

Common in UK, Europe, government projects

Common in USA, global enterprises

Documents & Templates

Standard templates and roles defined

Allows customization based on project needs