SOFTWARE PROJECT MANAGEMENT

UNIT 1 Detailed Notes

1. Activities Methodologies
Activities in Software Project Management:
• Project Planning and Tracking: Defining project scope, objectives, deliverables, and
schedules. Tracking involves monitoring progress against the plan using tools like Gantt
charts and project management software4.
• Resource Management: Allocating and managing resources such as personnel, tools, and
budgets to ensure project needs are met efficiently4.
• Scope Management: Defining and controlling what is included and excluded from the
project to prevent scope creep4.
• Estimation Management: Estimating time, cost, and resources required for project tasks and
deliverables4.
• Risk Management: Identifying, analyzing, and mitigating risks that could impact project
success4.
• Quality Management: Ensuring that the project deliverables meet the required standards
and specifications4.
• Communication Management: Facilitating effective information flow among stakeholders
and team members4.
Methodologies:
• Waterfall: A linear, sequential approach where each phase must be completed before the
next begins. Best for projects with well-defined requirements and low uncertainty123.
• Agile: An iterative and incremental methodology emphasizing flexibility, collaboration, and
customer feedback. Suited for projects with evolving requirements123.
• Scrum: A subset of Agile, using short sprints (1-2 weeks) and daily stand-ups to deliver
incremental value. Ideal for small, cross-functional teams12.
• Kanban: Focuses on visualizing work, limiting work in progress, and optimizing flow. Suitable
for continuous delivery environments3.
• Lean: Aims to maximize value by eliminating waste and improving processes3.
• PMBOK (Project Management Body of Knowledge): A set of best practices and guidelines
covering all phases of the project lifecycle, widely recognized for standardizing project
management12.

2. Categorization of Software Projects

Software projects can be categorized based on several criteria:
• By Size: Small, medium, or large projects, depending on team size, budget, and complexity.
• By Complexity: Simple (few modules, straightforward requirements) to complex (many
interdependent modules, dynamic requirements).
• By Application Domain: Business applications, embedded systems, web applications, mobile
apps, scientific computing, etc.
 • By Development Approach: New development, maintenance, enhancement, or re-
engineering projects.
• By Delivery Model: In-house development, outsourced, or hybrid projects.
• By Methodology Used: Waterfall, Agile, Scrum, etc.
Each category influences the choice of management approach, tools, and risk management
strategies.

3. Management Principles
Key management principles in software project management include:
• Clear Objectives: Define and communicate project goals and success criteria.
• Planning and Organization: Structure the project, assign roles, and develop detailed plans
for scope, schedule, and resources.
• Effective Communication: Maintain open channels for information sharing among all
stakeholders.
• Risk Management: Identify, assess, and plan for risks proactively.
• Resource Optimization: Allocate and utilize resources efficiently to avoid bottlenecks.
• Quality Assurance: Implement processes to ensure deliverables meet required standards.
• Change Management: Control and document changes to prevent scope creep and maintain
project stability.
• Continuous Improvement: Regularly review performance, learn from outcomes, and refine
processes for future projects.
• Stakeholder Engagement: Involve stakeholders throughout the project to ensure their needs
are met.
• Project Closure: Ensure all deliverables are completed, lessons are documented, and
resources are released.

4. Project Portfolio Management

Project Portfolio Management (PPM) is the centralized management of multiple projects to achieve
strategic objectives. It involves:
• Project Selection: Evaluating and prioritizing projects based on alignment with organizational
goals, resource availability, and potential ROI.
• Resource Allocation: Distributing resources across projects to maximize value and minimize
conflicts.
• Risk Balancing: Assessing and balancing risks across the entire portfolio, not just individual
projects.
• Performance Monitoring: Tracking progress, budgets, and outcomes at the portfolio level.
• Strategic Alignment: Ensuring all projects contribute to the organization’s long-term strategy
and objectives.
PPM helps organizations optimize project investments, balance competing demands, and adapt to
changing business priorities.

5. Risk Evaluation
Risk evaluation is the process of assessing identified risks to determine their likelihood and potential
impact on project objectives. Steps include:
• Risk Identification: List all possible risks that could affect the project.
 • Probability Assessment: Estimate the likelihood of each risk occurring (e.g., low, medium,
high).
• Impact Assessment: Evaluate the potential consequences if the risk materializes (e.g., cost
overruns, schedule delays, quality issues).
• Risk Prioritization: Rank risks using a risk matrix or probability-impact chart, focusing on
those with high probability and high impact.
• Quantitative Analysis: Assign numerical values to probability and impact to calculate risk
exposure (Risk Exposure = Probability × Impact).
• Documentation: Record findings in a risk register, including mitigation strategies and
monitoring plans.
• Review and Update: Regularly revisit risk evaluations as the project progresses and new risks
emerge.
Effective risk evaluation enables project managers to allocate resources to the most critical risks and
develop contingency plans, increasing the likelihood of project success.

UNIT 2 Detailed Notes

1. Software Process
A software process is a set of related activities and tasks that lead to the production of a software
product. It defines the structured sequence of steps followed during software development, ensuring
systematic progress from requirements to deployment and maintenance.
Key Phases of a Typical Software Process:
• Requirement Analysis: Gathering and analyzing user needs and system requirements.
• Design: Creating architecture and detailed designs for the system.
• Implementation (Coding): Actual development and coding of the software.
• Testing: Verifying that the software meets requirements and is free of defects.
• Deployment: Releasing the software to users.
• Maintenance: Ongoing support, bug fixes, and enhancements.
Purpose:
A well-defined software process improves predictability, quality, and management of software
projects, reducing risks and ensuring deliverables meet stakeholder expectations1234.

2. Choice of Process Model

Selecting the right software process model is crucial for project success. The choice depends on
project requirements, complexity, team size, customer involvement, and expected changes.
Common Software Process Models:
• Waterfall Model: Linear and sequential; best for projects with well-defined, stable
requirements. Changes are difficult once a phase is completed.
• V-Model: Extension of Waterfall, emphasizing verification and validation at each stage.
• Iterative and Incremental Model: Develops software in small increments, allowing feedback
and refinement at each iteration.
• Spiral Model: Combines iterative development with risk analysis; suitable for large, high-risk
projects.
 • Prototype Model: Builds a prototype for user feedback before final development; useful for
unclear requirements.
• Agile Model: Iterative and incremental, with frequent delivery, customer collaboration, and
adaptability to change.
• DevOps Model: Integrates development and operations for continuous delivery and
automation124567.
Factors Influencing Model Choice:
• Project size and complexity
• Requirement stability
• Customer involvement
• Risk tolerance
• Time-to-market needs
• Team experience

3. Rapid Application Development (RAD)

Rapid Application Development (RAD) is a software process model focused on quick development
and frequent user feedback. It emphasizes rapid prototyping over long drawn-out development
cycles.
Key Features:
• Phases: Requirements planning, user design, construction, and cutover.
• Prototyping: Early and continuous creation of working models for user feedback.
• User Involvement: High, with frequent interactions and feedback.
• Iterative Development: Components are developed in parallel and integrated quickly.
Advantages:
• Faster delivery of functional software.
• Better alignment with user needs due to frequent feedback.
• Flexibility to incorporate changes.
Disadvantages:
• May not be suitable for large, complex projects.
• Requires strong and continuous user involvement.
• Less attention to scalability and maintainability in early stages25.

4. COSMIC Full Function Point

COSMIC (Common Software Measurement International Consortium) Full Function Point is a
standardized method for measuring a software project's functional size.
Key Concepts:
• Measures the amount of functionality delivered to the user, independent of technology or
implementation.
• Based on four data movement types: Entry, Exit, Read, and Write.
• Each data movement is counted as a function point.
Process:
• Identify functional user requirements.
• Break down the system into functional processes.
• For each process, count the number of Entries (inputs), Exits (outputs), Reads (data
retrievals), and Writes (data storage).
 • The sum gives the functional size in COSMIC Function Points.
Advantages:
• Technology-independent, suitable for various software domains.
• Useful for project estimation, benchmarking, and productivity analysis.
Applications:
• Project estimation and planning.
• Productivity measurement.
• Benchmarking across projects and organizations.

UNIT 3 Detailed Notes

1. Project Schedules
A project schedule is a detailed plan that outlines project activities, deliverables, milestones, and
timelines. It serves as a roadmap for executing and controlling the project, helping teams track
progress, allocate resources, and manage dependencies267.
Key Elements:
• Task List: All activities required to complete the project.
• Dependencies: Logical relationships between tasks (e.g., Task B cannot start until Task A
finishes).
• Milestones: Significant events or checkpoints.
• Timeline: Start and end dates for tasks and the overall project.
• Resource Allocation: Assignment of personnel, equipment, and materials to tasks.
Common Scheduling Tools:
• Gantt Charts: Visualize tasks, durations, and dependencies.
• Network Diagrams: Show task sequencing and dependencies.
• Project Management Software: Automates scheduling, tracking, and reporting5.

2. Backward and Forward Pass

Forward Pass:
A scheduling technique used to determine the earliest possible start (ES) and finish (EF) times for
each activity, moving from the beginning to the end of the project network.
• Earliest Start (ES): The earliest time an activity can begin, considering predecessor activities.
• Earliest Finish (EF): EF = ES + Activity Duration.
Backward Pass:
Calculates the latest possible start (LS) and finish (LF) times for each activity, moving from the end of
the project back to the start.
• Latest Finish (LF): The latest time an activity can finish without delaying the project.
• Latest Start (LS): LS = LF – Activity Duration.
Purpose:
These calculations help identify float (slack) and determine the critical path, ensuring that project
deadlines are met5.

3. Critical Path (CPM)

The Critical Path Method (CPM) is a project scheduling technique that identifies the longest
sequence of dependent tasks (the critical path) that determines the shortest possible project
duration138.
Key Points:
• Critical Path: The path with zero float; any delay in these tasks will delay the project.
• Float (Slack): The amount of time a task can be delayed without affecting the project end
date.
• CPM Steps:
1. List all activities and durations.
2. Identify dependencies.
3. Draw the network diagram.
4. Perform forward and backward pass calculations.
5. Identify the critical path.
Benefits:
Helps prioritize tasks, allocate resources efficiently, and focus management attention on activities
that could delay the project5.

4. PERT Technique
Program Evaluation and Review Technique (PERT) is a project management tool used to estimate
project duration by analyzing the time required to complete each task, especially when there is
uncertainty138.
Key Features:
• Three-Point Estimation: For each activity, estimate:
• Optimistic Time (O): Minimum possible duration.
• Most Likely Time (M): Most probable duration.
• Pessimistic Time (P): Maximum possible duration.
• Expected Time (TE):
TE=O+4M+P6TE=6O+4M+P
• PERT Chart: A network diagram showing task sequences and dependencies.
Uses:
PERT is valuable for complex projects with uncertain activity durations, enabling better risk
assessment and schedule planning.

5. Risk Management and Planning

Risk Management in project scheduling involves identifying, analyzing, prioritizing, and planning for
potential events that could negatively impact the project schedule5.
Steps:
• Risk Identification: List possible risks (e.g., resource shortages, technical challenges, delays).
• Risk Analysis: Assess the probability and impact of each risk.
• Risk Prioritization: Focus on high-probability, high-impact risks.
• Risk Response Planning: Develop mitigation, avoidance, transfer, or acceptance strategies.
• Risk Monitoring: Continuously track risks and update plans as the project progresses.
Purpose:
Effective risk management ensures that potential schedule disruptions are anticipated and addressed
proactively, increasing the likelihood of project success.
UNIT 4 Detailed Notes

1. Framework for Management and Control

A project management framework provides a structured set of processes, tasks, and tools to guide a
project from initiation to closure12357. It ensures consistency, accountability, and efficiency in
managing projects of any scale.
Key Components:
• Project Lifecycle:
Five main phases—Initiation, Planning, Execution, Performance Monitoring, and Project
Closure35.
• Initiation: Define objectives, scope, and risks.
• Planning: Develop detailed schedules, assign tasks, and allocate resources.
• Execution: Carry out project tasks and deliverables.
• Performance Monitoring: Track progress, review performance, and adjust plans as
needed.
• Closure: Finalize deliverables, complete documentation, and release resources.
• Project Control Cycle:
Ongoing process of monitoring and controlling the project to ensure adherence to timelines,
budgets, and scope. Involves regular status updates, performance reviews, and proactive
management of deviations123.
• Tools and Templates:
Use of project plans, Gantt charts, risk logs, and performance templates to standardize and
streamline project management activities136.
Benefits:
• Provides clarity on roles and responsibilities.
• Ensures alignment with organizational goals.
• Facilitates communication and risk management.
• Enables continuous improvement and learning57.

2. Cost Monitoring
Cost monitoring involves tracking project expenditures and comparing them against the budget to
ensure the project remains financially on track.
Key Activities:
• Budget Baseline: Establish an approved budget for all project activities.
• Ongoing Tracking: Record actual costs as the project progresses.
• Variance Analysis: Compare actual costs with planned costs to identify deviations.
• Forecasting: Predict future spending trends based on current data.
• Reporting: Regularly update stakeholders on financial status.
Purpose:
• Detects cost overruns early.
• Enables corrective actions to control expenses.
• Supports informed decision-making and accountability.

3. Earned Value Analysis

Earned Value Analysis (EVA) is a quantitative technique for measuring project performance and
progress in terms of scope, time, and cost.
Key Metrics:
• Planned Value (PV): Budgeted cost of work scheduled.
• Earned Value (EV): Budgeted cost of work actually completed.
• Actual Cost (AC): Actual cost incurred for completed work.
Performance Indicators:
• Cost Variance (CV): CV=EV−ACCV=EV−AC
Positive CV means under budget; negative means over budget.
• Schedule Variance (SV): SV=EV−PVSV=EV−PV
Positive SV means ahead of schedule; negative means behind.
• Cost Performance Index (CPI): CPI=EVACCPI=ACEV
CPI > 1 is favorable.
• Schedule Performance Index (SPI): SPI=EVPVSPI=PVEV
SPI > 1 is favorable.
Purpose:
• Provides objective data on project health.
• Enables early detection of schedule and cost issues.
• Supports proactive management and forecasting.

4. Change Control & Software Configuration Management

Change Control is a formal process for managing modifications to project scope, deliverables, or
processes.
Steps:
• Change Request: Submit a formal request for change.
• Impact Analysis: Assess the effect on schedule, cost, and quality.
• Approval/Denial: Review and approve or reject the change.
• Implementation: Make the approved change.
• Documentation: Record the change and update project documents.
Software Configuration Management (SCM):
• Systematically manages changes to software artifacts (code, documents, test cases).
• Ensures consistency, traceability, and integrity throughout the software lifecycle.
• Involves version control, baseline management, and audit trails.
Purpose:
• Prevents unauthorized or uncontrolled changes.
• Maintains project stability and quality.
• Facilitates collaboration and accountability.

5. Contract Management
Contract management involves overseeing agreements with vendors, suppliers, or partners to
ensure all terms and obligations are met.
Key Activities:
• Contract Creation: Define scope, deliverables, timelines, and payment terms.
• Negotiation: Agree on terms and resolve ambiguities.
• Execution: Ensure compliance with contract terms during project execution.
 • Monitoring: Track deliverables, milestones, and payments.
• Amendments: Manage changes or disputes as needed.
• Closure: Confirm all obligations are fulfilled and formally close the contract.
Purpose:
• Minimizes legal and financial risks.
• Ensures clarity and mutual understanding between parties.
• Supports successful delivery of outsourced or procured components.

In summary:
Unit 4 covers the structured approach to managing and controlling projects, with an emphasis on
frameworks, cost and value tracking, controlled change, configuration management, and effective
contract oversight—all critical for project success123567.

UNIT 5 Detailed Notes

1. Best Method of Staff Selection

Staff selection is the process of choosing the most suitable candidate for a job from a pool of
applicants, ensuring a good match between organizational needs and candidate abilities. The best
selection methods combine multiple techniques for a holistic assessment.
Key Steps and Methods:
• Preliminary Interviews: Initial screening to eliminate candidates who do not meet minimum
criteria (skills, education, experience)14.
• Application Blanks: Candidates fill out forms detailing qualifications, experience, and other
relevant data14.
• Skills Assessments: Objective tests to evaluate technical and soft skills, such as coding
challenges for tech roles25.
• Structured Interviews: Standardized questions asked to all candidates for consistency and
fairness25.
• Behavioral Interviews: Assess how candidates handled situations in the past to predict
future performance5.
• Work Samples/Job Trials: Candidates complete tasks similar to the actual job to
demonstrate practical ability25.
• Psychometric Testing: Evaluates personality traits, cognitive abilities, and cultural fit5.
• Reference Checks: Verifies past performance and reliability67.
• Panel Interviews: Multiple interviewers assess the candidate from different perspectives5.
Best Practices:
• Use a combination of skills assessments and structured interviews for a comprehensive
evaluation.
• Focus on both technical and soft skills, as soft skills are often key predictors of long-term
success25.
• Ensure fairness and objectivity by standardizing evaluation criteria.

2. The Oldham and Hackman Job Characteristics

The Oldham and Hackman Job Characteristics Model identifies five core job dimensions that
influence employee motivation, satisfaction, and performance:
1. Skill Variety: The degree to which a job requires a range of different activities and skills.
2. Task Identity: The extent to which a job involves completing a whole, identifiable piece of
work.
3. Task Significance: The impact of the job on others, both inside and outside the organization.
4. Autonomy: The level of freedom, independence, and discretion the employee has in
scheduling work and determining procedures.
5. Feedback: The degree to which carrying out work activities provides direct and clear
information about performance.
Application:
Jobs designed with these characteristics enhance motivation, increase job satisfaction, and improve
performance.

3. Health and Safety

Health and safety in software project management refers to creating a work environment that
protects employees from physical and psychological harm.
Key Aspects:
• Ergonomics: Proper workstation setup to prevent repetitive strain injuries.
• Workplace Safety: Ensuring fire safety, electrical safety, and emergency preparedness.
• Mental Health: Addressing stress, workload management, and providing support for mental
well-being.
• Legal Compliance: Adhering to occupational health and safety regulations.
Benefits:
Promotes well-being, reduces absenteeism, increases productivity, and ensures compliance with
laws.

4. Communication Plans and Leadership

Communication Plans:
• Define how information will be shared among stakeholders and team members.
• Specify communication methods (meetings, emails, reports), frequency, and responsibilities.
• Ensure everyone is informed, aligned, and able to provide feedback.
Leadership:
• Provides vision, direction, and motivation to the team.
• Facilitates decision-making, conflict resolution, and team development.
• Effective leaders adapt their style to team needs, foster collaboration, and drive project
success.
Importance:
Clear communication and strong leadership are critical for team cohesion, timely decision-making,
and successful project outcomes.

5. Stress
Stress in project teams can arise from tight deadlines, heavy workloads, unclear roles, or
interpersonal conflicts.
Sources of Stress:
 • Unrealistic deadlines or expectations.
• Lack of control or autonomy.
• Poor communication or leadership.
• Job insecurity or organizational change.
Effects:
Reduced productivity, increased errors, absenteeism, and employee turnover.
Management Strategies:
• Set realistic goals and deadlines.
• Encourage work-life balance and provide support.
• Foster open communication and feedback.
• Provide resources for stress management (e.g., counseling, wellness programs).
Conclusion:
Managing stress is essential for maintaining team health, morale, and sustained project
performance.