PMP - Introduction Flashcards

1
Q

What are the 3 styles of PMOs

A

Supportive, Controlling, Directive

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

Describe predictive project management environment?

A

plan based approach. activities done in a specific order or in a linear fashion. Phases can be sequential or overlapping. Key roles: project manager and team. Deliverables transition to customer at completion.

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

OPM

A

organization project management - strategy execution framework that coordinate projects, programs, portfolios and operations management, and which enables organizations to deliver on strategy

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

Name 3 types of authority in organizational structures

A

Functional, matrix, project oriented

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

Define Functional relative authority

A

team member is part time on project and reports to a functional manager.

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

define matrix relative authority

A

team member is part time on a project and reports to both a functional manager and a project manger. Conflicted loyalty. PMP has medium control of the project and authority is shared with functional manager/sponsor

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

define project oriented relative authority

A

team member is full time on a project and reports to a project manager. PM high control over team members. Loyalty to Project

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

8 project performance domains

A

team, stakeholder, development approach and life cycle, planning, project work, delivery, measurement, uncertainty

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

Agile Manifesto 4 values

A

individuals and interactions > process and tools
working software > comprehensive documentation
customer collaboration > contract negotiation
responding to change > following a plan

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

Describe a Agile/SCRUM project management environment

A

Change based approach with incremental or iterative development. work is timeboxed in iterations/sprints or continuous flow. Key roles: product owners, project team, team lead/scrum master, agile. Value: iterative/incremental delivery to the customer, regular customer feedback cycles that enable continuous development

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

PESTLE

A

political, economic, social, technical, legal, environmental. typically used for a profit company to see if they have market space in a new place.

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

TECOP

A

technical, environmental, commercial, operational, political. Can we do business in this place (e.g. can we sell this across state lines). practical/technical

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

VUCA

A

Volatility, uncertainty, complexity, ambiguity. typically used for political spaces.

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

EEFs

A

Enterprise Environmental Factors. Culture. How people act. Conditions outside the control of the team and can influence, constraints or direct the project, program or portfolio. internal and external to the org. (e.g. resource capabilities, organizational culture, IT software, distribution of facilities)

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

OPAs

A

Organizational Process Assets. Project policies, procedures, and templates. Historical project info. All the input or assets on process used by an org in operating its business (e.g. org charts, onboarding procedures, business plans, processes, policies, protocols, and knowledge, data as stored)

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

List 6 business values

A

financial gain
new customers
social benefit
first to market
improvement (tech, process, etc.)
regularization (alignment or compliance with standards and regulations)

17
Q

what is a needs assessment

A

Kick off doc done by a business analyst done before the business case that involved understanding the business goals and objectives, issues, and opportunities.

18
Q

define a business document

A

developed prior to business start (usually by business analyst)
contains info about project objectives and contribution to business goal
helps determine if a project is worth it (required time, money, resources)

19
Q

benefits management plan

A

what work/projects should we be doing? should include:
- process for creating, maximizing, and sustaining project benefits
- time frame for short and long term benefits realization
- benefits owner or accountable person
- metrics
- assumptions, constraints and risks

20
Q

business case

A

More specific doc of why to do this particular project. Validates the project’s benefits and establishes boundaries.
- cost benefits anlysis
- business need
- quality specifications
- schedule or cost constraints

21
Q

OKRs

A

Objectives and Key Results. Objectives are goals and intents. Key results are teim bound with measurable milestones

22
Q

Incremental value delivery

A

when you preview a piece of your design to check to see if the end users likes it. Enables early feedback, allowing for adjustments to the direction, priorities, and quality of the product.

23
Q

ADKAR

A

Model for creating individual change
A - awareness of the need for change
D - desire to support the change
K - knowledge of how to change
A - ability to demonstrate new skills and behavior
R - reinforcement to make the change stick

24
Q

Project Governance

A

The framework, functions, and processes that guide project management activities to create a unique product, service, or result to meet organizational, strategic, and operational goals. Establish by PMO and critical for managing change in scope, budget, schedule, resources, quality, etc. Too much governance or too little is an issue. Also interface with the public as the face of a project for the company.

25
Q

Stage gates

A

point at which you review a project. governance can decide to kill the project based on the data the PMP shows. aka phase gate, decision point, toll gate, etc. stop, do a retrospective and make sure we are ready to move on and have met our exit criteria.

26
Q

How long is a scrum huddle?

A

15 minutes

27
Q

thresholds or tolerance levels

A

PMP have a specific zone of authority based on the company’s tolerance of risk. if outside the risk tolerance then escalate to to governance.

28
Q

Compliance

A

internal and external standards including government regulations, corporate policies, product and project quality, project risk. PMO monitors compliance at the organizational level. Project team also needs to follow project activity related compliance including quality or process, procurement of vendors,

29
Q

Compliance 5 best practices

A
  1. documentation
  2. risk planning
  3. compliance council – quality/audit specialists and legal/technical specialists
  4. compliance audit
  5. compliance stewardship