Chapter 3 Flashcards

1
Q

finish day/date

A

The time that task is scheduled to be

finished.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

concurrent task

A

If tasks can be completed at the same
time they are said to be concurrent, or
parallel.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

critical path

A
A series of events and activities with no
slack time. If any activity along the
critical path falls behind schedule, the
entire project schedule is similarly
delayed.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Project planning

A

Project planning includes identifying
project tasks and estimating completion
time and costs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Qualitative risk analysis

A

Evaluating risk by estimating the
probability that it will occur and the
degree of impact.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Microsoft Project

A

A powerful, full-featured program that
holds the dominant share of the project
management software market.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Brooks’ Law

A
This interesting concept was stated by
Frederick Brooks, Jr. an IBM engineer,
who observed that adding manpower to
a late software project only makes it
later
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

event

A

An event, or milestone, is a reference
point that marks a major occurrence.
Events are used to monitor progress
and manage a project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

worst-case estimate

A

The most pessimistic outcome is called

the worst-case estimate.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

task

A

A task, or activity, is any work that has a
beginning and an end, and requires the
use of company resources including
people, time, and/or money. Examples
include conducting a series of
interviews, designing a report, selecting
software

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Critical Path Method (CPM)

A
The Critical Path Method (CPM) was
developed by private industry, and
shows a project as a network diagram.
The activities are shown as vectors, and
the events are displayed graphically as
nodes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

activity

A

An activity, or task, is any work that has
a beginning and an end, and requires
the use of company resources including
people, time, and/or money.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

task name

A

A brief descriptive name for a task,
which does not have to be unique in the
project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

structured walk-through

A
A review of a project team member’s
work by other members of the team.
Generally, systems analysts review the
work of other systems analysts, and
programmers review the work of other
programmers, as a form of peer rev
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

duration

A

The amount of time it will take to

complete a task.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Project scheduling

A
Project scheduling involves the creation
of a specific timetable to facilitate
completion of a project. Scheduling also
involves selecting and staffing the
project team and assigning specific
tasks to team members.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

network diagram

A

A PERT chart also is referred to as a

network diagram.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

weight

A

Weight is an important value that
managers add to estimates so they can
be analyzed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

dependent tasks

A

A task is said to be dependent when it
has to be completed in a serial
sequence

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Program Evaluation Review Technique

PERT

A
The Program Evaluation Review
Technique (PERT) was developed by the
U.S. Navy to manage very complex
projects, such as the construction of
nuclear submarines.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Project monitoring

A

Project monitoring requires guiding,
supervising, and coordinating the
project team’s workload.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Risk identification

A

Listing each risk and assessing the

likelihood that it could affect a project

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

PERT/CPM

A
The Program Evaluation Review
Technique (PERT) was developed by the
U.S. Navy to manage very complex
projects, such as the construction of
nuclear submarines. At approximately
the same time, the Critical Path Method
(CPM) was developed by private
24
Q

task pattern

A
A logical sequence of tasks in a work
breakdown structure. Task patterns can
involve sequential tasks, multiple
successor tasks, and multiple
predecessor tasks.
25
Q

task box

A
In project management, a task box is a
component of a PERT/CPM chart that
contains important scheduling and
duration information about a task. Each
task in a project is represented by its
own task box in the PERT/CPM chart.
26
Q

project triangle

A

The three major components of a
project: cost, scope, and time. A project
manager tries to find the optimal
balance among these factors.

27
Q

milestone

A

A milestone, or event, is a reference
point that marks a major occurrence.
Milestones are used to monitor progress
and manage a project.

28
Q

task group

A

In task groups, each task represents

several activities.

29
Q

Risk management

A

The process of identifying, evaluating,
tracking, and controlling risks to
minimize their impact.

30
Q

design reviews

A
A design review, or structured
walkthrough, is a review of a project
team member’s work by other members
of the team. Generally, systems analysts
review the work of other systems
analysts, and programmers review the
work of other programmers
31
Q

open source

A

Software that is supported by a large

group of users and developers

32
Q

Testing reviews

A
A testing review, or structured
walkthrough, is a review of a project
team member’s work by other members
of the team. Generally, systems analysts
review the work of other systems
analysts, and programmers review the
work of other programmers
33
Q

Project reporting

A

Project reporting tasks include regular
progress reports to management, users,
and the project team itself.

34
Q

risk response plan

A
A proactive effort to anticipate a risk
and describe an action plan to deal with
it. An effective risk response plan can
reduce the overall impact by triggering
a timely and appropriate action
35
Q

predecessor tasks

A

Often, two or more concurrent tasks
depend on a single prior task, which is
called a predecessor task.

36
Q

work breakdown structure (WBS)

A

Breaking a project down into a series of

smaller tasks.

37
Q

Gantt chart

A
A horizontal bar chart that illustrates a
schedule. Gantt charts were developed
many years ago by Henry L. Gantt as a
production control technique and still
are in common use
38
Q

project coordinator

A
The project coordinator handles
administrative responsibilities for the
development team and negotiates with
users who might have conflicting
requirements or want changes that
would require additional time or
expense.
39
Q

risk management plan

A
Includes a review of the project’s scope,
stakeholders, budget, schedule, and any
other internal or external factors that
might affect the project. The plan
should define project roles and
responsibilities, risk management
methods and procedure
40
Q

code reviews

A
A code review, or structured
walkthrough, is a review of a project
team member’s work by other members
of the team to spot logic errors.
Generally, systems analysts review the
work of other systems analyst
41
Q

best-case estimate

A

The most optimistic outcome is called

the best-case estimate.

42
Q

successor task

A

Each of the concurrent tasks of a
predecessor task is called a successor
task.

43
Q

Slack time

A
The slack time for an event is the
amount of time by which an event can
be late without delaying the project.
The slack time for an event is the
difference between its latest
completion time (LCT) and earliest
completion time (ECT).
44
Q

risk

A

An event that could affect the project

negatively

45
Q

task ID

A

A number or code that uniquely

identifies a task

46
Q

person-day

A

The amount of work that one person

can complete in one day.

47
Q

quantitative risk analysis

A

Evaluating risk in terms of the actual
impact in terms of dollars, time, project
scope, or quality.

48
Q

probable-case estimate

A

The most likely outcome is called a

probable case estimate.

49
Q

start day/date

A

The time that a task is scheduled to

begin.

50
Q

bottom-up technique

A

A bottom-up technique analyzes a large,
complex project as a series of individual
tasks, called project tasks

51
Q

dependent task

A

A task is said to be dependent when it
has to be completed in a serial
sequence

52
Q

gateway

A
(1) In business processing modeling
notation, a fork in the process, allowing
the flow to go one way or another. (2) A
router or other network device used to
connect to a larger, dissimilar type of
network, such as the Internet.
53
Q

predecessor task

A

Often, two or more concurrent tasks
depend on a single prior task, which is
called a predecessor task

54
Q

project creep

A

The process by which projects with very
general scope definitions expand
gradually, without specific
authorization.

55
Q

project management

A

The process of planning, scheduling,
monitoring, controlling, and reporting
upon the development of an
information system.