©SIRJOEL 2024/2025 ALL RIGHTS RESERVED.
Atlassian Agile Project Management
Professional Cert Exam Questions And
Answers 100% Guaranteed Pass.
You're a senior manager and you're in charge of updating your bank's software. The director for
this project has been with the company for decades. This director started out as a developer in a
programming language called Fortran. Now the team is using a newer language called Python.
When you meet with the director they say, "we could do that in Fortran, but I'm not sure it could
be done in Python." After a few failed meetings you want to meet directly with the development
team so that they can answer your questions. What's the key challenge you're trying to
overcome? - Answer✔No director could specialize in all the technology that goes into a modern
software product
Explanation: Modern software projects require many developers with a variety of different skills.
It's very unlikely that anyone manager will be able to master all of the skills of the developers on
the team. So here the manager might want to encourage the team to self-organize and come up
with solutions.
What's the best way to describe the cone of uncertainty? - Answer✔You must make decisions
early when you know the least about how things will turn out
Explanation: It costs the least to plan and make changes at the very beginning of the cone of
uncertainty, but unfortunately that's when you know the least about what it will take to deliver
the product. As your team goes further into the cone, it becomes more expensive to make
changes, but at the same time the team becomes clearer on how it will deliver the product.
You're just starting out as a product owner for an agile team. The first week a project manager
gives you a bulleted list of project requirements. She says, "why don't you copy this into a
spreadsheet, and then we'll use it for the product backlog?" This is a good example of: -
Answer✔Approaching agile as a set of practices instead of a new way of thinking about your
product
1|Page
, ©SIRJOEL 2024/2025 ALL RIGHTS RESERVED.
Explanation: Copying over project requirements into user stories puts too much emphasis on the
practice of writing stories but not enough emphasis on the agile mindset.
Principles 1, 8, 9 and 10 of the Agile Manifesto describe prioritizing high-value work. What's a
common way that agile teams prioritize their work? - Answer✔They create a ranked list of what
the customer finds valuable
Explanation: Agile teams work on the highest value items first. This is different from other
software development practices that encourage teams to work on what's most technically
challenging or take the longest to develop. Agile teams typically have a representative of product
owner who ranks all of the products functions and features by customer value.
In a meeting, your managing director passes out a copy of the Agile Manifesto. They said that
agile teams are better at developing software. So you should read the printout and then work
together as an agile team. What's one of the challenges with this approach? - Answer✔The Agile
Manifesto describes a mindset and not a practical way of working
Explanation: The Agile Manifesto is written in a way that encourages teams to embrace a certain
mindset. It doesn't outline a practical way of working like you see in project management or
manufacturing.
What's the best definition of an agile team? - Answer✔It's a team that embraces a mindset that's
consistent with the Agile Manifesto
Explanation: Agile teams embrace a mindset that's consistent with the values and principles
outlined in the Agile Manifesto.
Agile teams often work in two-week "Sprints." What's one of the main justifications for having
such a short iteration of work? - Answer✔A short Sprint helps the team develop smaller batches
of work
Explanation: It's easier for the team to avoid multitasking if they focus on a smaller batch of
work. Agile teams typically work in two-week Sprints. During that time, the team should
completely focus on delivering the work they commited to during their planning.
On an agile team it's usually better to have a team of generalists than one of specialists.
FALSE
TRUE - Answer✔TRUE
2|Page
, ©SIRJOEL 2024/2025 ALL RIGHTS RESERVED.
Explanation: When you're working in agile team, it's better to have a group of generalists that
can always contribute some work to the product. If the team has a lot of specialists, then it might
encourage team members to work off large batches they need to hand off to the next specialist.
So for an agile team, it's better to have a group that knows a little bit about everything than one
where each person specializes.
You're a senior developer and your manager has asked you to work on two different software
development teams. Your manager says that no one knows the system as well as you do and so
you can work 20 hours on each team instead of 40 hours on one team. What will be the most
difficult challenge with this way of working? - Answer✔Multitasking between the two teams
will dramatically lower your productivity
Explanation: If someone works on more than one task, their productivity isn't 50% for each task.
In fact, their productivity might dip to around 30% for each task. That's because context
switching between the two tasks dips into their productivity. So a senior developer who switches
between teams has lower productivity.
Why do agile teams typically try to work in two-week Sprints? - Answer✔It helps the team focus
on short term planning
Explanation: Agile teams don't give up planning, they focus on short-term planning. That's one
of the advantages of working in two-week Sprints. Here the team can be sure that they are only
planning what needs to be delivered at the end of the next Sprint.
Your agile team is planning out their Sprint. There is a list of dozens of user stories that need to
be completed, but the team pulls out four stories that they plan to deliver in the next two-weeks.
This is a good example of... - Answer✔A work queue
Explanation: Agile teams should deliver smaller batches of work in a shorter work queue. Scrum
teams typically pull just a few items out of the product backlog. Then they'll put that in the
"Sprint backlog" for their next Sprint. So these items will be small batches of work put in a
Sprint backlog to be delivered in two weeks.
What's the main challenge with this user story, "As a mobile user, I want to be able to set the
application so that it only downloads data when I'm on Wi-Fi." - Answer✔This story doesn't
have any value statement
Explanation: Many teams who come from a project management background have difficulty
including value statements in their user stories. That's because project requirements rarely
included statements of customer value. But the value statement helps the development team
3|Page
Atlassian Agile Project Management
Professional Cert Exam Questions And
Answers 100% Guaranteed Pass.
You're a senior manager and you're in charge of updating your bank's software. The director for
this project has been with the company for decades. This director started out as a developer in a
programming language called Fortran. Now the team is using a newer language called Python.
When you meet with the director they say, "we could do that in Fortran, but I'm not sure it could
be done in Python." After a few failed meetings you want to meet directly with the development
team so that they can answer your questions. What's the key challenge you're trying to
overcome? - Answer✔No director could specialize in all the technology that goes into a modern
software product
Explanation: Modern software projects require many developers with a variety of different skills.
It's very unlikely that anyone manager will be able to master all of the skills of the developers on
the team. So here the manager might want to encourage the team to self-organize and come up
with solutions.
What's the best way to describe the cone of uncertainty? - Answer✔You must make decisions
early when you know the least about how things will turn out
Explanation: It costs the least to plan and make changes at the very beginning of the cone of
uncertainty, but unfortunately that's when you know the least about what it will take to deliver
the product. As your team goes further into the cone, it becomes more expensive to make
changes, but at the same time the team becomes clearer on how it will deliver the product.
You're just starting out as a product owner for an agile team. The first week a project manager
gives you a bulleted list of project requirements. She says, "why don't you copy this into a
spreadsheet, and then we'll use it for the product backlog?" This is a good example of: -
Answer✔Approaching agile as a set of practices instead of a new way of thinking about your
product
1|Page
, ©SIRJOEL 2024/2025 ALL RIGHTS RESERVED.
Explanation: Copying over project requirements into user stories puts too much emphasis on the
practice of writing stories but not enough emphasis on the agile mindset.
Principles 1, 8, 9 and 10 of the Agile Manifesto describe prioritizing high-value work. What's a
common way that agile teams prioritize their work? - Answer✔They create a ranked list of what
the customer finds valuable
Explanation: Agile teams work on the highest value items first. This is different from other
software development practices that encourage teams to work on what's most technically
challenging or take the longest to develop. Agile teams typically have a representative of product
owner who ranks all of the products functions and features by customer value.
In a meeting, your managing director passes out a copy of the Agile Manifesto. They said that
agile teams are better at developing software. So you should read the printout and then work
together as an agile team. What's one of the challenges with this approach? - Answer✔The Agile
Manifesto describes a mindset and not a practical way of working
Explanation: The Agile Manifesto is written in a way that encourages teams to embrace a certain
mindset. It doesn't outline a practical way of working like you see in project management or
manufacturing.
What's the best definition of an agile team? - Answer✔It's a team that embraces a mindset that's
consistent with the Agile Manifesto
Explanation: Agile teams embrace a mindset that's consistent with the values and principles
outlined in the Agile Manifesto.
Agile teams often work in two-week "Sprints." What's one of the main justifications for having
such a short iteration of work? - Answer✔A short Sprint helps the team develop smaller batches
of work
Explanation: It's easier for the team to avoid multitasking if they focus on a smaller batch of
work. Agile teams typically work in two-week Sprints. During that time, the team should
completely focus on delivering the work they commited to during their planning.
On an agile team it's usually better to have a team of generalists than one of specialists.
FALSE
TRUE - Answer✔TRUE
2|Page
, ©SIRJOEL 2024/2025 ALL RIGHTS RESERVED.
Explanation: When you're working in agile team, it's better to have a group of generalists that
can always contribute some work to the product. If the team has a lot of specialists, then it might
encourage team members to work off large batches they need to hand off to the next specialist.
So for an agile team, it's better to have a group that knows a little bit about everything than one
where each person specializes.
You're a senior developer and your manager has asked you to work on two different software
development teams. Your manager says that no one knows the system as well as you do and so
you can work 20 hours on each team instead of 40 hours on one team. What will be the most
difficult challenge with this way of working? - Answer✔Multitasking between the two teams
will dramatically lower your productivity
Explanation: If someone works on more than one task, their productivity isn't 50% for each task.
In fact, their productivity might dip to around 30% for each task. That's because context
switching between the two tasks dips into their productivity. So a senior developer who switches
between teams has lower productivity.
Why do agile teams typically try to work in two-week Sprints? - Answer✔It helps the team focus
on short term planning
Explanation: Agile teams don't give up planning, they focus on short-term planning. That's one
of the advantages of working in two-week Sprints. Here the team can be sure that they are only
planning what needs to be delivered at the end of the next Sprint.
Your agile team is planning out their Sprint. There is a list of dozens of user stories that need to
be completed, but the team pulls out four stories that they plan to deliver in the next two-weeks.
This is a good example of... - Answer✔A work queue
Explanation: Agile teams should deliver smaller batches of work in a shorter work queue. Scrum
teams typically pull just a few items out of the product backlog. Then they'll put that in the
"Sprint backlog" for their next Sprint. So these items will be small batches of work put in a
Sprint backlog to be delivered in two weeks.
What's the main challenge with this user story, "As a mobile user, I want to be able to set the
application so that it only downloads data when I'm on Wi-Fi." - Answer✔This story doesn't
have any value statement
Explanation: Many teams who come from a project management background have difficulty
including value statements in their user stories. That's because project requirements rarely
included statements of customer value. But the value statement helps the development team
3|Page
