Applied Software Project Management"O'Reilly Media, Inc.", 2005. gada 18. nov. - 324 lappuses "If you're looking for solid, easy-to-follow advice on estimation, requirements gathering, managing change, and more, you can stop now: this is the book for you."--Scott Berkun, Author of The Art of Project Management What makes software projects succeed? It takes more than a good idea and a team of talented programmers. A project manager needs to know how to guide the team through the entire software project. There are common pitfalls that plague all software projects and rookie mistakes that are made repeatedly--sometimes by the same people! Avoiding these pitfalls is not hard, but it is not necessarily intuitive. Luckily, there are tried and true techniques that can help any project manager. In Applied Software Project Management, Andrew Stellman and Jennifer Greene provide you with tools, techniques, and practices that you can use on your own projects right away. This book supplies you with the information you need to diagnose your team's situation and presents practical advice to help you achieve your goal of building better software. Topics include:
Jennifer Greene and Andrew Stellman have been building software together since 1998. Andrew comes from a programming background and has managed teams of requirements analysts, designers, and developers. Jennifer has a testing background and has managed teams of architects, developers, and testers. She has led multiple large-scale outsourced projects. Between the two of them, they have managed every aspect of software development. They have worked in a wide range of industries, including finance, telecommunications, media, nonprofit, entertainment, natural-language processing, science, and academia. For more information about them and this book, visit stellman-greene.com |
No grāmatas satura
1.–5. rezultāts no 86.
... important part of building better software is establishing transpar- ency. It's about making sure that, from the very beginning of the project, everyone agrees on what needs to be built, how long it will take to build it, what steps ...
... important thing that you can do to support them is to trust them and listen to them . However , you cannot blindly trust your team . You need to evaluate their ideas in relation to solid engineering principles . This is why the first ...
... important, and just as likely to be dismissed as unaffordable or “idealis- tic.” Yet software testing activities are ... important than any other; if any one of them has a serious error, that error will have an impact on the end product ...
... important activities in software development. Every discipline is equally important, and everyone on the team contributes equally to the project. A software requirements specification (SRS), for exam- ple, is no more important than the ...
... important. We use them every day in our own work, and we hope you find them as helpful and satisfying as we do. PART ONE Tools and Techniques 0. Chapter2CHAPTER TWO Software Project 10 CHAPTER ONE Part II: Using Project Management ...
Saturs
13 | |
15 | |
33 | |
53 | |
Reviews | 73 |
Software Requirements | 97 |
Design and Programming | 131 |
Software Testing | 171 |
Part Two | 201 |
Understanding Change | 203 |
Management and Leadership | 231 |
Managing an Outsourced Project | 255 |
Process Improvement | 277 |
Bibliography | 295 |
Index | 303 |
Citi izdevumi - Skatīt visu
Applied Software Project Management Andrew Stellman,Jennifer Greene Priekšskatījums nav pieejams - 2005 |