Toolkit 4 Project Management

Front 1

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, waiting for the delivery of equipment, and training users.

Back 1

activity/task

Front 2

The most optimistic outcome is called the best-case estimate.

Back 2

best-case estimate

Front 3

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 analysts, and programmers review the work of other programmers, as a form of peer review.

Back 3

structured walkthrough: code review, design review, requirements review, testing review

Front 4

If tasks can be completed at the same time

Back 4

concurrent task

Front 5

a series of events and activities with no slack time

Back 5

critical path

Front 6

activities are shown as vectors, and the events are displayed graphically as nodes.

Back 6

critical path method (CPM), Program Evaulation Review Technique (PERT), network diagram

Front 7

A task that has to be completed in a serial sequence.

Back 7

dependent task

Front 8

represent the amount of work that one person can complete in one day

Back 8

person-days

Front 9

two or more concurrent tasks depend on a single prior task

Back 9

predecesor task

Front 10

reference point that marks a major occurrence

Back 10

milestone/event

Front 11

After ECTs have been determined for all the nodes in a PERT/CPM network, the ECT of the last node:

Back 11

expected project duration

Front 12

horizontal bar chart that illustrates a schedule.

Back 12

Gantt chart

Front 13

most likely outcome

Back 13

probable case estimate

Front 14

person who 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

Back 14

project coordinator

Front 15

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

Back 15

project management

Front 16

can aid analysts in project planning, estimating, scheduling, monitoring, and reporting

Back 16

project management software

Front 17

guiding, supervising, and coordinating the project team's workload.

Back 17

project monitoring and controlling

Front 18

identifying project tasks and estimating completion time and costs

Back 18

project planning

Front 19

regular progress reports to management, users, and the project team itself.

Back 19

project reporting

Front 20

of a specific timetable to facilitate completion of a project

Back 20

project scheduling

Front 21

When tasks must be completed one after another,

Back 21

sequential task

Front 22

process of managing and controlling changes requested after the system requirements document has been submitted and accepted.

Back 22

software change control

Front 23

Each of the concurrent tasks of a predecessor task

Back 23

successor task

Front 24

each task represents several activities

Back 24

task groups

Front 25

can involve sequential tasks, multiple successor tasks, and multiple predecessor tasks.

Back 25

task patterns

Front 26

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

Back 26

weight

Front 27

The most pessimistic outcome

Back 27

worst case estimate