RM midterm exam

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/224

encourage image

There's no tags or description

Looks like no tags are added yet.

225 Terms

1
New cards

Scope

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

2
New cards

Deliverable

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

3
New cards

Project scope management

The processes involved in defining and controlling what is or is not included in a project, so the team and stakeholders share the same understanding of what will be produced and how.

4
New cards

Scope management processes

Planning scope management, collecting requirements, defining scope, creating the WBS, validating scope, and controlling scope.

5
New cards

Planning scope management

Determining how the project's scope and requirements will be managed. Outputs are the scope management plan and the requirements management plan.

6
New cards

Scope management plan contents

Prepare a detailed project scope statement, create a WBS, maintain and approve the WBS, obtain formal acceptance of completed deliverables, and control requests for changes to scope.

7
New cards

Requirement (PMBOK Sixth Edition)

A condition or capability that is necessary to be present in a product, service, or result to satisfy a business need.

8
New cards

Requirements management plan

Documents how requirements will be analyzed, documented, and managed: how to plan, track, and report requirements activities; do configuration management; prioritize requirements; use product metrics; and trace and capture requirement attributes.

9
New cards

Collecting requirements

Defining and documenting the features and functions of the project's products and the processes used to create them.

10
New cards

Ways to collect requirements

Interviewing stakeholders, focus groups and facilitated workshops, group creativity and decision-making techniques, questionnaires and surveys, observation studies, and benchmarking.

11
New cards

Requirements traceability matrix (RTM)

A table listing requirements, their attributes (e.g., name, category, source), and their status to ensure all requirements are addressed.

12
New cards

How Google Tests Software (best practice)

Describes how Google changed its culture so quality rests on those writing the code: don't rely on testers to ensure quality and don't believe in fads or buzzwords, including Agile.

13
New cards

Defining scope

Reviewing the project charter, requirements documents, and organizational process assets to create a scope statement.

14
New cards

Elements of a project scope statement

Product scope description, product user acceptance criteria, and detailed information on all project deliverables. Also helpful: project boundaries, constraints, assumptions, and supporting document references.

15
New cards

Scope clarity over time

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

16
New cards

Poor requirements management cost

For every dollar spent on projects and programs, 5.1 percent is wasted due to poor requirements management.

17
New cards

Work breakdown structure (WBS)

A deliverable-oriented grouping of the work involved in a project that defines its total scope. It is the foundation document for planning and managing schedules, costs, resources, and changes.

18
New cards

Decomposition

The main tool for creating a WBS: subdividing project deliverables into smaller pieces.

19
New cards

Work package

A task at the lowest level of the WBS.

20
New cards

Scope baseline

The approved project scope statement plus its associated WBS and WBS dictionary.

21
New cards

WBS development approaches

Using guidelines (e.g., U.S. DOD), the analogy approach, the top-down approach, the bottom-up approach, and mind mapping.

22
New cards

Analogy approach (WBS)

Reviewing the WBSs of similar projects and tailoring them to your project.

23
New cards

Top-down approach (WBS)

Starting with the largest items of the project and breaking them down.

24
New cards

Bottom-up approach (WBS)

Starting with the specific tasks and grouping them upward.

25
New cards

Mind mapping (WBS)

Using branches radiating out from a core idea to structure thoughts and ideas.

26
New cards

WBS dictionary

A document that describes detailed information about each WBS item, since many WBS tasks are vague. Its format can vary with project needs.

27
New cards

WBS and WBS dictionary advice

A unit of work appears in only one place; an item's content is the sum of the items below it; each item is the responsibility of one individual; team members help develop it; every item is documented in the dictionary; and the WBS stays flexible to changes.

28
New cards

Scope creep

The tendency for project scope to keep getting bigger and bigger.

29
New cards

Validating scope

Formalizing acceptance of the completed project deliverables, often through a customer inspection and then sign-off on key deliverables.

30
New cards

FoxMeyer Drug and McDonald's (scope failures)

FoxMeyer went bankrupt after scope creep and overemphasis on technology. McDonald's ended its 2001 real-time intranet project after spending $170 million on consultants and initial planning.

31
New cards

Controlling scope

Controlling changes to the project scope while keeping project goals and business strategy in mind. Goals: influence factors that cause changes, process changes by integrated change control procedures, and manage changes when they occur.

32
New cards

Variance

The difference between planned and actual performance.

33
New cards

Ways to improve user input

Insist sponsors come from the user organization, place users on the project team, hold regular meetings with defined agendas, deliver something regularly, don't over-promise, and locate users with the developers.

34
New cards

Ways to reduce incomplete and changing requirements

Follow a requirements management process, use prototyping, use case modeling, and JAD, keep requirements written and current, use a requirements database, test throughout, review changes from a systems perspective, emphasize completion dates, and allocate resources for change requests.

35
New cards

Software for scope management

Word processors for documents, spreadsheets and presentation software for charts and matrices, mind-mapping software for the WBS, communication software, project management software for the WBS and Gantt chart, and specialized software.

36
New cards

Scope in agile/adaptive environments

Stakeholders define and approve detailed scope before each iteration, producing a usable product at the end of each. Detailed scope develops over time.

37
New cards

Importance of project schedules

Delivering on time is a top challenge. Time has the least flexibility because it passes no matter what happens, and schedule issues are the main source of conflict, especially in the second half of projects.

38
New cards

Work styles and schedule conflicts

The Myers-Briggs J vs. P dimension reflects attitudes toward structure and deadlines. Cultures and countries also differ in their attitudes about schedules.

39
New cards

Project time management processes

Planning schedule management, defining activities, sequencing activities, estimating activity resources, estimating activity durations, developing the schedule, and controlling the schedule.

40
New cards

Planning schedule management

Determining the policies, procedures, and documentation for planning, executing, and controlling the project schedule.

41
New cards

Schedule management plan contents

Project schedule model development, scheduling methodology, level of accuracy and units of measure, control thresholds, rules of performance measurement, reporting formats, and process descriptions.

42
New cards

Defining activities

Identifying the specific activities team members and stakeholders must perform to produce the project deliverables.

43
New cards

Activity (task)

An element of work normally found on the WBS that has an expected duration, a cost, and resource requirements.

44
New cards

Activity list

A tabulation of activities to be included on the schedule, with each activity's name, identifier or number, and brief description.

45
New cards

Activity attributes

More information about an activity: predecessors, successors, logical relationships, leads and lags, resource requirements, constraints, imposed dates, and assumptions.

46
New cards

Milestone

A significant event that normally has no duration. It often takes several activities to complete one, and milestones help set schedule goals and monitor progress (e.g., customer sign-off).

47
New cards

FBI Trilogy project

A failed FBI system hurt by poor time management, missed milestones, and escalating costs. Sentinel replaced it in 2007 and still wasn't working well in 2014.

48
New cards

Sequencing activities

Identifying and documenting the relationships between project activities by reviewing activities and determining dependencies.

49
New cards

Dependency (relationship)

The sequencing of project activities or tasks. You must determine dependencies to use critical path analysis.

50
New cards

Mandatory dependency

Inherent in the nature of the work being performed. Sometimes called hard logic.

51
New cards

Discretionary dependency

Defined by the project team. Sometimes called soft logic, and should be used with care since it may limit later scheduling options.

52
New cards

External dependency

A relationship between project and non-project activities.

53
New cards

Network diagram

A schematic display of the logical relationships among, or sequencing of, project activities. It is the preferred technique for showing activity sequencing.

54
New cards

Arrow diagramming method (ADM)

Also called activity-on-arrow (AOA). Activities are arrows, nodes (circles) are start and end points, and it can show only finish-to-start dependencies.

55
New cards

Burst and merge (AOA diagrams)

A burst occurs when a single node is followed by two or more activities. A merge occurs when two or more nodes precede a single node.

56
New cards

AOA drawing rules of thumb

Work left to right, all arrowheads face right, and no arrows cross.

57
New cards

Precedence diagramming method (PDM)

Activities are boxes and arrows show relationships. It is more popular than ADM, is used by project management software, and is better at showing different dependency types.

58
New cards

Finish-to-start (FS)

Task B cannot start until task A finishes.

59
New cards

Start-to-start (SS)

Task B cannot start until task A starts.

60
New cards

Finish-to-finish (FF)

Task B cannot finish until task A finishes.

61
New cards

Start-to-finish (SF)

Task B cannot finish until task A starts.

62
New cards

Estimating activity resources

Estimating how many resources (people, equipment, materials) the team should use for each activity, considering difficulty, the organization's history, and resource availability.

63
New cards

Resource breakdown structure

A hierarchical structure that identifies the project's resources by category and type.

64
New cards

Duration vs. effort

Duration is the actual time worked on an activity plus elapsed time. Effort is the number of workdays or work hours required to complete a task. Effort does not normally equal duration.

65
New cards

Three-point estimate

An estimate with optimistic, most likely, and pessimistic values (e.g., 3, 4, and 5 weeks). It is needed for PERT and Monte Carlo simulations.

66
New cards

Developing the schedule

Using the other time management processes to determine project start and end dates and create a realistic schedule for monitoring progress. Tools: Gantt charts, critical path analysis, critical chain scheduling, and PERT.

67
New cards

Gantt chart

A standard format for showing project activities and their start and finish dates in a calendar format.

68
New cards

Gantt chart symbols

A black diamond is a milestone, thick black bars are summary tasks, lighter horizontal bars are task durations, and arrows are dependencies.

69
New cards

Adding milestones to Gantt charts

Enter a task with zero duration, or mark any task as a milestone, to emphasize important events or accomplishments.

70
New cards

SMART criteria (milestones)

Milestones should be Specific, Measurable, Assignable, Realistic, and Time-framed.

71
New cards

20-second rule (Shawn Anchor)

From The Happiness Advantage: people take the path of least resistance, so make distractions harder by adding time to them (e.g., keep email and websites closed while working).

72
New cards

Tracking Gantt chart

A schedule comparison chart showing planned dates against actual dates, including slipped milestones.

73
New cards

Critical path method (CPM)

A network diagramming technique used to predict total project duration.

74
New cards

Critical path

The longest path through the network diagram. It determines the earliest time the project can be completed and has the least slack or float.

75
New cards

Slack (float)

The amount of time an activity may be delayed without delaying a succeeding activity or the project finish date.

76
New cards

Calculating the critical path

Develop a good network diagram, add the durations on each path, and the longest path is critical. If a critical activity runs late, the project slips unless corrective action is taken.

77
New cards

Critical path facts

It is not the path with all the critical activities (it only accounts for time), there can be more than one if paths tie, and it can change as the project progresses.

78
New cards

Free slack (free float)

The time an activity can be delayed without delaying the early start of any immediately following activity.

79
New cards

Total slack (total float)

The time an activity can be delayed from its early start without delaying the planned project finish date.

80
New cards

Forward pass and backward pass

A forward pass through the network diagram determines early start and finish dates. A backward pass determines late start and finish dates.

81
New cards

Techniques for shortening a schedule

Shorten critical activity durations (add resources or change scope), crash, and fast track.

82
New cards

Crashing

Obtaining the greatest amount of schedule compression for the least incremental cost.

83
New cards

Fast tracking

Doing activities in parallel or overlapping them.

84
New cards

Updating critical path data

Update schedule information regularly because the critical path may change as actual dates are entered. If completion will slip, negotiate with the project sponsor.

85
New cards

Critical chain scheduling

A scheduling method that considers limited resources and uses buffers to protect the completion date.

86
New cards

Theory of Constraints (TOC)

A management philosophy developed by Eliyahu M. Goldratt and introduced in his book The Goal. It underlies critical chain scheduling.

87
New cards

Multitasking

When a resource works on more than one task at a time. Critical chain scheduling tries to minimize it.

88
New cards

Buffer

Additional time to complete a task.

89
New cards

Murphy's Law

If something can go wrong, it will.

90
New cards

Parkinson's Law

Work expands to fill the time allowed.

91
New cards

Project buffer and feeding buffers

Critical chain removes buffers from individual tasks. A project buffer is extra time added before the project's due date, and feeding buffers are extra time added before tasks on the critical path.

92
New cards

Program Evaluation and Review Technique (PERT)

A network analysis technique for estimating duration when individual activity estimates are highly uncertain. It uses probabilistic time estimates (optimistic, most likely, pessimistic).

93
New cards

PERT weighted average formula

(Optimistic time + 4 x most likely time + pessimistic time) / 6. Example: (8 + 4 x 10 + 24) / 6 = 12 days.

94
New cards

Agile and time management

Agile values customer collaboration over contract negotiation and responding to change over following a plan. The product owner defines and prioritizes work within a sprint, and not all work is defined before scheduling.

95
New cards

Schedule control suggestions

Perform reality checks, allow for contingencies, don't plan for 100% capacity all the time, and hold progress meetings with stakeholders with clear, honest communication.

96
New cards

Controlling the schedule

Knowing schedule status, influencing causes of change, determining that the schedule changed, and managing changes. Tools: progress reports, a schedule change control system, PM software (tracking Gantt), variance analysis, and earned value.

97
New cards

Reality checks on scheduling

Review the draft schedule or completion date in the charter, prepare a detailed schedule with the team, make sure it is realistic and followed, and alert top management early about problems.

98
New cards

People issues in scheduling

Strong leadership helps projects succeed more than good PERT charts. Project managers should use empowerment, incentives, discipline, and negotiation.

99
New cards

Cautions on project management software

Many people misuse it from lack of training. You must enter dependencies for dates to adjust and the critical path to be found, and enter actual schedule information to compare planned and actual progress.

100
New cards

Project cost management

The processes required to ensure the project is completed within an approved budget.