Requirements in Scrum
What do we call requirements in Scrum?
User Stories
True or False: It is ok for a more experienced team member to estimate a piece of work for the team if the senior member is more knowledgeable.
False; there is no role of a senior member in Scrum. Estimation is done as a team with "junior" members estimating as well.
True or False - Can the Scrum Team have 25 people?
False - Scrum teams should be no more than 10
True or False - there are no deliverable dates in Scrum
False - Scrum just does not estimate upfront but there is a way to provide dates
It initiates the Sprint by laying out the work to be performed for the Sprint: The Why, the What and the How.
Sprint Planning - The purpose of sprint planning is to define what can be delivered in the sprint and how that work will be achieved. Sprint planning is done in collaboration with the whole scrum team. Up to 4 or 8 hours.
No more Business Requirements document but Scrum uses this instead to store requirements
Product Backlog
Who has the final say in the ordering of the product backlog items?
Product Owner
This person is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
Product Owner - PO has this responsibility although they consult with their stakeholders, the Team only deals with the PO. PO is the person who represents the stakeholders, is the voice of the customer, provides direction to the team, makes priority decisions, and is responsible for the project success and ensuring that the team delivers value to the business
True or False: Scrum cannot work when there is a hard deadline
False. Scrum can work when there is a hard deadline but Scrum accepts that no one can 100% predict everything that will be delivered by a specific date up front. That is the problem with Waterfall.
A 15-minute event to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary.
Daily Scrum - this is a critical concept/meeting. Daily meeting no more than minutes to raise blockers, ask for help, request partnership, update on progress.
True or False - Requirements are locked requiring a change request to make changes thereafter.
False - Change requests goes away, Scrum welcomes changes even late in the development cycle
True or False: The scrum team does not have testers and work is passed on to a testing team once completed in the sprint.
False; Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint.
Accountable for the Scrum Team’s effectiveness, removal of impediments, and keeps the team focused
Scrum Master - this is not the Project Manager. There is not role of a PM in Scrum. The team manages themselves.
What is velocity?
Velocity is a scrum metric that measures the rate at which development teams deliver business value in terms of story points. It indicates the average amount of the product backlog that is turned into an increment of a product during a scrum team’s sprint.
Meeting to understand just enough information about work that is likely coming up in the next 1-3 sprints (10% of the current sprints capacity should be used for this).
Backlog Refinement
What does an "ordered backlog" mean?
Requirements are listed in order of importance no more High, Medium, or Low rankings. Scrum requires ordering reuirements 1 through X
True or False: If needed to complete work that is taking longer than expected, the sprint duration can be extended if the team agrees
False
This person discusses the objective that the sprint should achieve and presents the Product Backlog Items that (if completed in the sprint) would achieve the sprint goal?
Product Owner
Who is responsible for estimating the work in the scrum team?
The Development Team. In Scrum, the Development Team are those doing the work, not developers. This includes developers but also testers. Only the people doing the work estimate the work.
Meeting to gather information about the process and choose 1-3 actionable goals that can be immediately addressed in the next sprint.
Sprint Retrospective
What does MVP stand for and what does it mean in Scrum?
Minimum Viable Product - A minimum viable product (MVP) is a concept from Lean Startup that stresses the impact of learning in new product development. Eric Ries, defined an MVP as that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.
Which Scrum meeting is critical for delivering work in that it allows team members time to vet the work only committing to what will be included in the next sprint during this meeting?
Sprint Planning
True or False: UAT Testers are not part of the Development team in Scrum
False - everyone required to take any request to completion should be part of the Development Team. There is not separate UAT Phase in Scrum.
A concrete stepping stone toward the Product Goal
An increment - In Scrum, an increment is defined as a "potentially releasable" portion of work that adds value to what was delivered in the previous increment. In Scrum the goal is to deliver value to your customer as soon as possible and as frequently as possible. No more large projects and requirements.
A event to inspect the outcome of the Sprint and determine future adaptations.