Goals of Project Management & Success Criteria

Lecture 2 examines the core goals and success criteria of software project management. Successful project completion requires meeting stakeholder requirements, delivering functionality within committed deadlines, maintaining expenditures within allocated budgets, and adhering to strict software quality standards. The lecture analyzes project success metrics beyond simple delivery, evaluating user adoption, business value generation, and client satisfaction. Students investigate project life cycle phases: conceptualization, planning, execution, monitoring, and project closeout. The lecture emphasizes why software projects encounter unique failure modes due to product intangibility, volatile requirements, and rapid technological obsolescence. Key concepts such as configuration item identification, version control baselines, and formal change control board procedures are thoroughly analyzed. The lecture details algorithmic cost estimation models including COCOMO and Function Point Analysis to produce reliable effort forecasts. Structured decomposition methods are demonstrated using the Work Breakdown Structure to enforce the comprehensive one hundred percent rule. Network diagramming techniques such as CPM and PERT provide deterministic and probabilistic insights into critical path float times. Risk mitigation, monitoring, and management plans are formulated to identify technical, operational, and business exposure early in the lifecycle. Software quality assurance audits and formal technical reviews are presented as indispensable instruments for defect detection and process compliance. Organizational structures, including functional, projectized, and matrix configurations, are contrasted regarding project manager authority and team accountability. Team dynamics and collaborative leadership styles are analyzed to overcome Brooks's Law and foster high-performing software development cultures. The curriculum traces the evolutionary transition from traditional linear sequential lifecycles to iterative and risk-driven development paradigms. Practical guidance on utilizing project management software tools like Microsoft Project streamlines baseline tracking and resource leveling. Detailed inspections of post-implementation verification, user acceptance testing, and delivery milestones guarantee transparent project commissioning. Software maintenance categories, spanning corrective, adaptive, perfective, and preventive actions, are examined to sustain long-term system value. Measurement baselines and key performance indicators enable objective variance analysis across cost, schedule, and scope dimensions. Strategic trade-offs among project constraints illustrate how adjustments to scope or resources directly influence software reliability and delivery timelines.