ATLASSIAN AGILE PROJECT MANAGEMENT
PROFESSIONAL CERT | REAL EXAM QUESTIONS
WITH EXPERT VERIFIED ANSWERS FOR
GUARANTEED PASS | LATEST UPDATE 2025
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? - ✔✔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? -
✔✔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? - ✔✔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? - ✔✔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 - ✔✔TRUE
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? - ✔✔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? - ✔✔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... - ✔✔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." - ✔✔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 understand how they should deliver the product.
Sometimes the customer won't think of the most efficient way to deliver a product's
functions and features. So value statement gives the development team an opportunity
to collaborate and come up with better ideas on implementation.
You're a software developer for a large organization. You wait for very clear
specifications from business analysts in another department. Then when you're done
PROFESSIONAL CERT | REAL EXAM QUESTIONS
WITH EXPERT VERIFIED ANSWERS FOR
GUARANTEED PASS | LATEST UPDATE 2025
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? - ✔✔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? -
✔✔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? - ✔✔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? - ✔✔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 - ✔✔TRUE
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? - ✔✔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? - ✔✔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... - ✔✔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." - ✔✔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 understand how they should deliver the product.
Sometimes the customer won't think of the most efficient way to deliver a product's
functions and features. So value statement gives the development team an opportunity
to collaborate and come up with better ideas on implementation.
You're a software developer for a large organization. You wait for very clear
specifications from business analysts in another department. Then when you're done
