Back to CompTIA Project+ (Project+)

Project Management Concepts

Understand project characteristics, methodologies, risk management, scheduling, quality, communication, team management, and procurement (33% of exam).

Covers fundamental project management knowledge including project characteristics, methodologies (Agile vs. Waterfall), and frameworks. Encompasses change control processes, risk management strategies, issue tracking and resolution, schedule management with milestones and resource estimation, quality and performance management through retrospectives and KPIs, communication methods and meeting management, team and resource management including role definitions and performance management, and procurement with vendor selection and contract evaluation.
5 minutes 5 Questions

Project Management Concepts form the foundation of the CompTIA Project+ certification, encompassing essential principles that guide successful project delivery. A project is defined as a temporary endeavor undertaken to create a unique product, service, or result, with a definite beginning and end …

Concepts covered: Project characteristics, Project methodologies overview, Project management frameworks, Agile methodology, Waterfall methodology, Agile vs. Waterfall selection criteria, Hybrid project management approaches, Scrum framework, Kanban methodology, Lean project management, Team composition in different methodologies, Communication methods by methodology, Change control processes, Change request management, Change control board (CCB), Impact analysis for changes, Configuration management, Risk identification, Risk analysis techniques, Qualitative risk analysis, Quantitative risk analysis, Risk response strategies, Risk mitigation planning, Risk monitoring and control, Risk roles and responsibilities, Risk register management, Issue identification and tracking, Issue resolution processes, Issue escalation procedures, Issue documentation and outcomes, Issue log management, Milestone identification, Activity sequencing, Work breakdown structure (WBS), Resource estimation, Duration estimation, Critical path method, Schedule development, Schedule maintenance and updates, Schedule compression techniques, Dependencies and constraints, Quality management planning, Sprint retrospectives, Sprint reviews, Service-level agreements (SLAs), Key performance indicators (KPIs), Project audits, Testing cycles, Quality assurance vs. quality control, Continuous improvement, Communication methods assessment, Communication platforms, Communication plan development, Stakeholder communication strategies, Status reporting, Information distribution, Meeting agenda setting, Meeting roles and responsibilities, Timeboxing techniques, Action item documentation, Meeting minutes, Daily standup meetings, Resource gap analysis, Team performance management, Role definitions, RACI matrix, Team building, Conflict resolution, Virtual team management, Resource leveling, Resource allocation, Vendor evaluation criteria, Contract types, Procurement methods, Request for proposal (RFP), Request for quotation (RFQ), Vendor selection process, Contract negotiation, Procurement documentation

Test mode:
Start practice test
Project+ - Project Management Concepts Example Questions

Test your knowledge of Project Management Concepts

Question 1

Tom is the project manager for a manufacturing equipment upgrade. His organization has shortlisted two vendors after the RFP evaluation phase. Vendor Alpha offers a comprehensive solution with a 20% higher cost but includes extensive training and a five-year warranty. Vendor Beta proposes a lower-cost solution with minimal training and a two-year warranty. Both vendors have comparable technical scores. The CFO prefers Vendor Beta due to budget concerns, while the operations director strongly supports Vendor Alpha for long-term value. Tom needs to facilitate a final decision that satisfies organizational objectives. What should Tom do to resolve this vendor selection conflict?

Correct Answer: Conduct a total cost of ownership analysis comparing both vendors over the expected equipment lifecycle

The best approach for Tom is to conduct a total cost of ownership (TCO) analysis comparing both vendors over the expected equipment lifecycle.

This is the correct answer because:

  1. TCO analysis provides an objective, data-driven framework that addresses both stakeholders' concerns - the CFO's budget focus and the operations director's long-term value perspective.

  2. It captures all costs over the equipment's lifecycle, including initial purchase price, training costs, warranty coverage, potential maintenance after warranty expiration, and operational efficiency gains.

  3. This approach transforms a subjective conflict into an objective comparison, making it easier to reach consensus based on facts rather than opinions.

  4. It aligns with proper procurement practices by looking beyond initial costs to understand true value.

The other options are less effective:

  • Scheduling separate meetings to count supporter votes is not an appropriate decision-making method. Procurement decisions should be based on objective criteria and organizational benefit, not popularity contests among stakeholders.

  • Requesting revised proposals may be premature. Before asking vendors to revise their offers, Tom should first understand what the organization truly needs through proper analysis. Additionally, this approach delays the decision and may not resolve the fundamental disagreement.

  • Focusing a risk assessment solely on implementation timelines misses the core issue of the conflict, which centers on cost versus long-term value. While risk assessment is valuable, it should encompass more than just timelines and should support, not replace, a comprehensive cost-benefit analysis.

Question 2

What is the primary purpose of conducting a resource gap analysis during project planning?

Correct Answer: To identify discrepancies between the skills and quantity of resources needed versus those currently available to the project

The primary purpose of conducting a resource gap analysis during project planning is to identify discrepancies between the skills and quantity of resources needed versus those currently available to the project.

A resource gap analysis is a fundamental project management tool used during the planning phase to systematically compare what resources the project requires (in terms of both skill sets and quantity) against what resources are currently accessible. This analysis helps project managers:

  • Identify missing skills or competencies needed for project success
  • Determine if there are enough people with the right expertise
  • Plan for hiring, training, or procurement activities
  • Make informed decisions about resource allocation and acquisition strategies

This directly supports effective project planning by ensuring the project team understands resource shortfalls before work begins, allowing time to address these gaps through hiring, training, contracting, or reallocation.

The other answers, while touching on related project management concepts, misrepresent the core purpose of a resource gap analysis:

One option focuses on budget allocation and cost estimation, which is actually the purpose of cost management and budgeting processes, not resource gap analysis. While cost considerations may result from identifying resource gaps, determining total budget allocation is not the primary purpose of the gap analysis itself.

Another option describes performance benchmarking and establishing improvement targets, which relates to performance management and quality processes. A resource gap analysis is not primarily concerned with comparing current team productivity to industry standards, but rather with identifying missing resources needed for project completion.

The final option discusses variances between scheduled utilization rates and actual availability, which is more aligned with resource leveling and scheduling activities that occur during project execution and monitoring, not the initial gap analysis during planning. The gap analysis occurs before detailed scheduling and focuses on capability gaps rather than utilization variances.

Question 3

You are a project manager for a software company leading a team of 14 members who have been working on a customer relationship management platform for six months. During a recent team retrospective, you discover that the quality assurance testers and the development engineers have established an informal practice where they only communicate through a shared bug tracking system, avoiding all verbal or video discussions. The QA lead explains that written documentation creates an audit trail, while the development lead mentions that synchronous conversations often become confrontational when defects are discussed. Last month, a critical security vulnerability was logged in the system for three weeks before developers noticed it because neither group monitored the queue proactively. The product director has escalated concerns about response times to executive leadership and expects a remediation plan. What is the most effective team-building intervention to transform this avoidance-based communication pattern into constructive collaborative engagement?

Correct Answer: Facilitate a joint workshop where both groups co-create communication protocols that include regular brief synchronous check-ins alongside written documentation, establishing shared ownership for queue monitoring

The most effective team-building intervention is to facilitate a joint workshop where both groups co-create communication protocols that include regular brief synchronous check-ins alongside written documentation, establishing shared ownership for queue monitoring.

This approach is the best solution because it:

  1. Addresses the root cause: The underlying issue is conflict avoidance and lack of collaborative ownership. A joint workshop brings both teams together to solve the problem collectively rather than imposing a solution from above.

  2. Respects both perspectives: The QA team values audit trails (written documentation) while developers want to avoid confrontational conversations. This solution honors both needs by combining written documentation with structured, brief synchronous check-ins.

  3. Creates buy-in through participation: When team members co-create protocols themselves, they develop ownership and are more likely to follow through with the agreed-upon practices.

  4. Solves the immediate problem: Establishing shared ownership for queue monitoring addresses the critical issue of the security vulnerability sitting unnoticed for three weeks.

  5. Builds sustainable collaboration: This transforms the avoidance pattern into constructive engagement by teaching teams how to communicate effectively together.

The second option involving mandatory daily stand-ups with management attendance is problematic because it imposes a top-down solution, adds surveillance through required management presence, and may increase confrontation rather than resolve the underlying conflict avoidance issues.

The rotational liaison program creates a workaround rather than solving the communication problem. It actually reduces the need for group-level interactions, which perpetuates the avoidance pattern rather than transforming it into collaborative engagement.

The formal escalation matrix that routes issues to management relies entirely on hierarchical oversight and does not address the fundamental team dynamics problem. It treats symptoms rather than causes and does not build the collaborative relationship needed between QA and development teams.

More Project Management Concepts questions
2365 questions (total)
Start 100 question test