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 34.
... phases of development . Review Everything , Test Everything Reviews get a bad rap . Many people see them as frivolous . “ In a perfect world , " many project managers say , “ we would review all of our documents . But we live in the ...
... phase of a software project. They are designed to be implemented one at a time and in any order (with a few restrictions). This means that you have a lot of freedom to choose the approach that is best for your project. But no matter ...
... phase or area of a software project. It contains specific tools and techniques a project manager can use to help address problems, as well as information that most project managers should know about what goes on during that phase of the ...
... phases: a version of the software with some subset of the features is released first, and a newer, more complete version is released later. This section describes the plan for a phased release, if that approach is to be taken. This is ...
... phases, the fea- tures should be divided into those phases as well. • A description of the intermediate deliverable or work product that will be built. This is a list that covers (but is not limited to): software requirements ...
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 |