Scope Definition
Scope & SOW
Scope in Agile World
Controlling Project Scope
Potpourri/Misc
100

Scope is the summation of all deliverables required as part of the project. It includes 

A. Products

B. Services

C. Results

D. Product  & Services 

E. Product , Services & Results

E. Product, services & results

100

Identify the main components of the scope statement in SOW

A. Clearly define what the project will do

B. Clearly define what the project won't do

C. Both A & B

C. Both A & B

100

How is scope finalized in agile cycles ?

A. Prioritization of backlog.
B. Formal SOW process

A. Prioritization of backlog.

100

According to Bernie Roseke, one of the biggest sources of project distress is _____.

Ineffective project control

100

Define scope creep?

Scope creep refers to a scenario whereby changes occur after the project has been started and the changes are not defined or anticipated within the scope statement. When scope creep occurs, it can negatively impact the project timeline, deliverable quality, resources, budget, and other aspects. Managing the scope of your project can help avoid unwelcome surprises

200

Project scope changes can
impact _______ and _________.

Schedule and cost

200

SOW should include the success criteria for the project. What are the main components of the success criteria?

- Timeliness and schedule expectations
- Budget expectations
- Other goals for project, including customer’s expectations.

200

Product scope is more relevant to the agile development cycles. How is expected results ensured for each feature?

Acceptance criteria

200

Scope control can only be as good as _______. This will avoid scope creep.

Scope statement

200

True or false. Acceptance criteria can be loosely defined.

Acceptance criteria that spell out exactly how success will be measured

300

Discuss the impact of the project scope changes
in the different project stages - Project initiation , Project planning and Project execution ?

1. During project initiation, when the scope is being developed, any additions to the project scope will have the least impact on the project schedule or cost, because the schedule and cost estimating have not been finalized and no work will need to be discarded.
2. Scope changes implemented once work has begun will have a greater effect on the project schedule and cost than changes implemented during the project initiation or planning phase; therefore, it is imperative that the project scope be well defined before the project work begins.
3. During the planning phase, changes to the scope will have an impact on the schedule and cost because they will probably require added planning. This additional planning will require people resources and extra time to make adjustments to the plan.
4.Once the project work has begun, and later in the project’s life cycle, scope changes will dramatically increase the cost and delay the schedule of a project. Another negative impact of scope changes is the impact on team morale ;detrimental effect on team dynamics

300

What’s the difference between the statement of work and the scope of work?

The scope of work is just one section of the statement of work. While the SOW is a comprehensive document that details the project’s goals, guidelines, deliverables, schedule, costs and more, the scope section focuses on how those goals will be met.
SOW components:
Scope of work
Project objectives
Schedule
Tasks
Deliverables
Payment of the project
Expected outcomes
Certain terms, conditions and requirements

300

Compare the scope management process within
predictive / waterfall project and adaptive / agile projects.

1. Predictive project , scope is defined through scope statement in SOW.Baseline can only be changed though formal change control process.
2. In adaptive or agile lifecycle SOW will have high level of chanage in scope statement. there will be ongoing stakeholder engagement to prirotize the backlog.Vlaidate and control scope is iteraed in every cycle

300

Why should assumptions be considered when building the project scope?

Identify, document, and communicate assumptions. Assumptions are those elements that relate to the project that are assumed to be true for the duration of the project. Assumptions are necessary to provide an estimate of the cost and schedule to deliver the project’s scope during the planning phase of a project

300

Earned Value Method is employed to allow the project manager calculate ______ and ______.

Schedule variance and cost variance

400

What are some effective ways to avoid scope changes ?

1. Make sure that all stakeholders are included in the development of the project charter and development of the preliminary scope
2. Make sure that project requirements are understood as best as possible. The project requirements will evolve during project planning, but a better understanding during the initiation phase will ease the scope definition during the planning phase.
3. Make sure that project requirements are understood as best as possible. The project requirements will evolve during project planning, but a better understanding during the initiation phase will ease the scope definition during the planning phase.
4. Make sure that all deliverables are agreed on by the project team, project sponsor, and customer.
5. Make sure that no work outside the project scope is done.Make sure that all project scope change requests are effectively communicated to and understood by the customer.If a team member, senior manager, or the customer request changes, make sure the change(s) requested are fully analyzed and all impacts to the project are fully explained

400

You are currently working on the SOW for your Practicum project. Explain the process you are following. What are the challenges you are facing ? How do you plan to mitigate them?

Professor Gladys will decide the score!

400

Use examples from your professional experience, explain how you use artifacts such as Epics, stories etc to manage scope .

Unlike the wide and deep requirements of the traditional approach, I characterise Agile requirements as high level and focussed. The scope of an Agile project is defined by high level requirements, in the form of User Stories, scheduled in the Release Plan. Detailed (or deep) requirements are still necessary but they are only created when they are needed – this is the focussed bit.
This means that if/when the scope changes we have invested a minimal amount of energy in specifying out the bit that is no longer needed.

400

Name and briefly explain 2 of the main factors that result in scope creep.

1. Poorly documented scope
2. Poor requirements definition
3. Poor communication between stakeholders
4. Underestimating project work
5. External factors

400

Why is stakeholder buy-in important and what are some buy-in tactics that you've encountered in the past?

Professor Gladys will score!

500

You are project / product / program manager, and you receive a request for scope change .
What are the factors you would consider to evaluate whether a scope change is necessary? Elaborate briefly

1. Added value. The scope change produces added value that wasn’t there before. Even better, the proportional value relative to the expenditure is greater than the original project.
2. Market needs. The market was not adequately defined or market needs have changed, and the additional expenditure will be necessary to remain competitive.
3. Return on Investment. The project has identified a potential opportunity which will result in a return on investment that wasn’t anticipated before.
4. Impact on Schedule/Cost. The project has identified potential cost and/or schedule savings within other areas of the organization or future projects.
5. Product Liability or Risks. Additional risks and/or product liability have appeared, requiring more in-depth analysis and/or mitigation to save the organization money down the road.

500

Use the practicum project or internship as an example. Briefly describe how you interacted with different stakeholders to finalize the scope of the feature / project you are working on.

Professor Gladys will decide the score!

500

Can you think of an instance where you encountered scope creep in agile world? How did you handle it ?

Professor Gladys will score!

500

Name and briefly describe 3 of the 5 checklist items that can be used to develop a business case for scope change

1. Added value
2. Market needs
3. Return on Investment
4. Impact on Schedule/Cost
5. Product Liability or Risks

500

What type of project requires most flexibility when it comes to scope changes? Why?

The exception to this might be with an agile project, a technique which is used primarily in software development where pieces of software are developed, tested, and released in parts.