The software project manager's handbook : (Record no. 74178)
[ view plain ]
| 000 -LEADER | |
|---|---|
| fixed length control field | 09086nam a2201189 i 4500 |
| 001 - CONTROL NUMBER | |
| control field | 5989544 |
| 005 - DATE AND TIME OF LATEST TRANSACTION | |
| control field | 20220712205811.0 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION | |
| fixed length control field | 151221s2004 nju ob 001 eng d |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| ISBN | 9780471677772 |
| -- | electronic |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| ISBN | 0471677779 |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| -- | paper |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| -- | |
| 100 1# - AUTHOR NAME | |
| Author | Phillips, Dwayne, |
| 245 14 - TITLE STATEMENT | |
| Title | The software project manager's handbook : |
| Sub Title | principles that work at work / |
| 250 ## - EDITION STATEMENT | |
| Edition statement | 2nd ed |
| 300 ## - PHYSICAL DESCRIPTION | |
| Number of Pages | 1 PDF (450 pages). |
| 490 1# - SERIES STATEMENT | |
| Series statement | Practitioners ; |
| 505 0# - FORMATTED CONTENTS NOTE | |
| Remark 2 | Preface -- Part 1 -- 1 What Makes a Good Software Manager? -- 1.1 People Perspective -- 1.2 Business Perspective -- 1.3 Process Perspective -- 1.4 Key Thoughts in This Chapter -- References -- 2 Four Basics That Work -- 2.1 People, Process, and Product -- 2.2 Visibility -- 2.3 Configuration Management -- 2.4 Standards -- 2.5 Key Thoughts in This Chapter -- References -- 3 What Doesn't Work and Why -- 3.1 When the 3Ps Are Out of Balance -- 3.2 When There's Not Enough Visibility -- 3.3 When Configuration Management is Missing or Abused -- 3.4 When Standards are Dismissed -- 3.5 Key Thoughts in This Chapter -- Reference -- 4 Managing a Project Day by Day -- 4.1 Balancing the 3Ps to Create a Good Environment -- 4.2 Visibility: Project Control in a Simple Equation -- 4.3 CM: Managing Baselines with Milestones -- 4.4 Looking to Standards for Help -- 4.5 Key Thoughts in This Chapter -- References -- Part 2 -- 5 Requirements -- 5.1 Balancing the 3Ps: Requirements Analysis, Documentation, and Management -- 5.2 Visibility: Making Requirements Known -- 5.3 Using CM -- 5.4 Using Standards -- 5.5 Key Thoughts in this Chapter -- References -- 6 Planning -- 6.1 Elements of a Good Plan -- 6.2 Balancing the 3Ps: Selecting the Process -- 6.3 Making the Project Visible: Planning Techniques -- 6.4 Making the Project Visible: Estimating Techniques -- 6.5 Configuration Management -- 6.6 Standards -- 6.7 Key Thoughts in this Chapter -- References -- 7 Risk Management -- 7.1 A Task Overview -- 7.2 Balancing The 3Ps: Uncertainty and Choice -- 7.3 Making Risk Visible -- 7.4 Other Ways to Manage Risk -- 7.5 Configuration Management -- 7.6 Using Standards -- 7.7 Key Thoughts in this Chapter -- References -- Part 3 -- 8 Design -- 8.1 The Challenge of the 3Ps -- 8.2 Visibility-Expressing the Design -- 8.3 Design in the Code -- 8.4 Design and Process -- 8.5 Designing with COTS -- 8.6 Configuration Management -- 8.7 Standards: Writing the SDD -- 8.8 Key Thoughts in this Chapter -- References -- 9 Integration and Testing. |
| 505 8# - FORMATTED CONTENTS NOTE | |
| Remark 2 | 9.1 Some I&T Myths -- 9.2 Managing the 3Ps: People -- 9.3 Managing the 3Ps: Process -- 9.4 Visibility: Testing Techniques and Details -- 9.5 Configuration Management -- 9.6 Standards: Documenting the Test Plan -- 9.7 Key Thoughts in this Chapter -- References -- 10 Software Maintenance -- 10.1 What is Maintenance -- 10.2 Balancing the 3Ps: Managing the Maintainers -- 10.3 Balancing the 3Ps: Managing the Process -- 10.4 Balancing the 3Ps: Making the Most of the Product -- 10.5 Visibility: Understanding the Maintenance Stages -- 10.6 Configuration Management -- 10.7 Using Standards -- 10.8 Key Thoughts in this Chapter -- References -- Part 4 -- 11 Cookbook -- 11.1 Essentials -- 11.2 Opt: A Waterfall Project -- 11.3 System Upgrade: An Evolutionary Project -- 11.4 CTRAN: A Spiral Project -- 11.5 Other Software Projects -- 11.6 Key Thoughts in this Chapter -- References -- Appendix A Documents for the OPT Project -- A.1 OPT Executive Sponsor Memorandum -- A.2 OPT Project Context Document -- A.3 OPT Configuration Management Plan -- A.4 OPT Concept of Operations -- A.5 OPT Software Requirements Specification -- A.6 OPT Software Project Management Plan -- A.7 OPT Software Design Description -- Appendix B Configuration Management -- B.1 Will The Real CM Please Stand Up? -- B.2 The Main Ingredients -- B.3 Baselines -- B.4 CM Activities -- B.5 CM People -- B.6 CM Plan -- B.7 A CM Sketch -- B.8 Summary -- References -- Appendix C Structured Analysis and Design -- C.1 Structured Analysis -- C.2 Structured Design -- References -- Appendix D Annotated Bibliography -- D.1 Process -- D.2 Visibility -- D.3 People -- D.4 Journals -- Index -- About the Author. |
| 520 ## - SUMMARY, ETC. | |
| Summary, etc | Bring a new level of effectiveness to your software projectsRemember when creating software was fun? It could be again, if you use the methods in this book to help you plan and manage your project. In this new edition of The Software Project Manager's Handbook, expert Dwayne Phillips outlines the fundamental principles that project managers and software practitioners can use to help them succeed on any project. Success on software projects has more to do with how people think individually and in groups than with programming, asserts Phillips. In clear and concise steps, he shows software project managers and their team members how to manage projects effectively by paying attention to four basic principles: . Balancing people, process, and product . Making ideas visible . Applying configuration management properly . Using standards The book describes the requirements, planning, and risk management stages of the development cycle and examines the middle and late stages of development including design, test and integration, and maintenance. Phillips shares proven methods for dealing with common stumbling blocks for managers such as customers who want a voice in the design and endless test-fix cycles, and for planning maintenance so the customer is not left out of the process. Finally, the author examines past projects in detail-demonstrating why some projects were successful and why others failed. Phillips helps you apply these lessons with a "cookbook" formula that walks you step-by-step through a Waterfall, an Evolutionary, and a Spiral project.New material added to each chapter covers current issues including the role of process in software projects and the Agile Methods. The Software Project Manager's Handbook, Second Edition is the most innovative and up-to-date guide to making every software project a complete and painless success. |
| 650 #0 - SUBJECT ADDED ENTRY--SUBJECT 1 | |
| Subject | Computer software |
| General subdivision | Development. |
| 856 42 - ELECTRONIC LOCATION AND ACCESS | |
| Uniform Resource Identifier | https://ieeexplore.ieee.org/xpl/bkabstractplus.jsp?bkn=5989544 |
| 942 ## - ADDED ENTRY ELEMENTS (KOHA) | |
| Koha item type | eBooks |
| 264 #1 - | |
| -- | Los Alamitos, CA : |
| -- | IEEE Computer Society, |
| -- | 2004 |
| 264 #2 - | |
| -- | [Piscataqay, New Jersey] : |
| -- | IEEE Xplore, |
| -- | [2004] |
| 336 ## - | |
| -- | text |
| -- | rdacontent |
| 337 ## - | |
| -- | electronic |
| -- | isbdmedia |
| 338 ## - | |
| -- | online resource |
| -- | rdacarrier |
| 588 ## - | |
| -- | Description based on PDF viewed 12/21/2015. |
| 695 ## - | |
| -- | Algorithms |
| 695 ## - | |
| -- | Biographies |
| 695 ## - | |
| -- | Buildings |
| 695 ## - | |
| -- | Business |
| 695 ## - | |
| -- | Capability maturity model |
| 695 ## - | |
| -- | Companies |
| 695 ## - | |
| -- | Computational modeling |
| 695 ## - | |
| -- | Coordinate measuring machines |
| 695 ## - | |
| -- | Dictionaries |
| 695 ## - | |
| -- | Digital signal processing |
| 695 ## - | |
| -- | Documentation |
| 695 ## - | |
| -- | Electric breakdown |
| 695 ## - | |
| -- | Employment |
| 695 ## - | |
| -- | Encoding |
| 695 ## - | |
| -- | Estimation |
| 695 ## - | |
| -- | Floods |
| 695 ## - | |
| -- | Force |
| 695 ## - | |
| -- | Games |
| 695 ## - | |
| -- | Government |
| 695 ## - | |
| -- | Guidelines |
| 695 ## - | |
| -- | Hardware |
| 695 ## - | |
| -- | IEEE Computer Society |
| 695 ## - | |
| -- | Indexes |
| 695 ## - | |
| -- | Interviews |
| 695 ## - | |
| -- | Investments |
| 695 ## - | |
| -- | Local area networks |
| 695 ## - | |
| -- | Logic gates |
| 695 ## - | |
| -- | Maintenance engineering |
| 695 ## - | |
| -- | Manuals |
| 695 ## - | |
| -- | Microwave integrated circuits |
| 695 ## - | |
| -- | Monitoring |
| 695 ## - | |
| -- | Object oriented modeling |
| 695 ## - | |
| -- | Optimized production technology |
| 695 ## - | |
| -- | Organizing |
| 695 ## - | |
| -- | Personnel |
| 695 ## - | |
| -- | Planning |
| 695 ## - | |
| -- | Program processors |
| 695 ## - | |
| -- | Programming |
| 695 ## - | |
| -- | Project management |
| 695 ## - | |
| -- | Reliability |
| 695 ## - | |
| -- | Risk management |
| 695 ## - | |
| -- | Schedules |
| 695 ## - | |
| -- | Sections |
| 695 ## - | |
| -- | Software |
| 695 ## - | |
| -- | Software maintenance |
| 695 ## - | |
| -- | Software quality |
| 695 ## - | |
| -- | Software systems |
| 695 ## - | |
| -- | Spirals |
| 695 ## - | |
| -- | Standards |
| 695 ## - | |
| -- | Standards organizations |
| 695 ## - | |
| -- | Testing |
| 695 ## - | |
| -- | Tiles |
| 695 ## - | |
| -- | User interfaces |
| 695 ## - | |
| -- | Writing |
No items available.