Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.
AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by Exin
Exam Format
Registration
Validity
Skills this practice test covers
- Contrast the Agile way of thinking with a Waterfall project.
- Assign Scrum responsibilities correctly among the Product Owner, the Scrum Master and the Developers.
- Order and refine product backlog items, and test user stories against the INVEST criteria.
- Size backlog items with planning poker, triangulation or affinity estimation.
- Track sprint progress with burn-down charts, Kanban boards and other information radiators.
- Adapt Scrum to large projects, virtual teams and different contract types.
Explore related topics
EX0-008 exam content
5 domains · 26 topics · 240 of 248 questions sorted by domain
Agile way of thinking10%23 questions
This domain explains the thinking behind Scrum. Candidates describe the Agile Manifesto, show how Agile brings both predictability and flexibility, and recognize other Agile methods.
Skills tested
- Explain the four values of the Agile Manifesto, such as responding to change over following a plan.
- Show how fixed-length iterations make delivery predictable while leaving room for change.
- Recognize Agile methods other than Scrum, including Extreme Programming (XP), DSDM, Crystal and Kanban.
Questions by topic
- Agile Manifesto8
- Agile methods other than Scrum6
- Predictability and flexibility4
- Concepts of Agile and Scrum5
Scrum practices55%134 questions
The largest domain covers the working parts of Scrum: three roles, the timeboxed events, the product and sprint backlogs, and the product goal, sprint goal and definition of done.
Skills tested
- Explain what the Product Owner, the Scrum Master and the Developers are each accountable for.
- Describe the purpose of the sprint, the daily scrum, the sprint review and the sprint retrospective.
- Recognize good user stories and explain how the product backlog is refined and ordered.
- Separate the definition of done from the acceptance criteria of a single backlog item.
- Explain why Scrum works without a traditional project manager.
Official topics
- Scrum roles
- Scrum events
- The importance of the backlog
- Working toward goals
Scrum planning and estimation17.5%41 questions
This domain covers sprint planning and estimation. Candidates choose a sprint length, size backlog items with relative estimates, and use the team's velocity to forecast how much work fits in a sprint.
Skills tested
- Explain what happens in sprint planning and what the team brings into it.
- Choose a sprint duration from factors such as product complexity and risk.
- Estimate with planning poker, triangulation and affinity estimation.
- Compare estimates in ideal days, ideal hours and story points, and calculate the team's velocity.
Questions by topic
- Story Points4
- Planning Poker3
- Velocity6
- Estimation techniques5
- Triangulation4
- Sprint duration3
- Scrum planning10
- Sprint Planning inputs2
- Scrum estimation4
Monitoring Scrum projects10%24 questions
Scrum teams keep their progress visible to everyone. This domain covers information radiators, Kanban boards and the charts that show the work done and the work remaining.
Skills tested
- Read a burn-down chart and a burn-up chart, and say whether the work is on track.
- Use a Kanban board to show work in progress and spot bottlenecks.
- Explain the value of an information radiator placed where the whole team can see it.
Questions by topic
- Burn-down Chart4
- Kanban boards6
- Work visualization7
- Information radiators5
- Scrum monitoring2
Advanced Scrum concepts7.5%18 questions
The smallest domain looks at Scrum beyond a single collocated team: scaling to large, complex projects, working as a virtual team, and choosing contracts that suit iterative delivery.
Skills tested
- Recognize how frameworks such as Nexus and LeSS coordinate several Scrum teams.
- Name the problems a virtual team faces, such as the loss of osmotic communication.
- Compare fixed-price contracts with incremental delivery contracts in Scrum.
Questions by topic
- Scaling Scrum6
- Contracts in Scrum6
- Virtual teams5
- Scrum in different situations1
Requirements
- No formal prerequisites: anyone can book the exam.
- Recommended: a basic understanding of software development and of project management concepts.
- Recommended: experience working as part of a team.
About the EX0-008 exam
The EXIN Agile Scrum Foundation exam (EX0-008) checks that a candidate understands how a Scrum team plans, builds and reviews work in short, fixed-length sprints. It is a foundation exam with no formal prerequisites, written for developers, managers and other people who work with Scrum. Its largest domain, Scrum practices, covers the roles, the events, the two backlogs and the goals that keep a sprint on course. The syllabus also stresses that Scrum has no traditional project manager role. Passing earns the EXIN Agile Scrum Foundation certificate, which does not expire.
Scrum practices also holds the most questions in the PlanetCert practice test, with many on user stories, the Developers and the sprint backlog. The explanations matter most where two options sound alike, such as the definition of done and a story's acceptance criteria. Flashcard Mode works well for the long list of named concepts, from osmotic communication to the niko-niko calendar. Brainy AI Assistant can walk through a planning poker round or explain why the sprint goal stays fixed during a sprint.
How to earn the certification
- Earns
- EXIN Agile Scrum FoundationFoundation
The EXIN Agile Scrum Foundation certificate is valid for life and needs no renewal.
How to prepare for EX0-008
- 1
Learn who owns each decision
Scrum practices is the largest domain, and many of its questions ask who does what. List what the Product Owner, the Scrum Master and the Developers each own, from ordering the backlog to removing impediments.
- 2
Trace one sprint from start to end
Follow a single sprint through sprint planning, the daily scrums, the sprint review and the sprint retrospective. For each event, write down its purpose, who takes part and what it produces.
- 3
Estimate a small backlog by hand
Write a few user stories against the INVEST criteria and size them with planning poker in story points, then again in ideal days. Then invent the results of three sprints and calculate the team's velocity.
- 4
Sketch burn-down and burn-up charts
Draw both charts and a simple Kanban board for an imagined release. Knowing how each one looks makes the monitoring questions quick to read.
- 5
Close with flashcards and a timed run
Use Flashcard Mode for the named concepts, from the bus factor to an escaped defect. Then take the EX0-008 practice test in Timed Mode and ask Brainy AI Assistant about each missed question.
Start a timed EX0-008run
Who EX0-008 is for
- Developers and testers who are joining their first Scrum team.
- Project managers who need to see how work runs when Scrum has no project manager role.
- Product Owners and Scrum Masters who are new to their roles.
- IT service management staff and business managers whose teams are moving to Agile work.
Typical job titles: Scrum team member · Software developer · Project manager · Product owner · Scrum master · Business manager
EX0-008 glossary
20 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- Acceptance criteria
- Conditions that one backlog item must meet to be accepted; unlike the definition of done, they differ from item to item.
- Agile Manifesto
- A short statement of the values behind Agile work, such as individuals and interactions over processes and tools.
- Burn-down chart
- A chart that plots the work remaining against time, so the team can see whether it will finish the planned work.
- Daily Scrum
- A short daily event in which the Developers check progress toward the sprint goal and plan their work for the next day.
- Definition of Done (DoD)
- The shared quality standard that work must meet before the team calls it done and adds it to the increment.
- Developers
- The members of the Scrum team who create the increment in each sprint and own the sprint backlog.
- Information radiator
- A large, visible display of project information, such as a Kanban board, placed where the team and its visitors can see it.
- INVEST criteria
- A check for good user stories: each should be independent, negotiable, valuable, estimable, small and testable.
- Nexus framework
- A framework for scaling Scrum in which several Scrum teams build one product from a single product backlog.
- Niko-niko calendar
- A calendar on which each team member marks a daily mood, so that the team can spot problems early.
- Osmotic communication
- Information that a collocated team picks up just by hearing nearby conversations, which a virtual team loses.
- Planning poker
- An estimation game in which team members show their estimates at the same time, discuss the differences and then estimate again.
- Product backlog
- The single, ordered source of requirements for the product, which keeps changing as the team learns more.
- Product Owner
- The Scrum role accountable for maximizing the product's value and for ordering the product backlog.
- Scrum Master
- The Scrum role that coaches the team in Scrum, facilitates its events and helps remove impediments.
- Sprint
- A fixed-length timebox, usually one to four weeks, in which the team turns backlog items into an increment.
- Sprint backlog
- The backlog items chosen for the current sprint, together with the Developers' plan for delivering them.
- Sprint retrospective
- The event that ends a sprint, in which the Scrum team reviews how it worked and chooses improvements.
- Story points
- A relative unit of size that compares a backlog item with a reference story instead of counting hours.
- Velocity
- The amount of work, often counted in story points, that a team completes in a sprint; past velocity helps forecast future sprints.