CompTIA Project+ (PK0-005) flashcards

A security technique that regulates who or what can view or use resources in a computing environment.

• Ensures data confidentiality and integrity.
• Typically uses authentication and authorization.
• Can be role-based, attribute-based, or discretionary.

Memory trick: Govern your data like a kingdom: control who enters, what they do, and keep it in good shape.

The information needs of project stakeholders, including what information is needed, by whom, when, and how it should be delivered.

• Vary based on stakeholder role and influence.
• Form the basis for the communication management plan.
• Consider factors like urgency, confidentiality, and format.

Memory trick: Know your audience, know your message, know how to deliver.

A logical relationship where the successor activity cannot begin until the predecessor activity has completed.

• Most common type of dependency in project management.
• Predecessor must finish before successor can start.
• Often seen in sequential project phases.

Memory trick: Finish Strong, Start Fresh: FS is the standard path.

A technique used to identify the underlying reasons for deviations from the project schedule, enabling the project manager to implement effective corrective actions.

• Focuses on 'why' the problem occurred.
• Helps prevent recurrence of the issue.
• Essential for effective schedule control and corrective action planning.

Memory trick: When the schedule 'stumbles', first 'diagnose' the 'ailment' before giving medicine.

A component of the project management plan that describes how, when, and by whom project information will be administered and disseminated.

• Defines communication requirements for all stakeholders.
• Specifies communication methods, formats, content, and frequency.
• Ensures effective and efficient information flow.

Memory trick: Plan your talk, don't just ramble.

The process of prioritizing risks for further analysis or action by assessing and combining their probability of occurrence and impact.

• Outputs include updated risk register and risk report.
• Helps to focus attention on high-priority risks.
• Often uses probability and impact matrix for assessment.

Memory trick: Identifying, Analyzing, Responding, Monitoring: The Risk Journey.

A document describing the work, deliverables, timeline, and acceptance criteria for a vendor or contractor.

• Used primarily in procurement/contracting
• Defines scope of vendor deliverables
• Includes acceptance criteria and timeline

Memory trick: SOW = Scope Of Work you sow with a vendor

The process of identifying and addressing constraints in a Kanban workflow to improve flow, typically by shifting resources or adjusting WIP limits.

• Bottlenecks indicate a stage where work accumulates.
• Limiting WIP helps expose bottlenecks.
• Cross-functional teamwork is key to resolving bottlenecks.

Memory trick: Kanban's flow is smooth when bottlenecks are removed, like clearing a traffic jam.

The amount of time an activity can be delayed without delaying the project end date or violating a schedule constraint.

• Indicates scheduling flexibility.
• Activities on the critical path have zero float.
• Can be total float or free float.

Memory trick: Float is like a 'breather' in the schedule, a 'cushion' for tasks.

A project management technique that identifies the longest sequence of activities in a project schedule, which determines the minimum time required to complete the project. Any delay in critical path activities will delay the entire project.

• Identifies the longest path of dependent tasks.
• Determines the earliest project completion date.
• Often visualized and managed using Gantt charts.

Memory trick: Gantt charts map the grand path.

The process of estimating the type and quantities of material, human resources, equipment, or supplies required to perform each activity.

• Output is Activity Resource Requirements.
• Considers resource availability and skills.
• Feeds into cost and duration estimates.

Memory trick: To estimate activities, you need Activity Resource Requirements.

Data Lifecycle Management (DLM) is a comprehensive approach to managing the flow of an information system's data from creation and initial storage to its obsolescence and eventual deletion.

• Covers data creation, storage, use, sharing, archiving, and destruction.
• Ensures compliance with regulatory requirements and internal policies.
• Aims to optimize data value, reduce risks, and control costs.

Memory trick: DLM: Data Lives, Managed from Start to End.

A forecast of the total cost of a project when all work is completed, based on current project performance.

• Calculated using different formulas depending on assumptions about future performance.
• Compares actual costs to date with estimated costs for remaining work.
• Provides a revised total budget projection.

Memory trick: EAC forecasts the final cost, based on current project pace.

The final phase of the project life cycle, where all activities are formally completed, and the project is officially closed.

• Involves obtaining final acceptance from the customer.
• Ensures all contractual obligations are met.
• Releases project resources and archives project documents.

Memory trick: Final review means checking off obligations for project closure.

A technique used for building a project schedule network diagram that graphically represents the logical relationships (dependencies) among the project activities.

• Also known as Activity-on-Node (AON).
• Uses four types of logical relationships: Finish-to-Start (FS), Start-to-Start (SS), Finish-to-Finish (FF), Start-to-Finish (SF).
• Forms the basis for schedule analysis.

Memory trick: PDM links activities like dominoes.

A data storage architecture that manages data as objects, which are self-contained units with data, metadata, and a unique identifier, accessible via APIs over HTTP.

• Highly scalable and durable.
• Ideal for unstructured data (images, videos, backups).
• Accessed via APIs, not traditional file systems.

Memory trick: Cloud storage: Block is a disk, Object is a bucket, Archive is a vault, Ephemeral is temporary.

The approved version of a project plan component (scope, schedule, or cost) used as a fixed reference point to measure actual performance and variance.

• Established at the end of planning, before execution begins
• Common types: scope baseline, schedule baseline, cost baseline
• Changes to a baseline require formal change control approval

Memory trick: Baseline = the starting line 🏁 you measure your race against.

The process of prioritizing risks for further analysis or action by assessing and combining their probability of occurrence and impact. It uses descriptive terms (e.g., High, Medium, Low).

• Uses subjective judgment and descriptive scales.
• Helps prioritize risks without detailed numerical calculation.
• Often a precursor to quantitative risk analysis.

Memory trick: High risk, high response: Plan for the worst, hope for the best.

Funds, budget, or time identified to offset the impact of scheduled risk events that are 'known unknowns' (i.e., identified risks for which mitigation plans are developed).

• Part of the cost baseline.
• Managed by the project manager.
• Accounts for identified risks.

Memory trick: Budgeting is like packing for a trip; you pack the essentials, then add a 'just in case' bag.

The final phase of the project life cycle where deliverables are formally accepted, contracts are closed, resources are released, and lessons learned are documented.

• Includes formal sign-off/acceptance from the customer
• Archives all project documentation for future reference
• Captures lessons learned to improve future projects

Memory trick: 'I Plan Every Move Carefully' = Initiation, Planning, Execution, Monitoring, Closing.

A responsibility assignment matrix that maps out who is Responsible, Accountable, Consulted, and Informed for each task or deliverable in a project.

• R = Responsible (performs the task)
• A = Accountable (owns the task's completion, only one 'A' per task)
• C = Consulted (provides input)
• I = Informed (receives updates)

Memory trick: RACI: Responsibility Always Clarifies Involvement.

Tools designed to support iterative development, flexibility, and continuous delivery in agile project environments.

• Supports frameworks like Scrum and Kanban.
• Emphasizes flexibility and rapid iterations.
• Ideal for innovative or rapidly changing projects.

Memory trick: Choose your project software like you choose your shoes: fit the terrain!

The process of transforming plain text data into a coded format (ciphertext) to prevent unauthorized access.

• Protects data confidentiality.
• Can be applied to data at rest (stored) and data in transit (over networks).
• Essential for meeting many data privacy regulations.

Memory trick: Data Protection: Encrypt, Access, Audit your Assets.

A traffic light indicator (Red, Amber, Green) used to quickly communicate the overall health or status of a project or its key components.

• Red: Significant issues, off track.
• Amber: Minor issues, potential for deviation.
• Green: On track, no significant issues.

Memory trick: RAG status: Red means stop, Amber means caution, Green means go!

A 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.

• Held at the same time and place each day.
• Attended by the Development Team.
• Focuses on progress toward the Sprint Goal and impediments.

Memory trick: Scrum's daily sprint check-in keeps everyone in sync.

Security by Design is a cybersecurity principle that emphasizes the importance of building security into the software and systems from the initial design phase, rather than adding it as an afterthought.

• Proactive approach to security.
• Integrates security controls throughout the development lifecycle.
• Aims to prevent vulnerabilities rather than remediate them.

Memory trick: Design Security: Build it in, don't bolt it on.

A logical relationship where the successor activity cannot start until the predecessor activity has started. It can include a lag or lead time.

• Successor starts after predecessor starts.
• Often used when tasks can be partially parallel.
• Example: 'Pour foundation' can start when 'Excavate site' starts, but not necessarily immediately.

Memory trick: FS, SS, FF, SF: Friends Start, Sisters Finish, Fathers Start, Sons Finish.

A data gathering technique that involves a group of team members or subject matter experts to identify as many risks as possible in a short period.

• Encourages free-thinking and rapid idea generation.
• Facilitated by a neutral party.
• Aims for quantity of ideas, then quality.

Memory trick: To find all the 'hidden rocks', you need to 'shake the tree' with group ideas.

The Scrum role responsible for maximizing the value of the product and the work of the Development Team, primarily through managing and prioritizing the Product Backlog.

• Acts as the voice of the customer/stakeholders.
• Prioritizes items in the Product Backlog.
• Ensures the Development Team understands product backlog items.

Memory trick: POS: Product Owner, Scrum Master, Development Team are the three pillars of Scrum.

A formal event in Scrum where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. It is a key inspect and adapt opportunity.

• Held at the end of a Sprint.
• Team demonstrates completed work (Increment).
• Stakeholders provide feedback and collaborate on future direction.

Memory trick: Review feedback, Refine backlog, Repeat.

A core practice in Kanban that restricts the number of items in a specific workflow stage. This helps manage flow, prevent bottlenecks, and encourages teams to finish work before starting new tasks.

• Limits work in progress for each column/stage.
• Helps identify bottlenecks and improve flow.
• Forces focus on completing tasks.

Memory trick: Visualize, Limit, Manage, Improve, Feedback, Collaborate.

An earned value metric calculated as EV minus PV, indicating whether a project is ahead of, on, or behind schedule.

• Formula: SV = EV - PV
• Negative SV = behind schedule
• Positive SV = ahead of schedule; zero = on schedule

Memory trick: SV = 'Earned minus Planned' — negative means you're lagging

The longest sequence of scheduled activities that must be completed on time for the entire project to be completed on time. Activities on the critical path have zero float (slack), meaning no delays are permissible without extending the project duration.

• Determines the shortest possible project duration.
• Activities have no flexibility in their start or end dates.
• Requires close monitoring and management to prevent project delays.

Memory trick: Critical is zero float, Fast-track speeds, Dependency links, Slack allows give.

A set of guiding principles for software development and project management that prioritize individuals and interactions, working software, customer collaboration, and responding to change.

• Customer satisfaction through early and continuous delivery.
• Welcome changing requirements.
• Deliver working software frequently.
• Business people and developers work together daily.

Memory trick: Agile acts like a compass, guiding through uncertainty with quick turns.

A collection of tools and techniques used to gather, integrate, and disseminate the outputs of project management processes, often including software for scheduling, resource management, and collaboration.

• Provides a centralized source of truth for project data.
• Facilitates communication and collaboration for distributed teams.
• Integrates various project management functions into one system.

Memory trick: PMIS is the Swiss Army knife for project managers.

The process of reviewing all change requests, approving changes, and managing changes to deliverables, organizational process assets, project documents, and the project management plan.

• Applies to scope, schedule, budget, and quality baselines.
• Often involves a Change Control Board (CCB).
• Ensures only approved changes are implemented.

Memory trick: Change Control: Stop, Review, Go or No.

The set of rules, policies, and processes that ensure the effective and secure use of cloud resources, aligning with organizational objectives and regulatory requirements.

• Includes financial, operational, security, and compliance aspects.
• Crucial for managing risks and ensuring regulatory adherence in the cloud.
• Addresses data residency, access control, and auditability.

Memory trick: Cloud Governance: Cost, Security, Compliance, Operations.

A telecommunications network that extends over a large geographical area, connecting multiple local area networks (LANs).

• Used for inter-site communication.
• Often involves carriers like ISPs, using technologies such as MPLS, SD-WAN, or VPNs.
• Critical for distributed enterprises and cloud connectivity.

Memory trick: LAN is Local, WAN is Wide, MAN is Medium.

A formal document that outlines the strategy and tactics for managing the transition of individuals, teams, and organizations from a current state to a desired future state.

• Addresses resistance to change.
• Includes communication, training, and support strategies.
• Crucial for successful project adoption and benefits realization.

Memory trick: Change Management: Plan, Communicate, Support the Transition.

The knowledge area that includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully.

• Focuses on defining and controlling what is and is not in the project.
• Includes collecting requirements and creating the Work Breakdown Structure (WBS).
• Helps prevent scope creep.

Memory trick: Scope defines the 'what' of the project.

The knowledge area that ensures timely and appropriate planning, collection, creation, distribution, storage, retrieval, management, control, monitoring, and ultimate disposition of project information.

• Crucial for stakeholder engagement and project success.
• Involves identifying communication requirements.
• Includes processes for information flow.

Memory trick: Communication is the oil that keeps the project engine running smoothly.

A short, daily meeting in agile project management where team members synchronize activities and plan for the next 24 hours by answering three key questions.

• Typically 15 minutes or less.
• Focuses on 'What did I do yesterday?', 'What will I do today?', 'Are there any impediments?'.
• Promotes communication, transparency, and quick issue identification.

Memory trick: Daily stand-ups keep everyone standing together, informed and clear.

One of the twelve principles behind the Agile Manifesto, it states that agile processes harness change for the customer's competitive advantage. This means being able to adapt plans and priorities based on new information and feedback.

• Embraces change as an opportunity, not a problem.
• Allows for flexibility in project direction.
• Contributes to delivering higher customer value.

Memory trick: I Work, Customers Respond to Change.

A logical relationship where a successor activity cannot start until a predecessor activity has finished, and there's an additional waiting period (lag) after the predecessor's completion before the successor can begin.

• Most common type of dependency.
• Lag is a positive duration of time that must pass before the successor can start.
• Represented as FS+Lag.

Memory trick: FS with a lag is like waiting for paint to dry after a task is done.

A core Kanban principle that restricts the number of items in progress at each stage of a workflow, preventing bottlenecks and improving flow.

• Forces completion of current tasks before starting new ones.
• Highlights bottlenecks in the workflow.
• Improves throughput and reduces lead time.

Memory trick: Kanban helps you see the flow, limit the WIP, and improve continuously.

A project management technique used to analyze and represent the tasks involved in completing a project, especially when activity durations are uncertain.

• Uses three-point estimates: optimistic, pessimistic, most likely.
• Calculates a weighted average for expected activity duration.
• Helps manage uncertainty in project schedules.

Memory trick: Uncertainty asks for PERT's three-point view.

A project document used to record and track all identified project issues, including their description, impact, owner, status, and resolution plan, to ensure they are addressed systematically.

• Documents problems that have already occurred.
• Assigns ownership for issue resolution.
• Monitors status and tracks progress until closure.
• Distinct from a risk register, which tracks potential future events.

Memory trick: Issue Log solves problems, Risk Register warns, CCB decides, RTM links.

Software applications and platforms designed to facilitate virtual meetings, collaboration, and communication among project teams, especially those working remotely or across different locations.

• Enable online conferencing and screen sharing.
• Often include shared whiteboards, chat, and polling features.
• Critical for distributed teams to maintain effective communication.

Memory trick: Meeting tools make distant teams meet.

A comprehensive software solution that combines multiple project management functions (e.g., scheduling, resource management, collaboration, reporting) into a single platform to provide a unified view and control over a project.

• Offers real-time visibility into project progress and dependencies.
• Facilitates planning, execution, and monitoring.
• Crucial for managing complex projects with many interdependencies.

Memory trick: Integrated software Illuminates the entire project.

A measure of schedule efficiency on a project, expressed as the ratio of earned value to planned value.

• Formula: SPI = EV / PV.
• SPI > 1.0 indicates ahead of schedule.
• SPI < 1.0 indicates behind schedule.
• SPI = 1.0 indicates on schedule.

Memory trick: SPI is EV over PV, CPI is EV over AC.

A significant point or event in the project schedule with zero duration, used to mark progress.

• Has zero duration
• Marks completion of a phase or major event
• Used for tracking progress and reporting

Memory trick: Milestone = a flag with no width, just a marker

Advanced features in project management software that optimize resource allocation by addressing over-allocation (leveling) and allow for testing different scheduling scenarios (simulation) to find the most efficient project plan.

• Resolves resource conflicts and overloads.
• Adjusts task start/end dates based on resource availability.
• Enables 'what-if' analysis to explore alternative schedules.
• Aims to optimize project duration and resource utilization.

Memory trick: Leveling balances, Sims test, Gantt shows, RACI assigns, Burndown burns.

A scheduling technique that adjusts start/finish dates to resolve resource overallocation, often extending the schedule.

• Used when a resource is overallocated
• May extend the project timeline
• Does not change scope or add resources

Memory trick: Leveling = leveling out one worker's overloaded plate

An API is a set of defined rules that enable different software applications to communicate with each other, allowing for data exchange and functionality integration.

• Acts as an intermediary between systems.
• Facilitates real-time data exchange.
• Crucial for modern system integrations and microservices architectures.

Memory trick: API: Apps Project Interactions.

Core tenets of the General Data Protection Regulation (GDPR) that dictate how personal data must be processed and protected.

• Lawfulness, fairness, and transparency.
• Purpose limitation, data minimization.
• Accuracy, storage limitation, integrity, and confidentiality.
• Accountability.

Memory trick: GDPR: 'My Data' is 'My Right' – Protect it by Design.

The process of aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline.

• Occurs in the planning phase.
• Takes cost estimates as input.
• Output is the cost baseline.

Memory trick: Every Cost Plan is Determined and Controlled.

Choosing project management tools that support iterative development, flexible planning, continuous feedback, and adaptation, particularly suitable for projects with high uncertainty or evolving requirements.

• Prioritizes adaptability over rigid planning.
• Focuses on incremental delivery and rapid feedback.
• Common tools include burndown/burnup charts, Kanban, Scrum boards.

Memory trick: Agile tools adapt to uncertainty and change.

An Agile framework for developing, delivering, and sustaining complex products, characterized by iterative increments (sprints), self-organizing teams, and continuous feedback.

• Ideal for projects with high uncertainty and evolving requirements.
• Emphasizes transparency, inspection, and adaptation.
• Relies on a Product Owner, Scrum Master, and Development Team.

Memory trick: For complex, evolving projects, Scrum is the nimble guide.

A Scrum role responsible for maximizing the value of the product resulting from the work of the Development Team. The Product Owner is accountable for effective Product Backlog management.

• Represents the voice of the customer/stakeholders.
• Manages and prioritizes the Product Backlog.
• Ensures the value of the work done by the Development Team.

Memory trick: The Product Owner 'O'wns the vision and the value.

In cryptography, confidentiality ensures that information is accessible only to those authorized to have access, preventing unauthorized disclosure.

• Achieved through encryption.
• Protects sensitive data from eavesdropping.
• A core component of the CIA Triad.

Memory trick: CAN I: Confidentiality, Authentication, Non-repudiation, Integrity.