Chapter 5 study guide answers
1. Why is project scope management so challenging in IT projects?
Answer: It is challenging because of the new requirements a client might have because the technology available is changing so fast. The requirements that were set up at the beginning change more often, that is why it is important to have a well defined project scope document this will help in unexpected delays, and more work.
2. What about your project would be challenging to manage the scope? Be very specific.
Answer: The biggest challenge I see is not letting the project grow in size. It is very easy once the work starts, and wood gets cut to start adding little pieces to the project; added railing, more stairs, building an awning. Adding one or two little add-ons might not have a large effect on the scope, but trying to tackle them all would throw off everything. I have to make sure that we stick to the project guidelines.
3. What general suggestions do you have for preventing scope creep in various types of projects?
Answer: 1) Be sure to thoroughly understand the project vision. 2) Understand your priorities and the priorities of the stakeholders. 3) Define your deliverables and have them approved by the stakeholders. 4) Break the approved deliverables into actual work requirements.
5) Break the project down into major and minor milestones, and have your schedule approved by the stakeholders.
6) Assign resources and determine your critical path.
7) Expect some project creep.
4. In the section labeled Suggestions for Improving User Input, there are five bulleted items. Each are written from the IT perspective. Rewrite each in one or two sentences at most with a direct application to your own project. Be very specific; for example, the second bullet is "have users on the project team." In IT projects, they are talking about users of the IT application. Who would those people be in your project? People who might use your deck? People who might use your bathroom regularly?
Answer: It is challenging because of the new requirements a client might have because the technology available is changing so fast. The requirements that were set up at the beginning change more often, that is why it is important to have a well defined project scope document this will help in unexpected delays, and more work.
2. What about your project would be challenging to manage the scope? Be very specific.
Answer: The biggest challenge I see is not letting the project grow in size. It is very easy once the work starts, and wood gets cut to start adding little pieces to the project; added railing, more stairs, building an awning. Adding one or two little add-ons might not have a large effect on the scope, but trying to tackle them all would throw off everything. I have to make sure that we stick to the project guidelines.
3. What general suggestions do you have for preventing scope creep in various types of projects?
Answer: 1) Be sure to thoroughly understand the project vision. 2) Understand your priorities and the priorities of the stakeholders. 3) Define your deliverables and have them approved by the stakeholders. 4) Break the approved deliverables into actual work requirements.
5) Break the project down into major and minor milestones, and have your schedule approved by the stakeholders.
6) Assign resources and determine your critical path.
7) Expect some project creep.
4. In the section labeled Suggestions for Improving User Input, there are five bulleted items. Each are written from the IT perspective. Rewrite each in one or two sentences at most with a direct application to your own project. Be very specific; for example, the second bullet is "have users on the project team." In IT projects, they are talking about users of the IT application. Who would those people be in your project? People who might use your deck? People who might use your bathroom regularly?