These free Scrum study guides help you organise your learning around empirical planning, product goals, collaboration, usable increments and adaptation. Use the learning-path comparison, topic explanations, reference glossary, six-week plan and original scenarios to connect study notes with useful decisions. Choose the path that matches your current experience and intended goal, then practise explaining why a solution fits the requirement.
Want free reference PDFs? Email freelearning@ciscoforall.com with your exam code and name. We will send an available older reference file free of charge. Availability varies. See the request section below.
Choose a learning path that matches your goals
These are learning orientations, not official exam blueprints. Confirm the exact qualification or exam and its current scope before using any resource as a preparation checklist.
| Learning path | Who it suits | Core topics | Practice activity |
|---|---|---|---|
| Scrum foundations | New learners | Purpose, accountabilities and feedback | Explain how a team learns from completed work. |
| Scrum Master learning | Learners supporting team effectiveness | Facilitation and impediment investigation | Design a conversation that exposes a blocker. |
| Product Owner learning | Learners shaping product value | Goals, ordering and stakeholder evidence | Compare two backlog choices against a goal. |
| Team delivery learning | People building usable increments | Quality, collaboration and adaptation | Write a shared completion checklist. |
Set your Scrum target and organise your resources
Choose one target and write down what you want to understand or perform. A learner building foundations needs a different sequence from someone reviewing an unfamiliar area before an exam. Use your current experience to identify the first gap, and give that gap a specific practice activity instead of collecting more files without a plan.
Keep a resource register with the document name, topic, publication date and applicable product or framework version. Older reference PDFs can explain foundations, but they may describe retired credential names or earlier behaviour. Mark version-dependent steps for verification. The learning paths on this page help organise study; they do not replace the current provider objectives.
Use a product goal to guide choices
A team building a customer portal receives several feature requests. Describe the outcome the product should improve before ordering the work. A goal helps the team discuss trade-offs and makes feedback more useful than a simple count of completed features.
Write a goal that identifies the user and intended improvement. Compare a convenience feature with a feature that removes a frequent user obstacle. Explain which evidence supports your choice and what remains uncertain. This exercise develops product reasoning rather than memorisation of a framework definition.
Make backlog items understandable
A useful work item describes a need clearly enough for a productive discussion. Include the user context, intended outcome and important constraints. Avoid treating a large list of technical tasks as proof that the user requirement is understood.
Rewrite a vague item such as “improve reports” into two smaller outcomes. Describe what the user should be able to do and how the team could check it. Identify a question that must be answered before implementation and a decision that can remain open until feedback is available.
Plan around a coherent objective
An iteration plan should help people coordinate around a purpose, rather than only collect unrelated work. Discuss available capacity, dependencies and uncertainties. State what the team is trying to achieve and what adjustment would still preserve that objective.
Create a planning exercise with a known dependency and a limited amount of team capacity. Identify a smaller useful outcome if the dependency fails. Avoid filling every moment with tasks before discussing uncertainty. A plan becomes more credible when the team can explain both its intention and its assumptions.
Build quality into usable results
Describe the conditions that make a result usable for its intended purpose. These can include review, testing and integration appropriate to the product. A partially completed activity can represent progress without yet being a usable result for a stakeholder.
Write a shared completion checklist for a fictional online form. Include normal input, invalid input and access requirements. Then examine a feature that works in isolation but has not been integrated. Explain which checks remain before it can satisfy the team’s agreed completion conditions.
Use reviews to obtain evidence
A review is more useful when stakeholders can discuss a working result and its effect on the product goal. Prepare questions about the user task, assumptions and next priorities. Avoid reducing feedback to whether the demonstration looked polished.
Create a review exercise where users complete a task using a small product increment. Record what they achieved, where they struggled and what changed in your understanding. Separate direct observations from guesses about user preferences. Use the evidence to explain a proposed change in the order of future work.
Turn retrospectives into small experiments
A team notices that work repeatedly waits for a review. Describe the pattern with specific observations and invite explanations from the people involved. A productive improvement conversation looks for a change the team can test, rather than assigning blame to a role.
Propose a small experiment such as an earlier review conversation. Identify the expected benefit, the person coordinating it and the evidence to examine next time. Do not introduce ten process changes at once; that makes the effect harder to understand. Keep the experiment connected to the observed problem.
Quick reference glossary
| Concept | Meaning in your notes | Question to answer |
|---|---|---|
| Product goal | A direction for product improvement | Which outcome guides the next choice? |
| Backlog item | A piece of intended product work | What user need and uncertainty does it contain? |
| Increment | A usable addition to the product | What can stakeholders inspect? |
| Feedback | Evidence from inspection or use | What assumption did this change? |
| Impediment | An obstacle to effective work | What effect does it have on delivery? |
| Improvement experiment | A small process change to test | What observation would support continuing it? |
A flexible six-week Scrum study plan
Six weeks is an example structure. Extend a stage when you cannot yet explain or apply its concepts. The plan does not promise exam readiness.
| Stage | Focus | Practical work | Progress evidence |
|---|---|---|---|
| Week 1 | Use a product goal to guide choices | Write a goal that identifies the user and intended improvement. | Which outcome guides the next choice? Answer with evidence from your exercise. |
| Week 2 | Make backlog items understandable | Rewrite a vague item such as “improve reports” into two smaller outcomes. | What user need and uncertainty does it contain? Answer with evidence from your exercise. |
| Week 3 | Plan around a coherent objective | Create a planning exercise with a known dependency and a limited amount of team capacity. | What can stakeholders inspect? Answer with evidence from your exercise. |
| Week 4 | Build quality into usable results | Write a shared completion checklist for a fictional online form. | What assumption did this change? Answer with evidence from your exercise. |
| Week 5 | Use reviews to obtain evidence | Create a review exercise where users complete a task using a small product increment. | What effect does it have on delivery? Answer with evidence from your exercise. |
| Week 6 | Turn retrospectives into small experiments | Propose a small experiment such as an earlier review conversation. | What observation would support continuing it? Answer with evidence from your exercise. |
Common difficulties: evidence before action
| Observed difficulty | Useful first check | Avoid |
|---|---|---|
| Backlog keeps growing without direction | Compare requests with the product goal | Treating every request as equally urgent. |
| Work waits for review | Inspect the delay and test a small improvement | Blaming a person without examining the workflow. |
| Many tasks finish, little is usable | Review integration and completion conditions | Counting task closure as delivered value. |
| Review produces vague opinions | Observe a real user task and ask specific questions | Relying only on presentation feedback. |
| Plan breaks after one dependency fails | Revisit the objective and useful scope | Keeping every original task despite changed evidence. |
Original Scrum practice scenarios with explanations
Scenario 1: backlog keeps growing without direction. Your starting task is to compare requests with the product goal. Write the expected result, the evidence you would collect and the next decision if your first explanation is unsupported. The common mistake is treating every request as equally urgent. Explain why that shortcut could leave the underlying requirement unresolved, then compare your answer with the relevant topic notes above. These are original learning exercises, not reproduced exam questions.
Scenario 2: work waits for review. Your starting task is to inspect the delay and test a small improvement. Write the expected result, the evidence you would collect and the next decision if your first explanation is unsupported. The common mistake is blaming a person without examining the workflow. Explain why that shortcut could leave the underlying requirement unresolved, then compare your answer with the relevant topic notes above. These are original learning exercises, not reproduced exam questions.
Scenario 3: many tasks finish, little is usable. Your starting task is to review integration and completion conditions. Write the expected result, the evidence you would collect and the next decision if your first explanation is unsupported. The common mistake is counting task closure as delivered value. Explain why that shortcut could leave the underlying requirement unresolved, then compare your answer with the relevant topic notes above. These are original learning exercises, not reproduced exam questions.
Scenario 4: review produces vague opinions. Your starting task is to observe a real user task and ask specific questions. Write the expected result, the evidence you would collect and the next decision if your first explanation is unsupported. The common mistake is relying only on presentation feedback. Explain why that shortcut could leave the underlying requirement unresolved, then compare your answer with the relevant topic notes above. These are original learning exercises, not reproduced exam questions.
Scenario 5: plan breaks after one dependency fails. Your starting task is to revisit the objective and useful scope. Write the expected result, the evidence you would collect and the next decision if your first explanation is unsupported. The common mistake is keeping every original task despite changed evidence. Explain why that shortcut could leave the underlying requirement unresolved, then compare your answer with the relevant topic notes above. These are original learning exercises, not reproduced exam questions.
Track understanding with an error log
For each topic, record an explanation in your own words, one practice result and the next question to investigate. Mark the topic as understood when you can apply it to a different example. Recognising a familiar phrase or remembering an answer is a useful start, but it does not establish that you can reason through a new situation.
When an exercise exposes a mistake, write the assumption, the evidence that contradicted it and the corrected principle. Create a new example using different details and repeat the reasoning. Review weaker topics before spending another session on a comfortable area. If your goal is a credential, compare the tracker with the current objectives so important gaps remain visible.
Request free Scrum reference PDFs
Email freelearning@ciscoforall.com with your exam name and exact code, if applicable, and the topics you need. Use “Scrum Free Reference PDF Request” as the subject. We will send an available older reference file free of charge. Availability varies, and a free file may not be available for every target. The original notes and exercises on this page are free to read without requesting a PDF.
Use older files for background learning and compare them with the current scope of your intended qualification or exam. Product screens, commands, terminology and objectives can change. Verify version-specific information before applying it. We share only reference resources we are permitted to distribute.
Explore Scrum Premium PDFs
Browse Scrum Premium PDFs for additional preparation resources, then open the product that matches your intended target to explore its details. Compare the exam name and version carefully. Use this page to organise your foundations and identify weaker topics before choosing additional material.
Connect any Premium resource with a clear study task: review a weak topic, explain the reasoning behind a solution or repeat an unfamiliar scenario. Continue using practical activities and your error log so preparation develops understanding rather than only recognition of remembered answers.
Frequently asked questions
Is this study guide free?
Yes. The learning notes, tables, plan and original exercises on this page are free to read. Premium PDFs are available separately through our product pages.
Which Scrum path should I start with?
Start with the learning-path comparison and choose the row closest to your goal. If the core topics are unfamiliar, build the foundations first. A more advanced label does not make a resource the best starting point for every learner.
Are these the official exam objectives?
No. These are original learning notes and activities. Confirm the current provider objectives for your exact target and use them to identify any additional topics you need to study.
Can I request a free PDF for my exam?
Yes, you can ask. Include the exact name and code if available, plus the topics you need. Free reference files depend on availability and may be older resources.
Are older reference PDFs sufficient?
Treat them as background material. Compare their topics and version with your intended target and verify details that have changed. Continue practising the relevant concepts.
How should I use the six-week plan?
Use it as a starting structure and adjust it to your experience and available time. Repeat any stage where you cannot explain the topic or apply it to a new example.
How do Premium PDFs fit into my study?
Use the free notes to organise your learning and identify gaps. Explore a matching Premium resource for additional review material, then connect it with practical exercises and your topic tracker.
Does this page guarantee an exam result?
No. Results depend on your knowledge, practical skills and preparation.
Choose your next Scrum learning step
Select one learning path and complete one small exercise today. Save the evidence and the next question in your notes. For older reference material, email freelearning@ciscoforall.com with your target details. For additional preparation resources, browse Scrum Premium PDFs and explore the product that matches your goal.