Project+ (PK0-005)

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/128

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

129 Terms

1
New cards

Processes

Activities that underlie the effective practice of project management; they include all phases of concept/discovery, initiation, planning, execution, and closing.

2
New cards

Project budget

Total financial sum available to pay for project's expenses. Includes cost estimates and additional reserves to cover issues

3
New cards

Concept or discovery phase

Occurs before project starts. Filters out unfeasible projects, saving time

4
New cards

Initiation Phase

Idea approved as project. outline project. Ensure everybody understands their role. Draft project goals and timeline

5
New cards

Planning Phase

Team will define activities they need to complete. PM will create ways to keep project on track.

6
New cards

Execution phase

Team delivers work. PM monitors progress and measures performance, find and solve problems, maintain records, create reports

7
New cards

Closing phase

Confirm project is thorough, update documentation, create accurate financial summary. Celebrate

8
New cards

Business case

A brief document that justifies the investments made for a project and describes how a particular investment is in accordance with the organization's policy.

9
New cards

Executive summary

A brief synopsis of the rest of the business case. Gives an overview of the main points in a few sentences.

10
New cards

Problem statement

Presents a more thorough analysis of the current situation and the business problem, opportunity, or unmet need. Describes something that will change due to this process

11
New cards

Problem Analysis

Provides more context about why the project should be a priority. Can include historical performance data, experimental assessment, or other evidence to support business case

12
New cards

Options

Describes several approaches to solving problems. At least three, no more than five. Compares solutions with pros and cons.

13
New cards

Project Definition

Includes additional relevant information about the proposed project: project scope, resources needed, milestones, timeline

14
New cards

Financial overview

Covers relevant economic impacts of the project. Contains cost-benefit analysis or return on investment (ROI)

15
New cards

Recommendation

Narrows down options to best solution. Justifies why this approach is best case.

16
New cards

Do nothing

Should always be included in Options to describe impact of not solving the problem

17
New cards

Benefit

Money generated or saved due to a project. Aka financial value or revenues

18
New cards

Cost

Represents money spent on the project.

19
New cards

Net profit

The difference between benefit and cost

20
New cards

Environmental factors

How the organization impacts the natural world.

21
New cards

Social factors

How the company develops relationships and treats people, including employees, people in the community, and groups impacted by the company's products and services

22
New cards

Governance factors

Describes how the company operates, including its policies, transparency, and structure.

23
New cards

Corporate identity

Includes the company's vision, mission statement, values, and brand.

24
New cards

Operational work

Routine, predictable, and repetitive

25
New cards

Project work

Type of work that accomplishes something new.

26
New cards

organizational structure

Affects the project management process and the PM role. Defines how work moves and how people form into teams in a company.

27
New cards

Functional organization

Divides organization by areas of expertise or specialization.

28
New cards

Projectized organization

Organization type that pools resources around projects. When the project ends, the team disbands and reforms around new projects.

29
New cards

Data warehouse

An extensive database used for reporting and analytics. Used to create dashboards for monitoring company performance

30
New cards

Run chart

tool for tracking results over a period of time; trends occurring in a project without using statistical analysis

31
New cards

Matrix Organization

Any organizational structure in which the project manager shares responsibility with the functional managers for assigning priorities and for directing the work of persons assigned to the project.

32
New cards

Weak Matrix Organization

Functional manager retains all budget and staff management responsibilities. PM has less control over project.

33
New cards

Strong Matrix Organization

PM has substantial control over project. May have management responsibilities for budget and staff.

34
New cards

Program

A group of related projects that have a common objective

35
New cards

Project manager

Plan, organize, and keep teams on track throughout project life cycle

36
New cards

Program manager

Coordinates with project managers, oversees related projects in a program to obtain maximum benefits, provides guidance and support to every individual project

37
New cards

Project management office

A centralized, ongoing administrative unit or department that serves to improve project management performance within an organization by providing oversight, support, tools, and helpful methodologies

38
New cards

Supportive PMO

PMO type, provides support when requested. Doesn't force adherence to standards, may not assign or evaluate projects.

39
New cards

Controlling PMO

PMO type, Actively monitors project performance. Coordinates resource selection, and allocate PMs to projects. Does not have full authority, influence is limited.

40
New cards

Directive PMO

Most controlling type of PMO. Sets rules for everybody and company. Prioritizes projects, and allocate PMs for all projects in company.

41
New cards

Stakeholder

Anybody with a vested interest in a project

42
New cards

Senior management

Refers to highest level of leader ship in an organization

43
New cards

Sponsor

Person accountable for a project. Often a senior management member. Secure funding and remove resource related barriers.

44
New cards

Customer

In project management, the party to receive the benefit from the projects

45
New cards

Internal customers

People who work inside the project organization. They do not purchase the projects outcome.

46
New cards

External customers

Includes everyone outside the organization

47
New cards

End user

The person who interacts with a Projects final output

48
New cards

Portfolio

A group of all projects and programs, they do not need to be related

49
New cards

DevOps

Not a project mgmt methodology. Controls software engineering process and offers op support, reducing friction and improving cross-functional collaboration.

50
New cards

SDLC

A software development framework that improves process through continual improvement. Users incorporate best practices and lessons learned into framework to be more efficient every subsequent cycle

51
New cards

Scaled Agile Framework (SAFe)

Popular agile-at-scale framework that incorporates multiple agile practices and frameworks. Visualizes prominent roles, practices, events, and artifacts on interactive Big Picture

52
New cards

Extreme Programming (XP)

An agile software development framework that emphasizes software engineering practices and design to create higher quality of life for developers

53
New cards

PRojects IN Controlled Environments (PRINCE2)

Aims to control project management processes by creating clear project phases, clearly defining roles and responsibilities, predefining tasks to manage the project life cycle, and is the project management standard for the UK

54
New cards

Scrum

Lightweight, customer centric framework and is arguably the most common agile framework as it delivers iterative an adaptive value while intentionally covering only the barest requirements

55
New cards

Kanban

An agile development methodology, is relatively new and is used to control work in progress (WIP) levels and manage workflows in software and other business processes

56
New cards

Planned Value (PV)

What you should have spent at this point in the schedule

57
New cards

Budget at Completion (BAC)

How much the project should cost

58
New cards

Earned Value (EV)

How much of the project schedule is actually completed

59
New cards

Actual Cost (AC)

How much the project has cost so far

60
New cards

Cost Variance (CV)

How above or below budget the project is

61
New cards

Cost Performance Index (CPI)

Whether the project is within budget

62
New cards

Schedule Variance (SV)

How far behind schedule the project is

63
New cards

Schedule Performance Index (SPI)

Whether the project is ahead of or behind schedule

64
New cards

Estimate to Complete (ETC)

The cost needed to finish the remaining work

65
New cards

Estimate at Completion (EAC)

What the total project will probably cost

66
New cards

Variance at Completion (VAC)

How much the total project will be above or below budget

67
New cards

CV = EV - AC

cost variance formula

68
New cards

CPI = EV / AC

cost performance index formula.

69
New cards

SV = EV - PV

schedule variance formula.

70
New cards

SPI = EV / PV

schedule performance index formula.

71
New cards

EAC = AC + ETC or BAC/CPI

estimate at completion formula.

72
New cards

VAC = BAC - EAC

variance at completion formula

73
New cards

Project Scope Statement

Expands on the scope provided in project charter. Includes detailed descriptions of multiple elements

74
New cards

Project Charter

A brief, formal document, created in project initiation phase; outlines project parameters. Helps team, stakeholders, sponsor, and PM agree on why project matters and what needs to happen

75
New cards

solution design

Characterizes a conceptual plan representing how something must work and integrate. Aims to optimize product in given environment. Captures architecture and design requirements, including testing requirements, technical risks, and analysis of tradeoffs

76
New cards

Product Owner

Works with agile team. Identifies how to improve product and is accountable for creating most valuable product possible

77
New cards

Automated Testing

More expedient than other testing models, allows developer to run more tests frequently. Enables practices like continuous integration. Increases user's confidence in software's quality

78
New cards

Manual Testing

Creates severe capacity limit on software development. Adaptable because people can detect slight changes in software's appearance and work around it.

79
New cards

Slide Deck

Often serve as a backdrop to a conversation or presentation. Created by presentation software.

80
New cards

OCM plan

A strategy to support users in adapting to change. PM regularly updates it to assist team in creating plan for simplifying change and reducing resistance

81
New cards

Smoke test

Ensures that core functions work. Runs after engineer compiles code into build before deploying and releasing it.

82
New cards

Operational training

Education developers provide to entities and users to prepare them for working, maintaining, and improving a product on a long-term basis

83
New cards

Statement of Work (SOW)

Involves working together. Focuses on deliverables

84
New cards

terms of reference (TOR)

Consists of work to be delivered. Focuses on relationships

85
New cards

Diagramming tools

Allows users to create visual representations of processes, systems, objects, structures, ideas, and information. Outputs are diagrams, charts, and graphs.

86
New cards

Operational Expense

Regular expenses such as salaries, taxes, and recurring costs like subscriptions, rentals, and utilities.

87
New cards

Capital Expenses

Permanent assets such as data centers, vehicles, and equipment.

88
New cards

Project Sign-Off

Documented communication from project stakeholders that they agree to close the project. stakeholder indicates they agree that completed work meets agreed-upon requirements.

89
New cards

Project closure meeting

Final send-off of project and last working meeting. Team gathers one last time to discuss project and reflect on accomplishments and failures.

90
New cards

Project closure report

Final project summary and official project sign-off request

91
New cards

Success criteria

The measurable targets a project must meet before it can be considered successful.

92
New cards

Key performance indicators (KPIs)

Measures the most crucial indicators regularly to estimate a system's overall health. Should measure both leading and lagging indicators

93
New cards

market research

A vendor analysis process in which the organization researches a product or service and the vendors that deliver it

94
New cards

Quality Assurance

Includes all processes and procedures, aims to prevent quality issues. Encompasses quality control

95
New cards

Quality control

Part of quality assurance that involves inspecting finished work before it reaches customers

96
New cards

Quality objectives

Within a quality assurance plan by creating a list of measurable quality targets

97
New cards

Communication, simplicity, feedback, respect, and courage

Five values of extreme programming

98
New cards

lagging indicators

KPI reflective measures that describe actual success of a project or process

99
New cards

leading indicators

KPI predictive measures

100
New cards

Level

WBS layer where an element resides