PRACTICE
◉ Which role is responsible for managing the Development Team?
Answer: Development Team
Explanation
The Development Team is self-organized and manages itself instead
of receiving orders
◉ The Sprint Backlog makes visible all of the work the ______
identifies as necessary to meet the Sprint Goal. Answer:
Development Team
Explanation
This is up to the developers to identify how to accomplish the goal.
After all, they are the technical people in the project.The question is
about the Sprint Backlog tasks, rather than items.
◉ Who monitors the remaining work of the Product Backlog?
Answer: The Product Owner
Explanation
,The Product Owner is responsible for measuring the progress of the
project and tracking the remaining work in the Product Backlog.The
Development Team is responsible for measuring the progress of the
Sprint and tracking the remaining work in the Sprint Backlog.
◉ Who can change the Sprint Backlog in the middle of the Sprint?
Answer: Only the Development team
Explanation
the Product Backlog items selected for the Sprint do not change but
the Sprint Backlog also contains tasks and tasks evolve through the
Sprint. The Development Team owns the Sprint Backlog and only
they can change the Sprint Backlog. This is sometimes done based
on the input from the Product Owner.
◉ What type of process control is Scrum? Answer: Empirical
Scrum is empirical; based on the real-world experiences.
◉ Who assigns tasks to the developers? Answer: Development team
Explanation
The developers take responsibility for doing the tasks themselves
and the Development Team ensures that all tasks are done properly.
, Remember that they are self-organized. When items are "Done", the
Product Owner checked them but this is focused on the item rather
than individuals; all developers are accountable for the team's
outputs.
◉ How should developers deal with non-functional features?
Answer: Incorporate them into every increment
Explanation
Non-functional features are usually part of the Definition of Done
and should be considered for every Product Backlog item and every
Increment. Sometime, some non-functional features that address a
very particular part of the software can be added as separate items
in the Product Backlog.All Sprints are the same. There's no Sprint
zero, hardening Sprint, release Sprint, integration Sprint, etc.
◉ What is the prerequisite for starting the Sprint Planning meeting?
Answer: None
We prefer to have "ready" items at the top of the Product Backlog
before Sprint Planning, which is done through Product Backlog
refinement. However, nothing stops our flow of Sprints. For example,
we do not delay the Sprint because the items are not ready. In such
cases, the "unready" items would be selected for the Sprint and
refined during the Sprint."Ready" items are those that are clear and
small enough to fit into one Sprint.