Applied Software Project Management Book Review
It often comes with a software project management book that is practical
, easy to use scripts to read and the entire process are finished. Andrew Stallman and Jennifer Greene recent book Applied Software Project Management has done just that.
For software project management or software engineering that dry, boring and overly complicated, too many books, but this book is not one of them. To read it because your writing style is clear, without simplistic and the authors describe things in the right level of detail was happy. It seems they understand their audience and went on a very useful and practical way to write. They have certainly achieved this.
Book is one of the tools and techniques that can be applied to projects are included. Project planning, estimating, scheduling, reviews, requirements, design and programming and testing have their own chapter. Part two on project management to effectively use and understand in the chapter on change management and leadership, managing an outsourcing project and process improvement.
A clear theme in the book of software project teams face a description of the specific problems - the change, a project, endless testing and bug cycle between software engineers, tension and misunderstanding in determining the lack of quality assurance at every level of inadequate management and business users. None of these problems are technical, but the organization and management. Stellman and Greene to provide practical advice based on their experience in similar projects to solve problems.
Stellman and Greene have certain problems much about that software teams face seem to know. Once they begin to need to describe old problems and this theme is continued throughout the book. For every problem there is always at least one proposed solution. For example, they estimate a common scenario that senior managers do not rely on the technical team, somehow believing that the technical team are able to assess more consciously described yourself some slack. Your proposed solution for the assessment of these managers are involved in the process so they can see estimates made transparent and orderly manner. They then go on to describe in detail a Wideband Delphi estimation session and run in templates and documents that can be used during these sessions provide examples of how. He is also a valuable procedure for teams to offer the script to follow.
Plans to later chapters, in which planning, reviews, requirements, design and testing. Although these chapters cover each topic in the appropriate detail design, the area lacks in detail and what kind of design deliverables can be produced, nor has any information about what these design deliverables can be one of the details. This chapter must meet the requirements and analysis, and use cases and software requirements specification documents removed for a detailed description of the scripts for the process stands in stark contrast.
Another good aspect of the book of checklists that a large project management or software engineering topics dealing with the post appears. Important quality assurance techniques to verify the authors show the other side of software projects as a way of early errors are supposed to use capture. For example, if a software requirements specification checklist is that a key requirement is missing or unclear catch the error can be corrected during the analysis phase. Authors explain that mistakes of the capture and refurbishing, with the cost of fixing errors later found in a project cost is small compared to. His emphasis on quality management techniques throughout the project with examples of checklists to be applied is very practical and useful.
The authors use some of the examples that they would reconsider. They describe the process of refactoring to make code more manageable and an example of some Java code to use multiple iterations to which they gradually refactor. In the process, why they are used in situations where code refactoring is like spaghetti at the end. That's right, except that they like spaghetti very un refactor Java code to use an example. And I think they fall into a common programmer program code beautification web where programmers iterative code that works fine for the "right" code class to spend time to improve or object. I've seen in the project where the bus schedules do not allow it on time, and certainly no extra benefit not join the industry stakeholders. Although a small complaint.
I have more pages dedicated to risk management would have liked. Time after time, managing risk is one reason that projects fail is quoted as saying. Authors in a volatile way of risk management, risk management project just how and why the book should not be around in the early stages of project planning, simply take advantage of a better description to describe.
One thing that I thought the book was a detailed look at ways of walking lacking. Underlying assumption is that the software project in the spring to follow the law. I would disagree. There is the waterfall method has been developed over the past 20 years based on the iterative approach, especially for those are some important options. Waterfall approach is the main drawback is the belief that all requirements are known at the beginning of a project.
Walking on the other hand the view that the requirements change during the project because the users what they, or due to changes in business environment, a better understanding of the needs to get. This assumption is based on a better way of running this changing environment are designed. Waterfall approach, with changes in requirements often require a corresponding increase in the effort to come back with the first phase project. Author difficult to Rational (RUP) and integration of the authors spend more on a page should seriously consider how to address their practical advice and cascade processes run on alternative methods may be used.
Finally, I think people for the book to three different occupational groups by trying too broad. The first part consists of a software team (project managers, analysts, programmers and testers) is aimed at them. Part two of the project to improve the management practices of hired consultants and project managers who need to manage software outsourcing projects is addressed. Book has had better join the software team will focus entirely on the people.
Before the end of the chapter dealing with an outsourcing project
Management Books have been treated with a superficial way, almost as if the writers felt they mention outsourcing business priority these days is such a need. The last chapter dealing with process is such a big deal effectively with the subject is less. Separate consideration of these issues and books would have been better.
Not afford these things, the book people involved in software projects, both project managers and technical team members alike, is an excellent guide. They can direct their own projects.
I have someone who works as a software development team very practical book to help people improve their ability to create high quality software advice would recommend the book to be delivered. Come to think of it, I also own the companies that a negative image of the software development team would recommend to senior managers. Perhaps the senior managers to understand why process improvement resources to the best investment they can out of it.
by: articleno2
Au_.Exe Error - Fix these Problems Here ! Errors Fix Install Tool - Important Tip ! Free Software Ultravnc Best Article Submission Software: Critical Review 27$ Article submitter With Article Creator is a Pretty simple software to use How to Choose the Right Payroll Tax Software? Project Management Software - Necessary Features Project Collaboration Software - Why Use Project Collaboration Software Error Smart Review Tidysongs Review Cnet-a Good Software To Manage Your Favoriate Songs 2010 Deep Research Report On China Eda Software Industry Project Management Software - What To Look For Project Collaboration Software - Best Project Collaboration Software