Home › Study Guides › CAPM Study Plan: An 8-Week Week-by-Week Schedule
A real schedule with weekly targets, not vague advice to read the PMBOK Guide and take practice tests.
A CAPM study plan that actually works runs about eight weeks at six to eight hours a week, split across the exam's four domains: fundamentals, predictive, agile, and business analysis frameworks. Weeks one through five build content knowledge. Weeks six through eight add full-length practice exams and targeted remediation. "Read the PMBOK Guide and take practice tests" is technically correct advice, but it does not tell you what to do on a Tuesday. This does.
If you have more or less time than eight weeks, the structure still holds. Compress or stretch the weeks. What you should not do is skip the practice-testing weeks to save time. That is the part candidates cut first and regret most.
Before week one, confirm your eligibility and register. Building a study calendar around a date you have not locked in is how an eight-week plan quietly becomes a fourteen-week plan. Registering first creates a deadline, and the deadline is what does the work.
Week one is project management foundations. Cover the basic vocabulary: project versus program versus portfolio, the project life cycle, organizational structures from functional through matrixed to projectized, and the role of the project charter. Everything later builds on getting these terms precise rather than approximate. Build your first flashcard set for core terminology. The end-of-week check: can you explain the difference between a program and a portfolio without looking it up?
Week two covers the predictive process groups — initiating, planning, executing, monitoring and controlling, and closing. This is the traditional backbone and still a large share of CAPM content. Map each process group to its key outputs: the charter to initiating, baselines to planning, deliverables to executing. Drill the input and output relationships between processes, because that is where situational questions live. Start a weekly practice habit here, ten to fifteen questions, untimed, reviewing every wrong answer.
Week three is scope, schedule and cost. These three knowledge areas generate a disproportionate share of exam questions because they are where the formulas live. Memorise and practise earned value management — planned value, earned value, actual cost, cost variance, schedule variance, and the cost and schedule performance indices. Practise building a simple work breakdown structure and a network diagram. Then do fifteen to twenty questions focused specifically on earned value, which is the single highest-leverage formula topic on the exam.
Week four covers quality, resources, communications and risk. For quality, the cost of quality and the difference between quality assurance and quality control. For resources, RACI charts and the team development stages: forming, storming, norming, performing, adjourning. For risk, qualitative versus quantitative analysis, the risk register, and the response strategies of avoid, mitigate, transfer and accept. Another fifteen to twenty questions across the four areas.
Week five is agile and hybrid, and it is the week people underestimate. PMI's current exam content outline weights agile and hybrid content heavily, and treating it as an afterthought is the most common reason candidates fail. It will trip you up harder if your own work experience is entirely waterfall. Cover the core roles of product owner, scrum master and development team; the events of sprint planning, daily standup, sprint review and retrospective; and when and why teams blend predictive and agile approaches. Weight your twenty practice questions toward agile scenarios, because that is where waterfall-background candidates lose the most points.
Week six is your first full-length practice exam. Take all 150 questions timed, under real conditions, with no pausing and no notes. Then spend at least as long reviewing it as you did taking it. Score by domain rather than overall percentage — you need to know which of the four domains is weakest, not just your total. Rebuild flashcards for every concept behind a missed question.
Week seven has no fixed curriculum. It is driven entirely by what week six exposed. Spend it almost wholly on your two or three weakest areas, re-taking short quizzes of twenty to thirty questions isolated to those areas until you are consistently getting them right. Give the strong areas a quick pass to keep them fresh, nothing more.
Week eight is your second full-length exam, taken early in the week, then a taper. Compare domain scores against the first exam; you should see clear improvement in whatever you targeted in week seven. For the last two or three days before the real thing, light review only, mostly flashcards. No new material and no more full-length exams. Cramming in the final 48 hours tends to lower confidence more than it raises scores.
Adjusting this to your own schedule is fine and often smarter. If you are working full time, spreading it into ten to twelve weeks at five or six hours a week is more sustainable than compressing it, and a plan you stick to beats an aggressive one you abandon in week three. If you already have solid project management experience, weeks one through four will feel familiar and can be compressed. Do not skip week five even if you feel confident, because agile is the domain experienced waterfall project managers most reliably underestimate.
One last thing about practice questions: do not wait until week six to touch one. By then a wrong answer tells you nothing useful, because you have no baseline to say whether it is a knowledge gap or a fresh mistake. Weaving in short sets from week two onward gives you a running signal on where you actually stand, which is the whole point of practising in the first place.
Read this in the CoStudy app →