Scrum Theory Flashcards
How frequently product releases should occur?
Frequently enough to eliminate the risk that the product’s value will get out of line with the marketplace
While Scrum doesn’t require a release to occur every Sprint, it should be noted that the more elapsed time that accumulates since the last release, the higher the risk that the product’s value will get out of line with the marketplace. Product Owners should keep this risk in the forefront of their mind. Looking at it another way, the sooner you release, the sooner you can start capturing the value created by the product.
The Product Owner wants to apply some non-functional requirements to the Product. What is the best way to proceed?
Add the non-functional requirements to the DoD and check every Increment against these criteria
Non-functional requirements describe qualities of the Product being developed. For example, the Product should be secure and extensible. The only way to meet such requirements is to have them as a part of the DoD and check every Increment against these criteria.
What is the essence of Scrum? Select the most appropriate option.
A small team of people that is highly flexible and adaptive
The essence of Scrum is a small team of people. The individual team is highly flexible and adaptive. These strengths continue operating in single, several, many, and networks of teams that develop, release, operate and sustain the work and work products of thousands of people. They collaborate and interoperate through sophisticated development architectures and target release environments.
Select the two focus areas that are not considered in executing Value Driven Development by the Product Owner.
- Remover of impediments to the Development Team’s progress
- Coach of the Development Team in self-organization and cross-functionality
In executing Value Driven Development, the Product Owner must consider the focus areas of:
- Product Value Maximizer
- Product Visionary
- Product Marketplace Expert
- Product Release Decision Maker
- Lead Facilitator of Key Stakeholder Involvement
- Other Product Owner role Considerations
If multiple Stakeholders have varied interests in the product and different viewpoints what is the best strategy for the Product Owner?
Do an intelligent balancing of interests and try to maximize the value of the Product as a whole
Inherent in the role of facilitating key stakeholder involvement is weighing and balancing the (likely) differing viewpoints of multiple stakeholders who might have varied interests in the product. The Product Owner’s responsibility is to maximize the value of the product as a whole, and this will involve an intelligent balancing of interests.
Who is allowed to tell the Development Team to work from a set of requirements?
The Product Owner
The Product Owner’s decisions are visible in the content and ordering of the Product Backlog. No one is allowed to tell the Development Team to work from a different set of requirements, and the Development Team isn’t allowed to act on what anyone else says.
Select the three best options to finish the sentence below.
Technical debt …
- reflects some extra development work
- compromises long-term quality of the Product
- is a real risk which can genuinely be incurred
Technical debt is a concept in programming that reflects the extra development work that arises when code that is easy to implement in the short run is used instead of applying the best overall solution. In other words it can be defined as the longer term consequences of poor design decisions. Technical debt is a real risk which can genuinely be incurred. It compromises long-term quality of the Product.
One of the ways of handling technical debt is recording it on the Product Backlog. So, it becomes visible to the Scrum Team.
Product Backlog Refinement practice focuses on Items for upcoming Sprints, not the current Sprint in progress. True or false?
True
Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. The Items in the current Sprint are no longer on the Product Backlog, because they are now on the Sprint Backlog.
However, it is certainly fine for the Product Owner to add detail and clarification to the current Sprint’s work as well.
All the Scrum Teams working on the same product should have the same Sprint length.
False.
Scrum does not require having aligned Sprints for multiple teams.
Where Scrum can be used? Check all the applicable items.
- Development of almost everything we use in our daily lives as individuals and societies
- Managing the operation of an organization
- Development of software and hardware
- Development of products and enhancements
- Development and sustaining of Cloud and other operational environments
- Research and identifying of viable markets, technologies, and product capabilities
Scrum has been used to develop software, hardware, embedded software, networks of interacting function, autonomous vehicles, schools, government, marketing, managing the operation of organizations and almost everything we use in our daily lives, as individuals and societies.
Scrum has been used extensively, worldwide, to:
Research and identify viable markets, technologies, and product capabilities;
Develop products and enhancements;
Release products and enhancements, as frequently as many times per day;
Develop and sustain Cloud (online, secure, on-demand) and other operational environments for product use; and,
Sustain and renew products.
Which KVA categories should the Product Owner consider to measure and track the creation and delivery of value to the market place (select three)?
- Current Value
- Time-to-Market
- Ability to Innovate
According to the Evidence Based Management an Organization should focus on the following Key Value Areas (KVA) categories:
Current Value
Time-to-Market
Ability to Innovate
Select the three most applicable sentence endings.
Product Backlog Refinement …
- Usually takes no more than 10% of the capacity of the Development Team
- Is the act of adding detail, estimates, and order to Product Backlog items
- Is an ongoing process
Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. It usually consumes no more than 10% of the capacity of the Development Team.
How frequently the Product Owner should communicate and re-iterate his product vision to the Scrum Team and the Key Stakeholders?
Early and The PO should communicate and re-iterate his product vision to the Scrum Team and the Key Stakeholders early and often, reminding all involved of how that vision aims to maximize the value of the product and of the work the Scrum Team performs.
What factors should be considered by the Product Owner in the release decision (select four)?
- The costs and benefits of the upgrade
- Can customers actually absorb the new release?
- The customers that will be constrained by the new release
- The risk that the product’s value can get out of line with the marketplace
While Scrum doesn’t require a release to occur every Sprint, it should be noted that the more elapsed time that accumulates since the last release, the higher the risk that the product’s value will get out of line with the marketplace. Product Owners should keep this risk in the forefront of their mind.
Another factor in the release decision is whether your customers can actually absorb your frequent releases. Most customers approach this upgrade decision using a common sense method of weighing the costs and benefits of the upgrade(new increment). This is all the more reason to make sure that your releases are of the utmost value, and offer relatively low absorption costs. Regardless of the benefits and costs, some customers will still be constrained, so this constraint should be a consideration when deciding how often or whether to release.
The PO is the one and only person who can decide whether to release the latest increment of the product.
The Increment is “Done” by its definition.
How can the Product Owner bring his product vision to life (select 3)?
- Via the Product Backlog and iterating towards that vision every Sprint
- Utilizing the underlying empirical product planning features of Scrum
- Articulating the product vision to the Scrum Team and the Key Stakeholders early and often
The PO should communicate and re-iterate his product vision early and often, reminding all involved of how to help maximize value. Utilizing the underlying empirical product planning features of Scrum, the PO should also be ready to make strategic pivots for the product vision. This vision is brought to life in a more tactical way, via the Product Backlog and iterating towards that vision every Sprint.
