1. the need for change of scope could definitely need more time and
Download as DOCX, PDF0 likes5 views
The document discusses the need for transparency when a project's scope changes due to circumstances like weather or incompetence. It notes that stakeholders must be informed of the truth and solutions found. If incompetence caused issues, those responsible should be confronted and corrective measures taken, possibly even termination. The document also cautions that scope creep without a formal process can lead to problems, giving an example from a past software project where establishing rules helped get things under control.
1 of 1
Download to read offline
More Related Content
More from Vivan17 (20)
Ad
Recently uploaded (20)
Ad
1. the need for change of scope could definitely need more time and
- 1. 1. The need for change of scope could definitely need more time and or funding. The stakeholders must be told and told the truth. If circumstances caused it, such as weather, or even incompetence. The truth out helps find a solution. Where ever the incompetence occurred should be confronted, and measures to correct it should take place, even penalties, including termination if mandated. 2. In the normal course of a project, using the change process would change the scope of a project. However, a situation like what we saw in the Rosa County case is such a mess.Starting from scratch may be the only way to rescue victory out of the jaws of defeat. What is more likely to be the case is scope creep, expanding the deliverables without a formal process. I saw this happen with a software project I was running in the early eighties. I was the culprit. I didn't understand the problem and drove my programmers nuts with "little" fixes. We finally came to our senses and established rules for fixes and upgrades. As a result, my lead programmer canceled the contract he'd taken out on me.