UNIT 1: INTRODUCTION TO SOFTWARE PROJECT

MANAGEMENT

1. Introduction
Welcome and Course Overview:
o Briefly introduce the course and its objectives.
o Explain the importance of software project management in the IT
industry.
o Mention the relevance of this course to BIT students.
• Icebreaker Activity:
o A quick activity to get students engaged, like sharing past project
experiences (if any).
2. What is a Project?
• Definition of a Project:
o "A temporary endeavor undertaken to create a unique product,
service, or result."
o Key characteristics:
▪ Temporary: Has a definite beginning and end.
▪ Unique: Produces something distinct.
▪ Objective-driven: Aimed at achieving specific goals.
• Examples of Projects:
o Construction of a bridge
o Developing a new software application
o Organizing a conference
o Launching a marketing campaign
• Project Constraints (The Triple Constraint):
 o Time: The duration to complete the project.
o Cost: The resources required (budget).
o Scope: The work that needs to be done.
o Quality: The standard of the deliverables.
o Discuss how these constraints are interrelated and how changes in
one affect the others.
3. Software Projects vs. Other Types of Projects
• Differences:
o Intangibility: Software is not a physical product.
o Complexity: Software systems can be highly complex.
o Rapid Technological Change: The software industry evolves quickly.
o Requirement Volatility: Software requirements are more prone to
changes.
o High Failure Rates: Historically, software projects have had a higher
failure rate compared to other project types.
• Specific Challenges in Software Projects:
o Difficulty in accurately estimating development time and cost.
o Managing evolving user requirements.
o Ensuring software quality and reliability.
o Dealing with technical risks and uncertainties.
o Team collaboration and communication in distributed
environments.
4. Importance of Project Management
• Why is Project Management Important?
o Ensures projects are completed successfully (on time, within
budget, and meeting objectives).
 o Improves efficiency and productivity.
o Manages risks and uncertainties.
o Facilitates effective communication and collaboration.
o Enhances software quality.
o Increases stakeholder satisfaction.
o Drives innovation and competitive advantage.
• Consequences of Poor Project Management:
o Cost overruns
o Schedule delays
o Scope creep
o Poor quality
o Project failure
o Damaged reputation
• Case Studies:
o Briefly discuss examples of successful and failed software projects
to illustrate the impact of project management. (Find relevant,
short case studies)
5. Activities Covered by Software Project Management (30 minutes)
• Key Activities:
o Planning: Defining objectives, scope, activities, resources, and
schedule.
o Organizing: Structuring the project team and allocating resources.
o Staffing: Recruiting and managing the project team.
o Directing/Leading: Providing guidance, motivation, and direction to
the team.
 o Controlling: Monitoring progress, tracking performance, and taking
corrective actions.
o Risk Management: Identifying, analyzing, and responding to
project risks.
o Quality Management: Ensuring that the software meets the
required quality standards.
o Communication Management: Managing the flow of information
among stakeholders.
o Change Management: Handling changes to the project scope,
schedule, or budget.
• Activity Breakdown:
o Discuss each activity in detail, providing examples of how they are
applied in software projects.
• Process Groups:
o Relate the activities to the five project management process groups:
▪ Initiating
▪ Planning
▪ Executing
▪ Monitoring and Controlling
▪ Closing
6. Plans, Methods, and Methodologies (30 minutes)
• Definitions:
o Plan: A detailed scheme, program, or strategy worked out
beforehand for the accomplishment of a project. (e.g., Project
Management Plan, Risk Management Plan, Quality Management
Plan)
 o Method: A way of doing something, a systematic procedure,
technique, or process employed in the project. (e.g., Use Case
method, Agile method)
o Methodology: A system of practices, techniques, procedures, and
rules used by those who work in a discipline. It is a framework of
methods. (e.g., Waterfall methodology, Scrum methodology)
• Hierarchy:
o Methodology > Method > Plan
• Examples in Software Project Management:
o Methodology: Waterfall, Agile (Scrum, Kanban), Iterative, Spiral
o Method: Requirements gathering techniques (e.g., interviews,
prototyping), testing methods, risk assessment methods.
o Plan: Project schedule, budget plan, test plan.
• Discussion:
o Discuss different software development methodologies and their
advantages and disadvantages.
7. What is Management?
• Definition of Management:
o The process of planning, organizing, leading, and controlling the
efforts of organizational members and using all other organizational
resources to achieve stated organizational goals.
o Key functions of management:
▪ Planning
▪ Organizing
▪ Leading
▪ Controlling
• Management Skills:
 o Technical Skills
o Human/Interpersonal Skills
o Conceptual Skills
• Relevance to Software Project Management:
o Explain how general management principles apply to managing
software projects.
8. Management Control (15 minutes)
• Definition of Management Control:
o The systematic process of regulating organizational activities to
make them consistent with the expectations established in plans,
targets, and standards of performance.
• Elements of Management Control
o Setting standards
o Measuring performance
o Comparing performance against standards
o Taking corrective action
• Control in Software Projects:
o Scope Control
o Schedule Control
o Cost Control
o Quality Control
• Tools and Techniques for Management Control
o Gantt Charts
o Earned Value Management
o Status Reports
9. Traditional vs. Modern Project Management Practices (15 minutes)
• Traditional Project Management:
o Plan-driven approach (e.g., Waterfall).
o Linear, sequential phases.
o Emphasis on detailed upfront planning.
o Change is resisted.
o Suitable for projects with well-defined requirements.
• Modern Project Management:
o Adaptive approach (e.g., Agile).
o Iterative and incremental development.
o Emphasis on flexibility and collaboration.
o Change is embraced.
o Suitable for projects with evolving requirements.