The fundamentals of project management, whatever approach you use afterward (predictive, agile or hybrid): lifecycle, planning, delivery, governance, best practices and change management. The entry point of the Project Management & Agile cluster, meant to build a structured overview of the discipline before specializing.
Project management involves precise vocabulary and a defined sequence of phases that need to be second nature in a steering meeting: initiation, planning, execution, monitoring, closure, along with cross-cutting notions like the triangle of scope, cost and time, or risk management. Documentation alone doesn't anchor this vocabulary well — after 48 hours, passive re-reading leaves only about 30% of the content in memory.
Flashcards with spaced repetition work differently: every card forces you to actively retrieve a definition or a concept, rather than simply recognizing it while reading. The FSRS algorithm reschedules each card right before you'd forget it, which shortens the time needed to reach a given level of mastery.
This category is meant as a generic entry point: it prepares you equally well for traditional (predictive) project management and for an agile or hybrid context, before you move on to the Agile Methods, Scrum and Kanban, or PMO and Governance categories.
In practice, many professionals move between several frameworks over the course of their career — an internal methodology, a standard like the PMBOK, an agile approach — without the underlying vocabulary changing fundamentally. Consolidating this common foundation upfront makes it easier to pick up any specific framework later, instead of starting from scratch each time.
This also matters in job interviews and cross-team meetings, where recruiters and colleagues alike expect a shared baseline vocabulary regardless of the specific methodology your previous employer used.
Six subtopics structure the Project Management category, from the project lifecycle to cross-cutting principles.
The classic phases of a project — initiation, planning, execution, monitoring and closure — and the vocabulary tied to each of them.
Progress tracking, milestones, steering indicators, risk management and dependency management between tasks.
Decision-making bodies, roles and responsibilities, arbitration — the structure that frames decision-making on a project.
Proven practices to scope a project, communicate with stakeholders and limit scope creep.
Supporting teams and end users through the adoption of a new process, tool or organization resulting from the project.
Cross-cutting notions that come up across every approach to project management, predictive and agile alike.
A simple progression, meant to build an overview before specializing toward agile, governance or a certification.
Fundamentals and project lifecycle give you the general framework — the foundation every other subtopic builds on.
Once the lifecycle is in place, delivery/tracking and governance add the organizational and decision-making dimension.
Best practices and change management round out the picture with reflexes you can apply directly on the ground.
15 to 20 minutes a day is enough: the FSRS algorithm automatically adjusts the frequency of each card based on your answers, focusing on notions that are still fragile rather than those already well anchored, so you don't waste time re-reviewing what you already know.
Yes, that's exactly what it's designed for. The Fundamentals and project lifecycle and Core principles subtopics cover the basics before moving on to more specific notions like governance or change management.
No. The concepts covered here — lifecycle, tracking, governance, best practices — are cross-cutting and useful regardless of the approach. For agile-specific concepts, the Agile Methods category complements this one.
Project Management covers steering a single project. PMO and Governance covers the broader organizational dimension: multi-project portfolios, committees, stakeholders across the organization.
It's not required, but starting with Fundamentals and project lifecycle makes the following subtopics easier to understand, since they build on this base vocabulary.
They consolidate the general vocabulary of project management, which helps prepare for a certification, but the dedicated Project Certifications category is more directly aligned with the specific vocabulary of these bodies of knowledge.
It depends on how consistent you are. With 15 to 20 minutes a day, most learners see solid initial retention within a few weeks; the FSRS algorithm then spaces out cards you already master well.
Yes. Project management vocabulary is used by many roles that interact with projects without leading them directly — developers, designers, support staff, managers — to better understand steering decisions and communicate effectively with the project team.
Two natural next steps: PMO and Governance to go deeper into the organizational dimension, or switch to an agile context with Agile Methods then Scrum and Kanban, depending on the type of projects you work on.
Yes, this category exists in both English and French, with the same 6-subtopic breakdown in each language.
No. The vocabulary covered here is organizational and methodological rather than technical — it applies equally to software projects, construction, marketing campaigns or any other type of project.
Yes. Even a freelancer running a single client engagement benefits from a shared vocabulary around scope, milestones and change requests — it makes conversations with clients clearer and reduces the odds of scope disputes later on.
Access the decks in the Project Management category, free and premium.
See the decks