Scrum Basics
The timebox for a Daily Scrum is?
15 minutes
The timebox for the Sprint Review is:
4 hours for a monthly Sprint. For shorter Sprints it is usually shorter.
The timebox for the Sprint Planning event is?
8 hours for a monthly Sprint. For shorter Sprints it is usually shorter.
Which statement best describes Scrum?
A framework for creating complex products in complex environments. Feedback: Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
What are two effective ways for the Scrum Team to make non-functional requirements visible?
Add them to the Definition of Done so the work is taken care of every Sprint. Add them to the Product Backlog to ensure transparency.
When many Scrum Teams are working on a single product, what best describes the Definition of Done?
All Scrum Teams must have a Definition of Done that makes their combined Increment valuable and useful. Feedback: The Increment must be valuable and useful. This means that when many Scrum Teams are working on a single product, they are expected to adhere to a single Definition of Done for the Increment.
An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done?
All of the above: Without a new vocabulary as a reminder of the change, very little change may actually happen. The organization may not understand what has changed with Scrum and the benefits of Scrum may be lost. Management may feel less anxious.
The length of a Sprint should be:
Answer: All of these answers are correct. - Short enough to keep the business risk acceptable to the Product Owner. - Short enough to be able to synchronize the development work with other business events. - No more than one calendar month.
What are two ways a Scrum Master serves to enable effective Scrum Teams?
By removing impediments that hinder the Scrum Team. By facilitating Developer decision-making. Feedback: The Scrum Master serves the Scrum Team in several ways. Facilitation and removing impediments are examples of ways a Scrum Master helps a team become more effective.
Which two things should the Scrum Team do during the first Sprint?
Deliver an Increment of useful and valuable product. Develop and deliver at least one piece of functionality. Feedback: The heart of Scrum is a Sprint, which is one month or less during which a done, usable, valuable product Increment is created. This applies to every Sprint.
How much work must the Developers complete for each Product Backlog item they select for a Sprint?
Enough so that each Product Backlog item they select meets the Definition of Done. Feedback: The purpose of each Sprint is to deliver useful and valuable Increments that adhere to the Scrum Team's current Definition of Done.
True or False: It is mandatory that the product Increment be released to production at the end of each Sprint.
False
True or False: Scrum has a role called "project manager."
False
True or False: When multiple Scrum Teams work together on the same product, each team should maintain a separate Product Backlog.
False Feedback: Products have one Product Backlog, regardless of how many Scrum Teams are used. Any other setup makes it difficult for the Developers to determine what they should work on.
What is the main reason for the Scrum Master to be at the Daily Scrum?
He or she does not have to be there; he or she only has to ensure the Developers have a Daily Scrum. Feedback The Scrum Master only ensures that all Scrum events take place and are positive, productive, and kept within the timebox.
Who creates the Definition of Done?
If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.
When does the next Sprint begin?
Immediately after the conclusion of the previous Sprint.
The CEO asks the Developers to add a "very important" item to a Sprint that is in progress. What should the Developers do?
Inform the other members of the Scrum Team so the team can decide what to do.
The three pillars of empiricism are:
Inspection, Transparency, Adaptation. Feedback: Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known.Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.
Which statement best describes the Sprint Review?
It is when the Scrum Team and stakeholders inspect the outcome of the Sprint and figure out what to do next. Feedback: Every event in Scrum, besides the Sprint, which is a container for the other events, is an opportunity to Inspect and Adapt.
When does a Developer become the sole owner of a Sprint Backlog item?
Never. All Sprint Backlog items are "owned" by the Developers on the Scrum Team even though each item may be implemented by an individual Developer. Feedback: The Sprint Backlog and all of its items are collectively owned by the Developers. No individual Developer can claim ownership over an item as this would block communication and collaboration.
When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint?
Never. The entire Scrum Team is accountable for creating value every Sprint. Feedback All members of the Scrum Team share in the accountability for creating value every Sprint.
Who has the final say on the order of the Product Backlog?
Product Owner.
A Scrum Team consists of the following:
Scrum Master, Devs, PO
Select three incorrect, untrue, or misleading statements about Scrum?
Scrum is like traditional processes but with self-organization to replace Project Managers. Scrum is a methodology where you can pick and choose which parts of Scrum you think will work for your environment. Scrum is a framework that eliminates complexity. Feedback 1. Scrum is meant to be implemented as prescribed in the Scrum Guide. For example, the five events in the Scrum Guide are mandatory, each event has a specific purpose. 2. Scrum does not eliminate the complexity that is inherent in delivering a product in today's world, instead it offers a framework for dealing with complexity. By regularly delivering Increments of value teams gain the ability to inspect and rapidly adapt based on the feedback received. 3. Project Managers are not simply replaced by self-managing teams. Scrum is a framework for optimizing decision making based on the knowledge and experience of the entire team.
Which Scrum events are timeboxed?
Sprint Review. Sprint Planning. Sprint Retrospective. Feedback: The Scrum Guide states that the Sprint Planning, Sprint Retrospectives, and Sprint Reviews are timeboxed events. Sprints are fixed length events of one month or less to create consistency, and the Daily Scrum is a 15-minute event.
What is the role of Management in Scrum?
Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to cause organizational change that fosters empiricism, self-organization, bottom-up intelligence, and intelligent release of software.
Which of the following services is appropriate for a Scrum Master in regard to the Daily Scrum?
Teach the Developers to keep the Daily Scrum within the 15 minute timebox. Feedback: The Scrum Master ensures that the Developers have the event, but the Developers are responsible for conducting the Daily Scrum. The Scrum Master teaches the Developers to keep the Daily Scrum within the 15-minute timebox. The Scrum Master enforces the rule that only members participate in the Daily Scrum.
Who is required to attend the Daily Scrum?
The Developers. Feedback Only the people doing the work described on the Sprint Backlog need to inspect and adapt at the Daily Scrum. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers, they will need to be at the Daily Scrum.
Who is responsible for managing the progress of work during a Sprint?
The Developers. Feedback: The Developers use 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.
Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly?
The Product Owner Feedback: The Product Owner is the sole person responsible for ordering the Product Backlog. Their responsibilities include making the Product Backlog visible, transparent, and clear to all.
During a Sprint, a Developer determines that the Scrum Team will not be able to complete the items in their forecast. Who should be present to review and adjust the Product Backlog items selected?
The Product Owner and the Developers. Feedback: During the Sprint, scope may be clarified and re-negotiated between the Product Owner and the Developers as more is learned. It is important to be transparent when challenges arise since ultimately the entire Scrum Team is accountable for creating a valuable, useful Increment.
Who is on the Scrum Team?
The Scrum Master, The Product Owner, The Development Team. Feedback The Scrum Team consists of the Scrum Master, the Product Owner and Developers. The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
Why is the Daily Scrum held at the same time and same place?
The consistency reduces complexity. Feedback: The Daily Scrum is held at the same time and place each day to reduce complexity.
What does it mean to say that an event has a timebox?
The event can take no more than a maximum amount of time.
True or False: The purpose of a Sprint is to produce a valuable and useful Increment of working product.
True. False Feedback: The heart of Scrum is a Sprint, a timebox of one month or less during which a done, useful, and valuable working product Increment is created.
What is the recommended size for a Scrum Team?
Typically 10 or fewer people. Feedback: A Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people. Generally smaller teams communicate better and are more productive
The Product Backlog is ordered by:
Whatever is deemed most appropriate by the Product Owner.
When might a Sprint be abnormally cancelled?
When the Sprint Goal becomes obsolete. Feedback: A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint.
Upon what type of process control is Scrum based?
empirical. Feedback: Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed.
When should the Developers on a Scrum Team should be replaced?
As needed, while taking into account a short-term reduction in productivity. Feedback: Scrum Teams typically go through some steps before achieving a state of increased performance. Changing membership typically reduces cohesion, affecting performance and productivity in the short term.
Which of the following are examples of a Scrum Team practicing Scrum poorly or not exhibiting traits of a self-managing Scrum Team?
Stakeholders attend the Daily Scrum to check on the Scrum Team's progress. The Developers are working within the boundaries of their organizations functional description and nicely handing off work from analyst to developer to tester to integration. The Developers invite external stakeholders to the Sprint Planning to ask them how to turn a Product Backlog item into an Increment via a complete and detailed Sprint Backlog. Feedback · The Daily Scrum is for the Developers. It should not be used by external stakeholders to check progress. · During Sprint Planning the Scrum Team should be crafting the Sprint Goal based on the set of Product Backlog items selected for the Sprint. The Developers identify the necessary work to meet the Sprint Goal. · Scrum Team members do not have titles, and no sub-teams; such as testing, architecture, or operations are recognized. Accountability belongs with the Scrum Team as a whole, regardless of whether team members have specialized skills.