- Paperback: 280 pages
- Publisher: Addison Wesley (31 January 2002)
- Language: English
- ISBN-10: 0201737213
- ISBN-13: 978-0201737219
- Product Dimensions: 18.5 x 1.8 x 23.1 cm
- Average Customer Review: Be the first to review this item
Amazon Bestsellers Rank:
#8,60,440 in Books (See Top 100 in Books)
- #1360 in Books > Textbooks & Study Guides > Higher Education Textbooks > Engineering > Industrial Engineering
- #2028 in Books > Textbooks & Study Guides > Higher Education Textbooks > Computer Science > Database Storage & Design
- #2710 in Books > Computing, Internet & Digital Media > Hardware & Handheld Devices
Software Project Management in Practice Paperback – Import, 31 Jan 2002
Customers who viewed this item also viewed
Customers who bought this item also bought
Aimed at developers and IT managers alike, Software Project Management in Practice offers an invaluable guide to using lightweight software processes in real projects. Filled with sample documents, this book can benefit any organization seeking to improve the ways it manages software.
In an era of ever tighter schedules, implementing a serious software process becomes even more difficult. This book ventures a simple argument: that the techniques for software process management used by InfoSys (a company with a "mature" software process) can be applied to other organizations. Packed with sample documents drawn from real projects, this book is also notable for its clear presentation and the absence of the theoretical and jargon-laden prose that can be found in many software engineering texts.
The author first looks at how to assess a company's software process using the Capability Maturity Model (CMM) and other schemes. Surprisingly, the tools at InfoSys (which earn high CMM marks) are not fancy case tools, but databases, spreadsheets, and Microsoft Project files. Its software process database, for example, allows new projects to reuse existing documents and expertise. After an overview of the modified waterfall model software process used at InfoSys, the author looks at techniques for estimating the size and scope of projects. Then it's on to quality planning. A consistent theme here is that metrics and statistical process control (SPC) should be used to track defects. The book then covers risk assessment and the structure of teams. A standout section on configuration management outlines the role for preserving builds and project documents at each stage of the game.
Later sections examine the actual implementation and deployment of software. The author's argument for peer review of code is a strong one. He details strategies for running design and code reviews (if even by a single person) to catch defects and improper designs, as well as tips for overcoming resistance to such practices.
Sample defect tracking and status for projects also gets its due. Sample documents (using spreadsheets and even the layout of disk directories) to store project information show that a simple approach can yield productive results. The author then shows how to analyze the patterns of defects in software, including how to use statistical techniques to spot out-of-control projects. The book closes with the ways in which a project postmortem (or "project closure analysis") can be used to spot what went wrong and to improve things the next time around.
For both those new to software process or for those who want to see some practical ideas for successful process in a fast-paced world, this concisely packaged title fills a valuable niche with its mix of current thinking on software process and excellent real-world examples. --Richard Dragan
Topics covered: Overview of mature software processes and project management; assessing process maturity with the Capability Maturity Model (CMM); Key Process Areas (KPAs); overview of successful project management at InfoSys (the author's company); the waterfall software development process; using process databases (reusing project management expertise); effort estimation (bottom-up, top-down, use case, and overall approaches); overall and detailed scheduling; procedural and quantitative approaches to quality management; quality goals; defect estimation and prevention; identifying and prioritizing risks; risk management planning (plus monitoring and tracking risks); overview of metrics and measurement (including statistical process control or SPC); logging and tracking defects; project management plans (managing teams); configuration management; project reviews for better project execution (including group and one-person reviews); overcoming the Not Around Here (NAH) syndrome; project tracking explained (including defect tracking, status reports, milestone analysis); defect analysis and prevention (plus Pareto and causal analysis); process monitoring and audit; project closure analysis; and sample software project management documents from real projects.
From the Back Cover
We often hear about software projects that are late, over budget, or unable to satisfy customer needs. Yet some organizations are able to manage project after project successfully with desired results. In this book, Pankaj Jalote looks at one such organization, Infosys Technologies, a highly regarded high-maturity organization, and details the processes it has in place to manage projects. Revealing exactly how Infosys operates, Jalote provides an excellent case study to guide project managers everywhere. The specific Infosys practices described reflect sound management principles and practices. They are also grounded in common sense, and can be incorporated into any organization’s software development operation easily.
With an actual software project from Infosys used as a running example, the author explains the key aspects of successful project management–from process planning through project monitoring and closure. The practices discussed are also compatible with the widely adopted Capability Maturity Model® (CMM®). In the end, readers will gain a practical framework for systematically improving the planning and execution of any software project.
In-depth coverage of the Infosys software project management process includes:
Many guidelines exist for achieving higher software process maturity. This book shows you how by example.
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter mobile phone number.
No customer reviews
|5 star (0%)|
|4 star (0%)|
|3 star (0%)|
|2 star (0%)|
|1 star (0%)|
Review this product
Most helpful customer reviews on Amazon.com
One would be better served picking up a copy of PMI's PMBOK to learn about coherent project management processes.
What I like is the way this book lays out the how's of project management in a complete, detailed manner, and how it takes those how's from theory to practical application by providing real cases and the author's own insights and experience. Unlike other books, no matter how well written, this one will give you the confidence that the approach can be done.
All of the critical success factors of a well managed project and the techniques for attaining them are there - excellent planning and estimating, scheduling, execution and control practices are provided. More importantly, this book shows how quality is interwoven into the approach, as well as key metrics and how to gather, manage and use them. Since this information is provided within the context of cases and real examples, readers who are serious about managing software projects will be struck by the realism and how to apply mature processes and practices during the project.
I also like the insights into InfoSys, which is one of the most highly respected consulting and integration firms in the world. Reading this book solely for competitive intelligence purposes is a valid reason. However, reading it to become a top software project manager who can deliver on time and schedule is an even better reason to read this book. It is one of the best written books on a discipline that is both difficult and has a spotty record when it comes to success. Following the practices in it will assure success.
The book explains sound methods and practices for SPM that as the author says "are grounded in common sense and supported by simple measures and analyses"
As in his previous books Dr. Jalote demystifies the CMM by providing the reader with a very pragmatic and simple view of how SPM must be carried out, of course you must be aware that all the methods, techniques, and practices will not work unless those are performed in orderly and disciplined way.