project mgmt ch 5

____ refers ti all the work involved n creating the products of the project and the processes used to create them.

scope

which tool or technique for collecting requirements is often the most expensive and time consuming?

interviews

a ____ is a deliverable oriented grouping of the work involved in a project that defines its total scope

WBS

what approach to developing a WBS involved writing down or drawing ideas in a nonlinear format?

mind mapping

assume that you have a project with major categories called planning, analysis, design and testing. what level of the WBS would these items fall under?

Level 2

what are best practices that can help in avoiding scope problems on IT projeccts?

keeping scope realistic, use off the shelf hardware and software whenever possible, follow good project mgmt processes

scope ____ is often achieved by a customer inspection and then sign off on key deliverables

validation

what are some suggestions for improving user input?

develop a good project selection process for IT projects, have users on the project team co locate users with developers

project management software helps you develop a ____, which services as a basis for creating Gantt charts, assigning resources, and allocating costs

WBS

analogy approach

creating a WBS by using a similar project's WBS as a starting point

benchmarking

generating ideas by comparing specific project practices or product characteristics to those of other projects or products inside or outside the performing organization

bottom up approach

creating a WBS by having team members identify as many specific tasks related to the projet as possible and then grouping them into higher level categories

decomposition

subdividing project deliverables into smaller pieces

deliverable

a product, such as a report or segment of software code, produced as part of a project

Joint Application design (JAD)

using highly organized and intensive workshops to bring together project stakeholders -- the sponsor, user, business analysts, programmers and so on -- to jointly define and design information systems

project scope management

the processes involved in defining and controlling what work is or is not included in a project

project scope statement

a document that includes at least a description of the project, including its overall objectives and ujstification, detailed descriptions of all project deliverables, and the characteristics and requirements of products and services produced as part of th

prototyping

developing a working replica of the system or some aspect of it to help define user requirements

requirement

a condition or capability that must be met by the project or that must be present in the product, service or result to satisfy an agreement or other formally imposed specification

requirements mgmt plan

a plan that describes how project requirements will be analyzed, documented and managed

requirements traceability matrix (RTM)

a table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed

scope

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

scope baseline

the approved project scope statement and its associated WBS and WBS dictionary

scope creep

the tendency for project scope to keep getting bigger

scope validation

formal acceptance of project deliverables

top down approach

creating a WBS by starting with the largest items of the project and breaing them into subordinate items

use case modeling

process for identifying and modeling business events, who initiated them and how the system should respond to them

variance

the difference between planned and actual performance

WBS dictionary

a document that includes detailed information about each WBS item

work breakdown structure (WBS)

a deliverable oriented grouping of the owrk involved in a project that defines its total scope

work package

a task at the lowest level of WBS