Mehr lesen
Informationen zum Autor DWAYNE PHILLIPS has worked as a software and systems engineer with the U.S. government since 1980. He has a PhD in Electrical and Computer Engineering from Louisiana State University. Phillips is the coauthor, with Roy O'Bryan, of It Sounded Good When We Started (published by Wiley-IEEE Computer Society) and author of Image Processing in C as well as several dozen articles for computer magazines. Klappentext Software 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. Zusammenfassung Software 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. Inhaltsverzeichnis 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 Standa...
