PSM I Flashcards
(101 cards)
Burn-down chart
a chart which shows the amount of work which is thought to remain in a backlog
Time is shown on the horizontal axis and work remaining on the vertical axis. As time progresses and items are drawn from the backlog and completed, a plot line showing work remaining may be expected to fall. The amount of work may be assessed in any of several ways such as user story points or task hours. Work remaining in Sprint Backlogs and Product Backlogs may be communicated by means of a burn-down chart. See also: Burnup Chart
Burn-up Chart
A chart which shows the amount of work which has been completed. Time is shown on the horizontal axis and work completed on the vertical axis.
Coherent/Coherence
The quality of the relationship between certain product backlog items which may make them worthy of consideration as a whole.
Daily Scrum
Scrum event that is a 15-minute time-boxed event held each day for the Developers. The Daily Scrum is held every day of the Sprint. At it, the Developers plan work for the next 24 hours. This optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work. The Daily Scrum is held at the same time and place each day to reduce complexity.
Definition of Done
is a formal description of the state of the Increment when it meets the quality measures required for the product.
The moment a Product Backlog item meets the Definition of Done, an Increment is born.
The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review.
Developer
any member of a Scrum Team, that is committed to creating any aspect of a usable Increment each Sprint regardless of technical, functional, or other specialty.
Empiricism
the philosophy that all knowledge originates in experience and observations. It’s a cornerstone of the scientific method and underlies much of modern science and medicine. In the context of Scrum, empiricism refers to the idea that solving complex problems, or doing complex work, can only be done using an exploratory process rather than relying on predetermined plans.
Engineering standards
a shared set of development and technology standards that Developers apply to create releasable Increments of software.
Increment
Scrum Artifact that defines the complete and valuable work produced by the Developers during a Sprint. The sum of ALL INCREMENTS FORM A PRODUCT.
Product Backlog
A Scrum Artifact that consists of an ordered list of the work to be done in order to create, maintain and sustain a product.
Managed by Product Owner
Product Backlog Refinement
Activity in a Sprint through which the Product Owner and the developers add granularity to the Product Backlog.
Product Owner
Role in Scrum accountable for maximizing the value of a product, primarily by incrementally managing and expressing business and functional expectations for a product to the Developers.
Product Goal
The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define “what” will fulfill the Product Goal.
Which two things are appropriate for a scrum master to do if the scrum team doesn’t have the tools and environment to completely finish each selected product backlog item?
- Coach the Development Team to improve its skills, tools, and infrastructure over time and adjust the Definition of Done accordingly.
- The team must create a realistic Definition of Done under current circumstances.
How much of the Sprint backlog must be defined during the Sprint Planning event?
Enough so the Development Team can create its best forecast of what is can do, and to start the first several days of the Sprint.
How is management that is external to the Scrum Team involved in the Daily Scrum?
Managers are not required at the Daily Scrum.
When Developers are having trouble delivering an increment because they do not understand a functional requirement, what should they do?
Collaborate with the Product Owner to determine what is possible and acceptable.
The developers ask their PO to re-order the Product Backlog. The team is waiting for an external supplier to deliver a component. Without that component, there will not be enough work in the next Sprint to occupy the full team. As the Scrum Master, what advice would you give the PO?
Remind the Product Owner that his primary concern is the flow of value reflected in the ordering of the Product Backlog.
A developer takes the Scrum Master aside to express his concerns about data security issues. What should the Scrum Master do?
Ask the Developer to share the concern with the team as soon as possible.
Why is the Daily Scrum held at the same time and same place?
The consistency reduces complexity.
What is the typical size for a Scrum Team?
10 or fewer.
What is the function or purpose of Management in Scrum?
Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to encourage organizational change that fosters empiricism, self-management, bottom-up intelligence, and intelligent product delivery.
Management has no official role or accountability on a Scrum Team. However, management external to the Scrum Team is relevant in setting the vision and strategy to guide the overall direction of the organization.
Who has the final say on the order of the Product Backlog?
The Product Owner.
Which statement best describes the Sprint Review?
It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.
Every event in Scrum, besides the Sprint, which is a container for the other events, is an opportunity to Inspect and Adapt.