PSPO Mikhail Exam With Questions And
Verified Answers
What are the two essential features a Scrum Team should possess?
-It should choose how best to accomplish their work, rather than being directed by others outside the
team
-It should have all competencies needed to accomplish the work without depending on others not
part of the team
A system is decomposed into elements like workflows, features, capabilities, etc. How it affects Scrum
Teams on a scaled project?
It will be reflected in the implementation.
Two ways how Dev Teams can ensure a good application architecture?
* Architecture is an ongoing discussion
* The DT should have a set of architecture principles and follow them
How to start a big complex project?
Form 1-2 teams of best developers for implementing the core, add more teams later.
During sprint review stakeholders notice that the product development progress is not very clearly
visible and lacked transparency. Moreover, they are not able to understand the next steps. Who is
responsible for this?
Product Owner is responsible
Scrum Team decides they need to create one more artifact UI markup to better understand the
product feature, can they proceed or not since Scrum Teams should capture product features/needs
only in Product Backlog?
Of course, the team can proceed. Right, PB is the single source of requirements for any changes to be
made to the product. If the Scrum Team does not understand what should be done next, it means the
PB needs to be refined. The Product Owner should put his product vision as backlog items, maybe
with help of the Development Team.
Can the PO invite stakeholders to PBL refinement sessions?
I would say the PO should not usually do this. The PO must be the arbiter of product value and how it
is represented to the team. Frequently key stakeholders do not know exactly what they want and
how it can be achieved. This is a job for the PO to understand their needs, decide how they can be
fulfilled with the maximum value.
Does the Product Backlog contain only functional requirements for the Product?
No
A Project Manager working with your Scrum Team has raised concerns about progress and money
spent. What are the two best responses?
1) Scrum doesn't have PMs*
2) Share the PB and forecast for the sprint*
Who are the individuals the PO should consult with when considering the value of a Product?
, The most important individuals for maximizing value for the Product are the Key Stakeholders. The PO
should identify and involve them as necessary throughout the development effort. The Key
Stakeholders are typically customers, purchasers, users, and the people that fund the product's
development. These people may be internal or external to the Organization.
What is Product Owner work that a Product Owner might delegate? Choose one from (a. Ordering PB,
b. Writing user stories, c. Facilitating meetings).
The Product Owner can delegate ordering the product backlog
What three things might a Scrum Product Owner focus on to ensure his product delivers value?
-Key Stakeholder Involvement
-Product Marketplace
-Product Release Decisions
My job as a Product Owner focuses on the following (Choose 2 answers):
-Clearly communicating project or release status and strategies to customers and stakeholders
-Working with customers and stakeholders to identify the most important product requirements
All work to be done by the Development Team must ultimately originate from the Product Backlog?
I think, in the broad sense the answer is "yes". The PB is the source for the Sprint Backlog. The Sprint
Backlog is the source of the Dev Team work. However, only the Dev Team knows how to implement
Sprint Backlog Items. It can involve technical tasks, for example, removing some technical debt or
even installing a development environment for a new developer.
A Product Owner can measure success by an increase in the team's velocity?
No. It is just one of the first steps to success. Success in Scrum is getting maximum value with the
existing resources. Value, as defined in a Scrum context, is the financial (or social) benefit an
organization receives or might receive by creating and releasing the product under development. In
order for value to actually be captured, a release of the product must occur. The sooner you release,
the sooner you can start capturing the value created by the product.Increase in team's velocity shows
that the Dev Team became more mature and can do more in the same time frame
The Sprint Review is mainly an inspect and adapt opportunity for which group?
The Scrum Team and Stakeholders
If two Scrum Teams are added to the development of a product that previously only had one Scrum
Team, what will be the immediate impact on productivity of the original Scrum Team?
Its productivity is likely to decrease
What three factors are best considered when establishing the sprint length? Choose 3 answers.
-is good because the bigger part of interaction with the Key Stakeholders happens at the Sprint
Review meeting. If the Sprint length is bigger, this feedback loop becomes longer.
-Shorter Sprints is an effective way to hone in on the requirements or try out the technology before
committing to a solution.
-Shorter Sprints suppose that the Dev Team produces "done" increments more frequently. It allows
the PO to release the increments more frequently too.
How would an organization with 100 developers divide into teams?
Verified Answers
What are the two essential features a Scrum Team should possess?
-It should choose how best to accomplish their work, rather than being directed by others outside the
team
-It should have all competencies needed to accomplish the work without depending on others not
part of the team
A system is decomposed into elements like workflows, features, capabilities, etc. How it affects Scrum
Teams on a scaled project?
It will be reflected in the implementation.
Two ways how Dev Teams can ensure a good application architecture?
* Architecture is an ongoing discussion
* The DT should have a set of architecture principles and follow them
How to start a big complex project?
Form 1-2 teams of best developers for implementing the core, add more teams later.
During sprint review stakeholders notice that the product development progress is not very clearly
visible and lacked transparency. Moreover, they are not able to understand the next steps. Who is
responsible for this?
Product Owner is responsible
Scrum Team decides they need to create one more artifact UI markup to better understand the
product feature, can they proceed or not since Scrum Teams should capture product features/needs
only in Product Backlog?
Of course, the team can proceed. Right, PB is the single source of requirements for any changes to be
made to the product. If the Scrum Team does not understand what should be done next, it means the
PB needs to be refined. The Product Owner should put his product vision as backlog items, maybe
with help of the Development Team.
Can the PO invite stakeholders to PBL refinement sessions?
I would say the PO should not usually do this. The PO must be the arbiter of product value and how it
is represented to the team. Frequently key stakeholders do not know exactly what they want and
how it can be achieved. This is a job for the PO to understand their needs, decide how they can be
fulfilled with the maximum value.
Does the Product Backlog contain only functional requirements for the Product?
No
A Project Manager working with your Scrum Team has raised concerns about progress and money
spent. What are the two best responses?
1) Scrum doesn't have PMs*
2) Share the PB and forecast for the sprint*
Who are the individuals the PO should consult with when considering the value of a Product?
, The most important individuals for maximizing value for the Product are the Key Stakeholders. The PO
should identify and involve them as necessary throughout the development effort. The Key
Stakeholders are typically customers, purchasers, users, and the people that fund the product's
development. These people may be internal or external to the Organization.
What is Product Owner work that a Product Owner might delegate? Choose one from (a. Ordering PB,
b. Writing user stories, c. Facilitating meetings).
The Product Owner can delegate ordering the product backlog
What three things might a Scrum Product Owner focus on to ensure his product delivers value?
-Key Stakeholder Involvement
-Product Marketplace
-Product Release Decisions
My job as a Product Owner focuses on the following (Choose 2 answers):
-Clearly communicating project or release status and strategies to customers and stakeholders
-Working with customers and stakeholders to identify the most important product requirements
All work to be done by the Development Team must ultimately originate from the Product Backlog?
I think, in the broad sense the answer is "yes". The PB is the source for the Sprint Backlog. The Sprint
Backlog is the source of the Dev Team work. However, only the Dev Team knows how to implement
Sprint Backlog Items. It can involve technical tasks, for example, removing some technical debt or
even installing a development environment for a new developer.
A Product Owner can measure success by an increase in the team's velocity?
No. It is just one of the first steps to success. Success in Scrum is getting maximum value with the
existing resources. Value, as defined in a Scrum context, is the financial (or social) benefit an
organization receives or might receive by creating and releasing the product under development. In
order for value to actually be captured, a release of the product must occur. The sooner you release,
the sooner you can start capturing the value created by the product.Increase in team's velocity shows
that the Dev Team became more mature and can do more in the same time frame
The Sprint Review is mainly an inspect and adapt opportunity for which group?
The Scrum Team and Stakeholders
If two Scrum Teams are added to the development of a product that previously only had one Scrum
Team, what will be the immediate impact on productivity of the original Scrum Team?
Its productivity is likely to decrease
What three factors are best considered when establishing the sprint length? Choose 3 answers.
-is good because the bigger part of interaction with the Key Stakeholders happens at the Sprint
Review meeting. If the Sprint length is bigger, this feedback loop becomes longer.
-Shorter Sprints is an effective way to hone in on the requirements or try out the technology before
committing to a solution.
-Shorter Sprints suppose that the Dev Team produces "done" increments more frequently. It allows
the PO to release the increments more frequently too.
How would an organization with 100 developers divide into teams?
