The Software Project Manager's Handbook: Principles That Work at WorkSoftware project managers and their team members work individually towards a common goal. This book guides both, emphasizing basic principles that work at work. Software at work should be pleasant and productive, not just one or the other. This book emphasizes software project management at work. The author's unique approach concentrates on the concept that success on software projects has more to do with how people think individually and in groups than with programming. He summarizes past successful projects and why others failed. Visibility and communication are more important than SQL and C. The book discusses the technical and people aspects of software and how they relate to one another. The first part of the text discusses four themes: (1) people, process, product, (2) visibility, (3) configuration management, and (4) IEEE Standards. These themes stress thinking, organization, using what others have built, and people. The second part describes the software management principles of process, planning, and risk management. Part three discusses software engineering principles, the technical aspects of software projects. The fourth part examines software practices giving practical meaning to the individual topics covered in the preceding chapters. The final part of this book continues these practical aspects by illustrating a sample project through seven distinctive documents. |
Contents
1 | 8 |
Four Basics That Work | 27 |
What Doesnt Work and Why | 39 |
Managing a Project Day by Day | 47 |
Part 2 | 95 |
33672E | 149 |
10 | 155 |
11 | 172 |
2 | 274 |
Integration and Testing | 291 |
3 | 306 |
Software Maintenance | 323 |
Part 4 | 343 |
Appendix B Configuration Management | 439 |
Configuration Management | 441 |
Structured Analysis and Design | 459 |
Common terms and phrases
Acme agile methods allocated baseline analysis basic black box testing build Capability Maturity Model Chapter chart CM person CM plan CM staff CMMI complete configuration management ConOps control gate cost create cycle decisions described design baseline diagram document earned value Emca entity errors estimate everything evolution executive sponsor extreme programming Figure functional baseline hardware high-level design input inspection ject lead customer low-level design meet ment modules Operations OPT project OPT system organization perform Personal Software Process phase problem programmers project manager project plan project team quadrant risk management schedule shows Software Development software maintenance software project software system software units solution source code Specification spiral SPMP spreadsheet status subroutine subsystem task Test Plan testers tion User Need V-chart visibility techniques ware waterfall Weinberg white box testing Write Test Plan Write test procedure
References to this book
Software-Qualitätsmanagement in der Praxis: Software-Qualität durch Führung ... Ernest Wallmüller No preview available - 2001 |
Challenges in Information Technology Management Man-Chung Chan,Ronnie Cheung,James N. K. Liu No preview available - 2008 |