ACING PSM I EXAMS: A COMPLETE QUESTIONS AND
ANSWERS BLUEPRINT FOR A+ ACHIEVEMENT.
When a sprint is cancelled, all incomplete product backlog items are
re-estimated and put back on the Product Backlog.
Sprint planning Topic One
What can be delivered in the Increment resulting from the upcoming Sprint?
Sprint Planning Topic Two
How will the work needed to deliver the Increment be achieved?
Sprint planning is created by
the collaborative work of the entire Scrum Team.
Sprint Planning
where the work to be done during the sprint is planned
In topic one of sprint planning, the development team works to
forecast the functionality that will be developed during the
Sprint.
In topic one of sprint planning, the product owner discusses
the objective that the Sprint should achieve and the Product Backlog items that, if completed in the
Sprint, would achieve the Sprint Goal
In topic one of sprint planning, the entire scrum team
collaborates on understanding the work of the Sprint
The number of items selected from the product backlog is determined by
solely the development team
Sprint Planning Inputs
Product Backlog, the latest product Increment, projected capacity of the Development Team during the
Sprint, and past performance of the Development Team.
The sprint goal
an objective that will be met within the Sprint through the implementation of the Product Backlog, and
it provides guidance to the Development Team on why it is building the Increment
During sprint planning the scrum team crafts
a sprint goal
, In topic two of sprint planning, the development team
decides how it will build this functionality into a "Done" product Increment
during the Sprint.
The Sprint Backlog
The Product Backlog items selected for this Sprint plus the plan for delivering
them
In topic two of sprint planning, the product owner
can help to clarify the selected Product Backlog items and make trade-offs
In Topic Two of sprint planning the development team usually starts by
by designing the system and the work needed to convert the Product Backlog into a working product
Increment.
In Topic Two of sprint planning, the development team may invite
other people to attend to provide technical or domain advice
By the end of sprint planning, the development to should be able to
explain to the
Product Owner and Scrum Master how it intends to work as a self-organizing team to
accomplish the Sprint Goal and create the anticipated Increment
The sprint goal gives guidance to the development team on
why it's building the increment
The sprint goal can be
any other coherence that causes the Development Team to work
together rather than on separate initiatives.
Daily scrum is held at the same time and place each day because
it reduces complexity
The development team uses the daily scrum to
inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the
work in the Sprint Backlog.
The daily scrum optimizes
the probability that the Development Team will meet the Sprint Goal.
The structure of the daily scrum is set by
the development team
ANSWERS BLUEPRINT FOR A+ ACHIEVEMENT.
When a sprint is cancelled, all incomplete product backlog items are
re-estimated and put back on the Product Backlog.
Sprint planning Topic One
What can be delivered in the Increment resulting from the upcoming Sprint?
Sprint Planning Topic Two
How will the work needed to deliver the Increment be achieved?
Sprint planning is created by
the collaborative work of the entire Scrum Team.
Sprint Planning
where the work to be done during the sprint is planned
In topic one of sprint planning, the development team works to
forecast the functionality that will be developed during the
Sprint.
In topic one of sprint planning, the product owner discusses
the objective that the Sprint should achieve and the Product Backlog items that, if completed in the
Sprint, would achieve the Sprint Goal
In topic one of sprint planning, the entire scrum team
collaborates on understanding the work of the Sprint
The number of items selected from the product backlog is determined by
solely the development team
Sprint Planning Inputs
Product Backlog, the latest product Increment, projected capacity of the Development Team during the
Sprint, and past performance of the Development Team.
The sprint goal
an objective that will be met within the Sprint through the implementation of the Product Backlog, and
it provides guidance to the Development Team on why it is building the Increment
During sprint planning the scrum team crafts
a sprint goal
, In topic two of sprint planning, the development team
decides how it will build this functionality into a "Done" product Increment
during the Sprint.
The Sprint Backlog
The Product Backlog items selected for this Sprint plus the plan for delivering
them
In topic two of sprint planning, the product owner
can help to clarify the selected Product Backlog items and make trade-offs
In Topic Two of sprint planning the development team usually starts by
by designing the system and the work needed to convert the Product Backlog into a working product
Increment.
In Topic Two of sprint planning, the development team may invite
other people to attend to provide technical or domain advice
By the end of sprint planning, the development to should be able to
explain to the
Product Owner and Scrum Master how it intends to work as a self-organizing team to
accomplish the Sprint Goal and create the anticipated Increment
The sprint goal gives guidance to the development team on
why it's building the increment
The sprint goal can be
any other coherence that causes the Development Team to work
together rather than on separate initiatives.
Daily scrum is held at the same time and place each day because
it reduces complexity
The development team uses the daily scrum to
inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the
work in the Sprint Backlog.
The daily scrum optimizes
the probability that the Development Team will meet the Sprint Goal.
The structure of the daily scrum is set by
the development team
