Software Project Management In Practice By Pankaj Jalote New!
The book operates on a simple premise: Software projects fail not because of bad programmers, but because of bad planning, poor risk management, and a lack of measurement.
The book is rooted in the belief that software project management is a distinct discipline, separate from general project management, due to the unique, intangible nature of software. It draws heavily from the Capability Maturity Model (CMM) and the Project Management Body of Knowledge (PMBOK), synthesizing them into a cohesive narrative that is accessible yet rigorous.
Finally, the book addresses the often-neglected phase of closure. It emphasizes the importance of post-project analysis, documentation, and lessons learned—crucial steps for organizational growth and knowledge retention. Software Project Management In Practice By Pankaj Jalote
| Book | Focus | Jalote's Differentiator | |------|-------|--------------------------| | The Mythical Man-Month (Brooks) | Philosophical principles | Jalote gives step-by-step processes . | | Software Project Survival Guide (McConnell) | Practical survival tactics | Jalote is more systematic/metrics-heavy. | | PMBOK (PMI) | Generic project management | Jalote is software-specific . | | Agile Estimating & Planning (Cohn) | Agile-only | Jalote covers plan-driven + hybrid. |
The "Practice" aspect shines here. Jalote provides templates for risk mitigation, monitoring, and contingency planning that are used in top-tier software factories in India and Silicon Valley. The book operates on a simple premise: Software
For a helpful overview or "article-style" summary, you can refer to this detailed review from ResearchGate or explore the key takeaways summarized below: Core Focus: The Infosys Case Study The book primarily uses Infosys Technologies
Veterans will find validation. Jalote codifies the "dark arts" of project recovery and stakeholder communication. His chapter on Project Tracking and Control provides metrics that actually matter (Earned Value Analysis, Defect Density) versus vanity metrics (Lines of Code written). Finally, the book addresses the often-neglected phase of
He emphasizes —you cannot manage what you cannot measure. Every process recommended is tied to a tangible outcome (e.g., schedule, defect rate, effort variance).
: The text revolves around the ACIC Project , a real-world case study used to illustrate planning, execution, and closure.
Pankaj Jalote is a highly respected figure in software engineering, formerly the Director of IIIT Delhi and a professor at IIT Kanpur. His books (especially An Integrated Approach to Software Engineering ) are standard texts in many academic curricula.