Scrum Guide Flashcards
Understand basics of Scrum
What is the definition of Scrum?
A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
Name three attributes of Scrum?
- Lightweight
- Simple to understand
- Difficult to master
What does Scrum Framework consist of?
- Scrum Team
- Roles
- Events
- Artifacts
- Relationships
What was scrum initially designed for?
Managing and developing products
Today, Scrum’s iterative and incremental methods are used for complex industries like:
- Product development
- Services
- Management
What does ‘develop’ or ‘development’ mean in the Scrum Guide?
Complex Work
What Process Control Theory is Scrum based on?
Empiricism
What is Empiricism?
Asserts that knowledge comes form experience and making decisions based on what is known.
What three pillars is empirical process control based on?
Transparency, inspection, and adaptation.
What is transparency?
Aspects of a process must be visible to those responsible for the outcome. Aspects must be defined by a common standard to share understanding of what is being seen.
What is inspection?
Inspection allows users to detect undesirable variances, and should be performed by skilled inspectors.
What is adaptation?
After inspection - adjustments must be made to minimize future deviation.
What are the four formal events identified for inspection and adaptation?
Sprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective
What are the five Scrum Values? (Hint: NOT Pillars)
Commitment Courage Focus Openness Respect
What three roles are in a Scrum Team?
Product Owner
Development Team
Scrum Master
How are Scrum Teams organized?
They are self-organizing and cross-functional (They are not directed by others outside the team.)
How does the Scrum Team model facilitate complex work?
This team model optimizes flexibility, creativity, and productivity. Teams don’t rely on others who are outside of the Scrum Team for competency.
What is the role of the Product Owner?
Maximize VALUE of the product built by the Dev Team. This member owns and manages the Product Backlog.
What is included in Product Backlog management?
Clearly expressing backlog items
Order items to achieve goals and missions
Optimize value of Dev Team work
Ensure items are clear to all and show what is in the pipeline
Ensure Dev Team understands the items
Who can manage the Product Backlog?
The Development Team or the Product Owner. The Prod Owner remains accountable regardless.
If someone wants to see a change in the Product Backlog, who is addressed?
The Product Owner
What is the role of the Development Team?
These members do the work required to deliver a potentially releasable increment of “Done” product at the end of each sprint.
Who is included in the Development Team?
Between three and nine professionals doing work on the product - this can only include the Product Owner or Scrum Master if they are also executing work of the Sprint Backlog.
What are some characteristics of the Dev Team?
- Self Organizing
- Cross Functional
- No titles
- No sub-teams
- Accountability belongs to the whole team
What is the role of the Scrum Master?
Promotes and supports Scrum as defined in the Scrum Guide by helping everyone understand theory, practices, rules, and values.
Who does the Scrum Master serve?
The Scrum Master helps those who are outside the Scrum Team understand what interactions are helpful and which are harmful (Organization), while also serving the Product Owner and the Development Team.
How does the SM serve the PO?
- Ensure goals / scope / product domain are understood by the team
- Provide techniques for backlog management
- Help the team understand need for clear and concise backlog items
- Facilitate knowledge for backlog management to maximize value
- Facilitate scrum events as needed
How does the SM serve the Dev Team?
- Coach the dev team to self organize and cross function
- Help create high-value products
- Remove impediments for dev team
- Facilitate scrum events as needed
- Coach team in organizational environments where Scrum is not fully adopted and understood
