Project+ 1st set redone

A comprehensive set of 300 vocabulary flashcards covering basic project management characteristics, methodologies, change control, risk, issues, scheduling, quality, communication, meetings, resource management, and procurement.

Start and finish

A basic characteristic of a project indicating defined temporal boundaries.

Unique

A characteristic of a project indicating it is a specific, non-routine endeavor.

Reason/purpose

The core driver or objective behind the initiation of a project.

Project as part of a program

A characteristic where a project is situated within a group of related projects managed in a coordinated way.

Project as part of a portfolio

A characteristic where a project is part of a collection of projects, programs, and operations managed as a group to achieve strategic objectives.

DevSecOps

An IT project methodology and framework that integrates security into the DevOps process.

DevOps

A methodology and framework used in IT projects focusing on communication, collaboration, and integration between software developers and IT operations.

Kanban

A visual framework and methodology used in IT projects to manage work by prioritizing tasks on a board.

PRojects IN Controlled Environments (PRINCE2)

A structured project management methodology and practitioner certification program.

Software Development Life Cycle (SDLC)

A framework defining tasks performed at each step in the software development process.

Scrum

An Agile framework for managing knowledge work, with an emphasis on software development.

Scaled Agile Framework (SAFe)

A set of organization and workflow patterns intended to guide enterprises in scaling lean and agile practices.

Extreme programming (XP)

An agile software development framework that aims to improve software quality and responsiveness to changing customer requirements.

Waterfall

A linear and sequential project management approach where each phase must be completed before the next begins.

Tolerance for change/flexibility

A criterion for selecting a project method based on how well the project can handle modifications.

Requirements (Selection Criterion)

The specific needs or conditions that must be met, used as a factor in choosing a project methodology.

Budget (Selection Criterion)

Financial constraints or considerations used to determine the appropriate project management method.

Schedule (Selection Criterion)

Time-related constraints and deadlines used as a factor for methodology selection.

Environmental factors

External or internal conditions that influence the selection of a project management method.

Cultural factors

The shared values and behaviors of an organization that affect project method selection.

Developmental factors

Factors related to the growth and progress of the project team or product that influence method selection.

Industry standards

The established norms and requirements within a specific business sector that guide project methodology.

Team composition

The makeup of the project team, including roles and expertise.

Product ownership

The role or responsibility of being the primary stakeholder and decision-maker for the product.

Roles and responsibilities

The specific tasks and duties assigned to individual team members within a project.

Team size

A factor in team composition referring to the number of members in a project group.

Resource allocation and commitment

The process of assigning and securing the necessary personnel and tools for a project.

Differences in communication methods

A comparison point between Agile and Waterfall regarding how information is shared.

Change control process

A structured approach to managing changes to the project's scope, schedule, or budget.

Create/receive change requests

The first step in the change control process involving the initiation of a modification proposal.

Change control log

A document used to record and track all change requests throughout the project life cycle.

Preliminary review

An initial assessment of a change request to determine its validity and scope.

Impact assessments

Evaluations performed to determine how a proposed change will affect project constraints.

Document change recommendations

The step in the change control process where formal advice on whether to proceed with a change is recorded.

Determine decision makers

Identifying the specific individuals or groups authorized to approve or reject project changes.

Escalate to the change control board (CCB)

The process of moving a change request to a formal committee for final decision-making.

Communicate change deployment

The step of notifying relevant parties about the implementation of an approved change.

Document the status of approval

Recording whether a change request was approved, rejected, or deferred in the change control log.

Product change vs. project change

A distinction in change management between modifications to the end deliverable versus modifications to the project's execution plan.

Communicate the change status

Keeping stakeholders informed on the progress and outcome of change requests.

Update the project plan

Adjusting the formal project documentation to reflect approved changes.

Implement changes

The actual execution of approved modifications to the project or product.

Validate the change implementation

Confirming that an implemented change meets the intended requirements and functions correctly.

Manage scope creep/scope change

The activity of controlling unauthorized or unplanned expansions to project boundaries.

General risks

Broad categories of potential events that could negatively or positively impact a project.

Known risk

A potential event that has been identified and can be planned for in advance.

Unknown risk

A potential event that has not been identified and cannot be anticipated.

New projects

A situational risk factor arising from the initiation of unfamiliar endeavors.

New management

A situational risk factor involving changes in leadership and oversight.

Regulatory environment changes

A risk factor related to new laws or industry regulations that may affect the project.

Digital transformation

A risk factor associated with the large-scale integration of digital technology into business areas.

Infrastructure end-of-life

A risk factor where hardware or systems reach the end of their useful or supported existence.

Merger and acquisition

A situational risk factor involving the joining or purchase of companies.

Reorganization

A risk factor related to changes in the internal structure of an organization.

Major cybersecurity event

A risk factor involving significant data breaches or digital attacks.

Accept (Negative Risk)

A risk response where the project team acknowledges the risk and decides not to take any action unless it occurs.

Avoid (Negative Risk)

A risk response aimed at eliminating the threat or protecting the project from its impact.

Mitigate (Negative Risk)

A risk response intended to reduce the probability or impact of a potential threat.

Transfer (Negative Risk)

A risk response that shifts the impact and ownership of a threat to a third party.

Accept (Positive Risk)

A response to opportunity where the team takes no proactive action but is willing to take advantage of it if it happens.

Enhance (Positive Risk)

A risk response designed to increase the probability or impact of an opportunity.

Exploit (Positive Risk)

A risk response that seeks to ensure that the opportunity absolutely happens.

Share (Positive Risk)

A risk response that involves allocating ownership of an opportunity to a third party best able to capture the benefit.

Qualitative risk analysis

A risk assessment technique focusing on prioritizing risks by evaluating their probability and impact.

Quantitative risk analysis

A risk assessment technique involving numerical analysis of the effect of risks on project objectives.

Impact analysis

The process of identifying the potential consequences of a risk or issue.

Simulation

A quantitative technique used to model the potential outcomes of a project based on risks.

Probability vs. impact

A comparison used to prioritize risks based on how likely they are to occur and how much force they will have.

Situational/scenario analysis

A risk analysis technique that explores different hypothetical outcomes based on specific conditions.

Interconnectivity

A factor in risk analysis referring to how various risks are linked or influence one another.

Detectability

A factor in risk analysis determining how easily a risk or its triggers can be identified.

Prioritization

The order of importance assigned to risks or issues to guide management focus.

Issue tracking

The continuous process of monitoring existing problems that are currently affecting the project.

Connections between issues and changes

The relationship where an unresolved problem leads to a formal request for modification.

Resolution plan

A documented strategy for addressing and closing an identified project issue.

Outcome documentation

The recording of the results after an issue has been resolved or a risk response executed.

Connections between risks and issues

The relationship where a realized risk becomes an active project issue.

Connection between risks and changes

The relationship where managing a potential risk requires a modification to the project plan.

Escalation path

The predefined sequence of steps or levels for reporting and resolving issues that cannot be handled at the current level.

Ownership (Issue Management)

The assignment of a specific individual to be responsible for the resolution of an issue.

Execute contingency plans

The act of performing a pre-planned set of actions when a specific risk event occurs.

Root cause analysis

The process of identifying the underlying reason for an issue to prevent it from recurring.

Contingency/fallback plans

Backup plans developed to be used if the primary plan fails or a risk occurs.

Risk management strategies

High-level approaches used to handle potential threats and opportunities.

Issue severity

A measure of the seriousness or intensity of a project issue.

Impact to project (Issue Identification)

An assessment of how an active issue is currently affecting project constraints.

Urgency

The degree to which an issue requires immediate attention or resolution.

Scope of impact to organization

A measure of how far-reaching the effects of an issue are within the broader company.

Issue escalation

The process of moving an issue to a higher management level for resolution.

Work-arounds

Unplanned responses to issues when no prior contingency plan existed.

Points of escalation

Specific contacts or roles designated to receive escalated project issues.

Upcoming milestones

Significant points or events in the project timeline used for tracking progress.

Activity identification

The process of defining the specific actions required to produce project deliverables.

Sprint goals

The specific objectives set for a short, time-boxed period of work in Agile.

Sequencing

The process of identifying and documenting relationships among project activities.

Dependencies

The relationships between activities that determine the order in which they must be performed.

Hard logic

A type of sequencing dependency also known as mandatory logic.

Mandatory logic

A constraint that is inherently required by the nature of the work being done.

Soft logic

A type of sequencing dependency also known as discretionary logic.

Discretionary logic

A dependency based on best practices or specific preferences rather than physical constraints.