Font size
WorksheetsScrum 101
Total questions: 25
Worksheet time: 25mins
What is Scrum?
A tedious methodology focusing on KPI's and status meetings.
A framework for developing, delivering, and sustaining complex products.
A set of strict rules and processes put in place to deliver software quickly and frequently.
A linear, sequential approach to the software development life cycle that emphasizes a logical progression of steps.
Who runs the Scrum Team?
The Product Owner
The ScrumMaster
The Development Lead
Trey Keller, Android Mobile Web Cart Integration Tech Lead and Proud Supporter of Jimmie Johnson and the #48 Ally NASCAR team
None of the Above
What is the purpose of the Daily Scrum / Daily Stand-up?
To provide status updates to the Product Owner and ScrumMaster.
To get work assignments for the day.
To get all of the developers' questions from the day before answered.
To plan work for the next 24 hours, optimize team collaboration and performance through inspection of progress, and forecast upcoming Sprint work.
The rules of Scrum are most clearly defined by which three things?
Roles, events, and artifacts.
Backlogs, meetings, and processes.
Training, improvement, and delivery.
Transparency, inspection, and adaption.
The Agile Manifesto consists of four _______, and twelve _______.
roles, events
methodologies, processes
values, principles
stand-up questions, rules
Scrum is founded on empirical process control theory, or empiricism. What are the three pillars of empiricism?
Roles, events, and artifacts.
Transparency, inspection, and adaption.
Hypothesis, experimentation, and conclusion.
Question, answer, and decide.
The Product Owner's main responsibilities are (pick all that apply):
Assign work to the team.
Maximize the value of the product resulting from work of the Development Team.
Clearly expressing business and customer requirements in the Product Backlog items and prioritizing those items to best achieve goals and missions.
Creating reports and holding status report meetings.
Prioritizing the Sprint Backlog.
Once a Sprint has started, _________ prioritizes the Sprint Backlog and ________ can change the amount of work the team committed to.
the Development Team, the Development Team
the Product Owner, the Product Owner
the Development Team, the Product Owner
the Product Owner, the ScrumMaster
The Product Owner, no one
What should be the output delivered at the end of each Sprint?
A demo of the work completed and an explanation of what was not completed.
An explanation of the work completed and new Backlog items created for the work that wasn't completed.
A status report for the key stakeholders and leadership.
A potentially releasable Increment of "Done" product.
Who tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality?
The ScrumMaster
The Product Owner
The Solutions Manager
None of the Above
What titles/roles are defined as Development Team members?
Product Owner, ScrumMaster, Developer, and QA.
None. Scrum recognizes no title or sub-teams in the Development Team.
Junior developer, senior developer, and development lead.
Developer, development lead, and quality assurance tester.
The ScrumMaster is responsible for (pick all that apply):
Facilitating Scrum events as requested or needed.
Coaching the Development Team in self-organization and cross-functionality.
Telling the Development Team how to turn a Product Backlog into a releasable Increment.
Ensure that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible.
Helping employees and stakeholders understand and enact Scrum and empirical product development.
Which of this are not identified as a Scrum Event?
Sprint Planning
Story Refinement
Sprint Review
Sprint Retrospective
Sprint
Who has the authority to cancel a Sprint before the time-box is over?
The ScrumMaster
The Development Team
The Solutions Manager
The Product Owner
Who is responsible and accountable for ensuring everything a Development Team committed to is completed within a Sprint?
The Development Leads
The ScrumMaster
Every single member of the Scrum Team
The Product Owner
The Solutions Manager
True or False: If the Team commits to 10 stories in a Sprint, completes 15 stories, but 3 of the stories the Team originally committed to were not completed, the Team has still met their commitment.
True
False
What are the Scrum Artifacts and who owns each one? (pick all that are correct)
Product Backlog - owned by the Product Owner
Sprint Backlog - owned by the Development Team
Increment - owned by the Development Team
Monitoring of Progress Towards Goal - owned by the Product Owner
Monitoring of Sprint Progress - owned by the Development Team
Sprint Planning is meant to answer what two questions? (Choose the correct two answers below)
How will the work needed to deliver the Increment be achieved?
What can the team do to stay busy?
What can be delivered in the Increment resulting from the upcoming Sprint?
Can the QA team test everything the Developers complete?
What is the intended purpose of tracking Sprint Velocity?
To monitor and judge the increase or decrease of progress from Sprint to Sprint.
To identify impediments preventing the Team from completing the work they have committed to.
To forecast the amount of work a Team can typically complete during a Sprint.
To add transparency and show that a Development Team is delivering value.
Under what circumstances would it make sense to cancel a Sprint?
The Product Owner has decided mid-Sprint that some other chunk of work is now more important than what the team has committed to.
A member of leadership has determined that they want some new initiative worked on and completed immediately.
It never makes sense to cancel a Sprint.
The Sprint Goal has become obsolete because the company changes director or the market or technology conditions have changed.
What does 1 story point equate to?
One day's worth of development work from concept to completion.
One hour worth of development work from concept to completion.
An abstract measurement of the simplest, baseline amount of effort, complexity, and risk a User Story presents on average and relative to type of work the Development Team typically does.
An absolute 100% accurate measurement of how much effort it will take for the Development Team to deliver a story without question.
What is Acceptance Criteria?
The functional requirements of how to complete a User Story.
Conditions a software product must satisfy to be accepted by the user, customer, or stakeholder.
Business requirements including all designs, research, and documentation to answer all questions a developer might have to complete a User Story.
Optional as long as there is separate technical documentation and fully vetted UX designs.
What are the five key components of a User Story?
Business requirements, functional requirements, designs, documentation, and estimates.
Fully vetted requirements, UX designs, all questions answered, all research completed, and absolute assurance that the story will be completed as is.
An epic, a feature, a role, an ask, and a reason.
A user role, what the user wants, a quantifying value, acceptance criteria, and small and simple.
When estimating a story, the Team should consider what? (pick all that apply)
Effort
Time
Complexity
Risk
Individual Skill Levels
What is the purpose of Tasks being created during Sprint Planning and the Estimated Time to Completion being added?
To ensure the Development Team is actually working.
To track hours on a Project Manager's Gantt Chart.
To identify how quickly a developer can complete an entire User Story.
To help the team understand the breakdown of the work and how long the Tasks take to complete at a granular level.
