Getting Through the Atlassian Jira Agile Module 3 Assessment Without Losing Your Mind
Module 3 of the Agile With Atlassian Jira certification covers the practical side of setting up and running sprints. It's where you actually use the software instead of just reading about theory. I took this assessment twice because the first time I guessed on enough questions to miss the passing score by three points. Not proud of that, but it taught me how to study it properly. I'm not going to hand you a list of answers. Anyone selling that is probably running a scam. What I will tell you is exactly what the module tests and how to actually understand the material so you don't need the cheat sheet. The exam covers sprint planning, backlog refinement, story point estimation, burn-down charts, and the difference between Scrum and Kanban workflows inside Jira. These are concrete topics with right and wrong answers based on how Atlassian designed their tool to work. One thing most people miss: the assessment loves to trick you on the difference between a Scrum board and a Kanban board in Jira. Specifically, they ask which fields are available in each view and what happens when you switch between them. In practice, I found that spending ten minutes actually clicking through a Jira instance and toggling between the two board types memorized this better than any amount of reading. The exam won't tell you that switching a Scrum board to a Kanban board in the same project does not migrate your sprint data. That single fact cost me a question on my first attempt.
Another counter-intuitive detail is how story points work in the context of velocity calculations. The module expects you to know that velocity is calculated from completed story points per sprint, not from estimated points. I remember working on a real project where the team kept logging estimated points as completed because they confused the two fields in their report. Our velocity was completely fake for three consecutive sprints before anyone noticed. The assessment will ask about this distinction directly, so make sure you understand it cold. The burn-down chart questions are straightforward if you've actually looked at one. The burn-up chart is where people get tripped up. Jira generates a burn-up chart that includes scope changes, which means the total lines move when new stories are added mid-sprint. On the exam, they might show you a burn-up graph with a rising total line and ask what it indicates. The answer is scope creep or scope expansion during the sprint, not a problem with the estimation. I've seen teams panic over burn-up charts when the total line went up, thinking their progress was wrong. It's not. It's working as designed. For backlog refinement, the assessment tests whether you know the recommended frequency and duration. The official Atlassian guidance is roughly two hours per week for a two-week sprint cycle, though they frame it as a guideline rather than a hard rule. The exam tends to favor the guideline answer unless the question specifically asks about flexibility.
When it comes to sprint burndown, understand that a flat line means no work was logged that day. This doesn't necessarily mean the team did nothing. It could mean they spent the day in meetings or troubleshooting production issues that don't have Jira tickets attached. I once had a developer tell me his team had a perfect burndown for a full sprint because they were doing unplanned hotfix work outside the tracker. The sprint was a disaster despite what the chart showed. The module wants you to know what the chart measures and what it doesn't. The practical tip that actually helped me pass: go into a free Atlassian cloud account and do every single exercise in the learning module interactively. Don't just read through it. Click every button. Break things. Reset the board. The questions map almost directly to the UI actions you perform in those exercises. I cut my study time roughly in half by doing this instead of re-reading the text content three times. If you're struggling with a particular question type, focus your energy on the sprint review and retrospective sections. Those appear frequently and the answers often depend on understanding the Agile manifest principles rather than Jira-specific features. The exam blends both, and the blend is where people lose points.
Get the Full Details
There's no shortcut around actually understanding the material. The assessment is designed to catch people who memorize without comprehending. Study the boards, know the charts, understand the Scrum ceremonies as Jira implements them, and you should pass on the first try without needing to look anywhere else.
