Mis 448 Test 2 Ch 5

Front 1

Define Scope

Back 1

Scope refers to all the work involved in creating the products of the project and the processes used to create them.

Front 2

What is a deliverable

Back 2

A deliverable is a product produced as part of a project, such as hardware or software, planning documents, or meeting minutes.

Front 3

What does project scope management include

Back 3

Project scope management includes the processes involved in defining and controlling what is or is not included in a project.

Front 4

What are the Project Scope Management Processes (5 of them)

Back 4

Scope planning: Deciding how the scope will be defined, verified, and controlled.
Scope definition: Reviewing the project charter and preliminary scope statement and adding more information as requirements are developed and change requests are approved.
Creating the WBS: Subdividing the major project deliverables into smaller, more manageable components.
Scope verification: Formalizing acceptance of the project scope.
Scope control: Controlling changes to project scope.

Front 5

What are key inputs to a scope management plan

Back 5

Key inputs include the project charter, preliminary scope statement, and project management plan.

Front 6

As time progresses what should the scope become

Back 6

As time progresses, the scope of a project should become clearer and more specific.

Front 7

Define Work Breakdown structure or WBS

Back 7

A WBS is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project.

Front 8

What kind of document is a WBS

Back 8

A WBS is a foundation document that provides the basis for planning and managing project schedules, costs, resources, and changes.

Front 9

What is decomposition

Back 9

Decomposition is subdividing project deliverables into smaller pieces.

Front 10

Example of a WBS in tabular form.

Back 10

1.0 Concept
1.1 Evaluate current systems
1.2 Define requirements
1.2.1 Define user requirements
1.2.2 Define content requirements
1.2.3 Define system requirements
1.2.4 Define server owner requirements
1.3 Define specific functionality
1.4 Define risks and risk management approach
1.5 Develop project plan
1.6 Brief Web development team
2.0 Web Site Design
3.0 Web Site Development
4.0 Roll Out
5.0 Support

Front 11

What are the 4 approaches in creating a WBS

Back 11

Analogy approach: Review WBSs of similar projects and tailor to your project.
Top-down approach: Start with the largest items of the project and break them down.
Bottom-up approach: Start with the specific tasks and roll them up.
Mind-mapping approach: Write tasks in a non-linear, branching format and then create the WBS structure.

Front 12

What is a WBS dictionary

Back 12

A WBS dictionary is a document that describes detailed information about each WBS item.

Front 13

What are 4 pieces of good advice with creating a WBS

Back 13

A unit of work should appear in only one place in the WBS.

The work content of a WBS item is the sum of the WBS items below it.

A WBS item is the responsibility of only one individual, even though many people may be working on it.

The WBS must be consistent with the way in which work is actually going to be performed; it should serve the project team first, and other purposes only if practical.

Front 14

What are 2 more pieces of good advice when creating a WBS?

Back 14

Project team members should be involved in developing the WBS to ensure consistency and buy-in.

The WBS must be a flexible tool to accommodate inevitable changes while properly maintaining control of the work content in the project according to the scope statement.

Front 15

What is 1 piece of good advice when creating a WBS dictionary

Back 15

Each WBS item must be documented in a WBS dictionary to ensure accurate understanding of the scope of work that is included and not included in that item.

Front 16

Define scope verification

Back 16

Scope verification: Formalizing acceptance of the project scope.

Front 17

What are 2 good things to remember about scope verification

Back 17

It is very difficult to create a good scope statement and WBS for a project.
It is even more difficult to verify project scope and minimize scope changes.

Front 18

What is scope control

Back 18

Scope control involves controlling changes to the project scope.

Front 19

What are the Goals of scope control

Back 19

Influence the factors that cause scope changes.
Ensure changes are processed according to procedures developed as part of integrated change control.
Manage changes when they occur.

Front 20

What is variance

Back 20

Variance is the difference between planned and actual performance

Front 21

What is scope creep

Back 21

scope creep is the uncontrolled changes in a project's scope.

Front 22

What are 6 things to remember about changing requirements (this is also good for scope creep)

Back 22

Put requirements in writing and keep them current.
Create a requirements management database for documenting and controlling requirements.
Conduct adequate testing throughout the project life cycle.
Review changes from a systems perspective.
Emphasize completion dates to help focus on what’s most important.
Allocate resources specifically for handling change requests and enhancements (as NWA did with ResNet).

Front 23

What is one good thing to remember about scope creep

Back 23

Once you decide on the scope, be careful on defining your scope