Chapter 6: Planning for Software Quality 145 idea
Chapter 6: Planning for Software Quality 145 idea that we believe changes should be discouraged in project management. Sometimes changes are absolutely necessary in order to make your stakeholders happy. The two points to consider regarding change control are Consider how changes may affect quality, and address this in your change control plan and your quality management plan. Changes are not evil beings to be avoided. They are a necessary part of any project, and your process for dealing with them should be addressed in your change control plan. What you need is integrated change control. Integrated change control is a method to examine change and its influence on the project as a whole. When changes are proposed, answer all of the following questions: What affect does this change have on the project scope? If your scope grows, then you ll need to reflect additional time and cost considerations to incorporate the change. The inverse is true as well; the customer may want to remove deliverables from the scope, but this doesn t always mean that the cost or quality baselines should be adjusted. Sometimes you ve already invested time and monies into the deliverables they now want removed from the project. What affect does this change have on cost and time? Obviously this question is considered in light of the scope growing or shrinking, but the consumption of time or funds to satisfy a change request may spread your schedule and budget too thin to maintain quality. One of the biggest mistakes software project managers make is trying to please everyone by accepting changes without reflecting time and cost changes. Then they ll overwork their project team to achieve the project objectives, and quality suffers. Don t be that kind of boss.
Note: If you are looking for reliable webhost to maintain and run your java application check Vision java hosting services