CompTIA Project+ Foundations
A structured CompTIA Project+ course covering fundamentals, life cycle, scope, resources, communication, and Agile, with linked practice questions.
Course progress
0 / 5
Back to courses
What you will learn
- Describe project fundamentals and life cycle.
- Explain scope, schedule, and cost.
- Describe resources, quality, and risk.
- Explain communication and stakeholders.
- Describe Agile and hybrid approaches.
Before you start
- Basic business familiarity is helpful.
- No project management experience is required.
- No previous CompTIA certification is required.
Lesson 1 Project Fundamentals and Life Cycle
CompTIA Project+ validates practical project management skills for entry-level and mid-level professionals. A project is a temporary endeavor with a defined objective, while a program groups related projects and a portfolio aligns them with strategy. Stakeholders are anyone affected by or able to affect the project. The project charter authorizes work, and the business case justifies it. Projects follow phases: initiation, planning, execution, monitoring and controlling, and closing. Phase gates review progress, milestones mark important points, and a work breakdown structure decomposes deliverables. A project manager balances constraints such as scope, time, cost, quality, resources, and risk.
Example
Example: An organization approves a project charter, forms a program to coordinate related efforts, and uses phase gates to review each stage.Lesson 2 Scope, Schedule, and Cost
Scope, schedule, and cost are core project constraints. Scope defines the work required, and requirements describe capabilities the project must meet. A Gantt chart shows tasks and dependencies, and the critical path determines the shortest possible duration. Estimates predict effort and cost, and the budget is the approved cost plan. Baselines are approved plans used to measure performance. Change control reviews scope changes, while uncontrolled growth is scope creep. A work breakdown structure organizes deliverables into manageable packages. Project managers monitor actuals against baselines, update schedules, and communicate changes through a formal change process.
Example
Example: A project manager builds a WBS, calculates the critical path, and uses change control when a sponsor requests an additional feature.Lesson 3 Resources, Quality, and Risk
Projects need people, equipment, and materials. Resource planning identifies what is needed and when. Quality measures whether deliverables meet requirements, and defects are nonconformances that must be corrected. Risks are uncertain future events, while issues are current problems. A RAID log tracks risks, assumptions, issues, and dependencies. Assumptions are beliefs accepted for planning, and dependencies define relationships between tasks. Risk responses include mitigation, avoidance, transfer, and acceptance. Regular quality reviews, testing, and inspections prevent defects. Teams should update the RAID log frequently and escalate unresolved issues.
Example
Example: A team records a delivery risk in the RAID log, mitigates it with a backup vendor, and escalates a current staffing issue.Lesson 4 Communication and Stakeholders
Communication keeps stakeholders informed and projects moving. A communication plan defines who receives what information, when, and through which channel. Status reports update progress and issues, and meeting agendas keep meetings focused. Stakeholder analysis assesses interest, influence, and needs. Escalation raises unresolved issues to higher authority, and decision logs record decisions. Lessons learned capture experience for future projects, and kickoff meetings align the team. Retrospectives review what went well and what to improve. Clear communication reduces misunderstandings, builds trust, and helps teams identify risks early.
Example
Example: A weekly status report shares progress, an escalation resolves a blocked approval, and a retrospective improves the next sprint.Lesson 5 Agile and Hybrid Approaches
Agile project management delivers value in small increments with frequent feedback. Sprints are timeboxed iterations, and the product backlog is a prioritized list of work. The Product Owner prioritizes value, the Scrum Master facilitates the team, and developers build increments. Daily standups keep the team aligned, and burndown charts show remaining work. Kanban boards visualize workflows and limit work in progress. Retrospectives help teams improve. Hybrid approaches combine predictive and adaptive methods when parts of a project need upfront planning and others need flexibility. Project+ expects professionals to understand when Agile, predictive, or hybrid is appropriate.