No student devices needed. Know more
104 questions
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.
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 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.
Who should know the most about the process toward a business objective or a release, an be able to explain the alternatives most clearly?
The Scrum Master
The Product Owner
The Development Team
The Project Manager
When the Sprint is over?
When all Product Backlog items meet their definition of done
When the time-box expires
When all the tasks are completed
When the product Owner says it is completed
What questions should be answered in the stand-up meeting?
What will I do today?
What did I do yesterday?
Do I see any impediment?
What worked well?
What could be improved?
The time-box for a Daily Scrum is?
15 minutes for a 4 week sprint. For shorter Sprints it is usually shorter.
Two minutes per person.
4 hours.
15 minutes.
Which is the most popular methodology for Agile
Waterfall
SDLC
ScrumBan
Scrum
What is a requirement for Scrum
Using JIRA
Being disciplined in applying the process
Having a separate Scrum master
Having 4-weeks sprints
What is at the heart of scrum?
Testing
Sprint planning
Daily Scrum
Sprint
When should a retrospective meeting be held?
Only at the end of a release
At the end of each sprint, before the sprint review meeting
At the end of each sprint, after the sprint review meeting
Only at the end of a project
How often should backlog grooming occur?
Once, at the beginning of the project
Once, at the end of the project
Every Sprint
Every release cycle
Who runs the Scrum Team?
The Product Owner
Trey Keller, Android Mobile Web Cart Integration Tech Lead and Proud Supporter of Jimmie Johnson and the #48 Ally NASCAR team
The Development Lead
None of the Above
What are are the different scrum events
Stand-up, Group coding, Back log refinement , Sprint Retrospective
Daily Scrum, Group coding, Back log refinement , Sprint Retrospective
Daily Scrum, Sprint Review, Back log refinement , Sprint Retrospective
Daily Scrum, Sprint Review, Sprint Planning, Sprint Retrospective
Who is the Scrum Team?
Scrum Master
Product Manager
The Development Team
Project Manager
The Product Owner
Who writes tests in a Scrum Team?
The Scrum Master
The Development Team
Coders
QA specialists
The product Backlog is ordered by:
Least valuable items at the top to most valuable at the bottom
Size
Risk
Items are randomly arranged
Whatever is deemed most appropriate by the Product Owner
Who is responsible for managing the process of work during the Sprint
The Product Owner
The Scrum Master
The Product Owner
The Development Team
What are the two primary ways a Scrum Master keeps a Development Team working as its highest level of productivity?
By keeping high value features hight in the Product Backlog
By removing impediments that hinder the Development Team
By starting and ending the meetings at the proper time
By facilitating Development Team decisions
Who creates the Definition of "Done"?
The Product Owner as he/she is responsible for the product
The Scrum Master as he/she is responsible for the Development Team's productivity
The Scrum Team , in a collaborative effort where the result is the common denominator of all members' definitions
The CEO asks the Development Team to add an urgent item to a Sprint that is in process. What should the Development Team do?
Inform the Product Owner and Scrum Master so they can work with the CEO
Add the item to the current Sprint and drop an item of equal size?
Add the item to current Sprint without any adjustments
Add the item to the next Sprint
Stand-up meeting is also known as ...
Scrum Master
Scrum Meeting
Daily Scrum
Scrum Retrospective
Who are responsible for creating user stories?
Product Owner
Scrum Team
Manager
Customer
CEO
What are the responsibilities of Scrum Master?
Removing impediments
Setting product vision and priorities
Implementing the product
Providing process leadership
Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next
Scrum Master
Product Owner
Clearly expressing Product Backlog items
Scrum Master
Product Owner
Optimizing the value of the work the Development Team performs
Scrum Master
Product Owner
Coaching the Development Team in self-organization and cross-functionality
Scrum Master
Product Owner
Who creates the Definition of "Done"?
The Product Owner as he/she is responsible for the product
The Scrum Master as he/she is responsible for the Development Team's productivity
The Scrum Team , in a collaborative effort where the result is the common denominator of all members' definitions
The CEO asks the Development Team to add an urgent item to a Sprint that is in process. What should the Development Team do?
Inform the Product Owner so he/she can work with the CEO
Add the item to the current Sprint and drop an item of equal size?
Add the item to current Sprint without any adjustments
Add the item to the next Sprint
What is a Product Backlog?
It is a living artifact of product requirements that exists and evolves as long as a product exists.
It is a formally approved list of requirements to be implemented over a set period.
It is a detailed list of functionality from which the Development Team draws items, to be complemented by a separate Technology Backlog managed by the Development Team.
It is a list of references to Use Case documents that are stored in a central repository. The references should be viewable and clickable by anybody to enhance transparency.
Ensuring the Development Team understands items in the Product Backlog to the level needed
Scrum Master
Product Owner
What does NOT belong to the agile manifesto's main pillars?
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Processes over people
Customer collaboration over contract negotiation
Which Agile Manifesto value would be most relevant to this situation – A scrum master insists on rigid compliance with a well-defined process for performing scrum?
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Responding to change over following a plan
Customer collaboration over contract negotiation
Who among the following is responsible for deciding on the Acceptance Criteria for various tasks?
Development Team
Scrum Master
Product owner
Architects
Which Agile Manifesto value would be most relevant to this situation – A customer realized in the middle of a project that what was being built will not really meet his needs and a very different solution is more appropriate; however, the new approach will significantly increase the cost and schedule for completing the effort?
Working software over comprehensive documentation
Responding to change over following a plan
Customer collaboration over contract negotiation
Individuals and interactions over processes and tools
Who among the following is responsible for achieving the maximum business value of the project?
Product Owner
Scrum Master
Development Team
Product Manager
Which statement best describes Scrum?
A complete methodology that defines how to develop software
A cookbook that defines best practices for software development
A defined and predictive process that conforms to the principles of Scientific Management
A framework within which complex products in complex environments are developed
In an Agile environment, what is the main responsibility of a tester?
There is no role as a Tester in Scrum
Send test execution reports to the stakeholders
Create automation scripts
Finding bugs
Create test scenarios and test cases
What should a Development Team do during a Sprint Planning meeting when they have realized that they have selected more than the items they can complete in a Sprint. Select 2 best choices
Get more developers onboard from other teams
Inform the Product Owner
Work overtime
Take a call to remove some of the Sprint Backlog Items
What are the main responsibilities of a self-organizing development team? Select 3 best choices
Develop the Sprint Backlog items
Estimate the items to be picked up for the upcoming Sprint
Monitor the Project’s performance and send a report to stakeholders
Create new Product Backlog items
Tasking the current Sprint Items
What are the advantages of using a cross-functional team
Faster decision making
Improved communication between members of the team
Individual responsibility can be assigned to each member of the team based on their expertise
Option 1 & 2
When is a User Story READY? Select 2 best choices
When it has been estimated and it is small enough
When you are able to answer 3 questions – Why? (What are the stakeholders trying to achieve), What? (What is the end result of the story) and How? (What is the Implementation strategy)
When the requirement document/artifacts are reviewed and agreed upon within the team
When detailed design and test plans are complete
During Backlog Refinement, PO mentions based on vision of the product, these are my top 3 priority items. There is moment of silence. Then one team member says – “we have no idea. Let’s discuss when you’ve finished writing the requirement.” What best choice team have here
Look at the small stories irrespective of priority and plan for those
Work closely with PO and refine the top priority stories further
Reschedule the discussion once the requirement is written fully
During Backlog Refinement, a team member says “I’m just a tester. Do u mind if I join when testing stories are discussed?” What choice team have here? Select 2 best answers
This is fine. Tester can join when respective stories are being discussed
Team needs to refer their acceptance criteria. Tester needs to contribute on testing strategy of all the stories
Team should seek tester’s expertise to get the story done and plan the tasks accordingly
Team should propose smaller sessions with focused team members only to properly refine the stories
Product Backlog should be ordered on the basis of
Value of the items being delivered
The complexity of the items being delivered
Size of the items being delivered
The risk associated with the items
Based on the Scrum Team choice
Which of the following is NOT a purpose of story point estimates
Set delivery dates
Enable short-term planning of sprints
Allow for long-term forecasting
Quantify project work
The three pillars of empirical process control are:
Respect for people, Kaizen, Eliminating Waste
Planning, Demonstration, Retrospective
Planning, Inspection, Adaptation
Inspection, Transparency, Adaptation
The sprint Burndown chart is a tool used by teams to:
Measure the work left to be completed during a sprint
Calculate the amount of the teams budget remaining
Measure the work completed during a sprint
Ensuring that Daily Standup meetings are run in a timely and structured manner is the responsibility of the:
Development team
Product owner
Scrum Master
Which of the following is delivered at the end of the Sprint
A document containing test cases for the current sprint
An architectural design of the solution
An increment of Done software
Wireframes designs for User Interface
When is a Sprint Retrospective ceremony performed
Whenever the team suggests or Whenever needed
At the end of each Sprint
Whenever the Product Owner suggests
Whenever the Scrum Master suggests
When can a Sprint be canceled
The Sprint items are no longer needed
Sprint can never be canceled
When Development is unable to complete the work
Information required to start the development is not available
Whenever the Product Owner says
What is the significance of determining a Definition of Done. Select 3 best choices
Determines the objective behind each sprint
Determines the number of tasks being completed for each Sprint Backlog item
Increases Transparency
Increments delivered are more effective and potentially releasable
Develops a common understanding amongst all the team members as to what all needs to be completed to mark every item complete
What is done during a Sprint Review Meeting. Select 2 best choices
Demo of the Increment
The team discusses the improvements that can be applied for the upcoming sprints
Present the Project’s performance to the Stakeholders
Inspect progress towards the Sprint Goal
Discuss the architectural and technical aspects of the project
Who should necessarily attend the Daily Standup meeting
The Scrum Team
The Development Team and the Product Owner
The Development Team and the Scrum Master
The Development Team
The Scrum Team and the Stakeholders
Which of the following activity is not timeboxed
Sprint Retrospective
Sprint
Product Backlog Refinement
Daily Standup
Sprint Review
During sprint execution, when are new sprint tasks added
When the product owner identifies a new task
When the scrum master identifies a new tak
Never. The sprint tasks are fixed and decided during sprint planning
As soon as possible after they are identified, unless they reflect a scope change in the sprint goals
When the scrum master or PO approves them
What is a Scrum Team expected to do during the first Sprint. Select 2 best choices
Test the product
Develop a detailed plan for the rest of the project
Nail down the architecture
Build a thin slice of potentially shippable functionality
When Scrum teams fully embrace Agile technical practices, how often do these teams integrate their work and rerun regression tests
Continuously as things change; potentially many times per day
Only at the end of each sprint
Once per day (or night)
What is the recommended size of a scrum team
It doesn't matter, as long as the team is cross functional
9 plus or minus 3
10 plus or minus 3, or more if the team is geographically dispersed
7 plus or minus 2
Which is not an effective way to encourage collaboration between the scrum development team and product owner
Act as a go-between for them
Teach the team to talk in terms of business needs and objectives
Listen to their communications
Teach the product owner about technologies the team uses
What is a good size for a sub task
One person per day or less, so other team members can easily detect when a task is stuck
2-3 people 2-3 days, so that every product backlog item equals one sprint task
Which of the following are explicitly defined questions in the daily Scrum meeting
What time is the next daily scrum meeting
What did I do yesterday (or since last scrum meeting)
What are my actuals compared to my estimates
What impedes me (blocks my progress)
What will I do today (or before the next scrum meeting)
The length of a Sprint should be?
Short enough to keep the business risk acceptable to the Product Owner.
Short enough to be able to synchronize the development work with other business events.
No more than one calendar month.
All of these answers are correct.
The definition of "Done" describes the work that must be completed for every Product Backlog item before it can be deemed releasable. What should the Development Team do when, during the Sprint, it finds out that a problem outside of their control blocks them from doing all this work?
Immediately raise the issue to the Scrum Master as an impediment.
Complete the work that can be done on as much scope as possible and use the Sprint Review to plan the rest with the stakeholders.
Complete the work that can be done on as much scope as possible and complete the rest during the "hardening" sprints at the end of the release.
Cancel the Sprint.
Stop using Scrum.
What happens during Sprint 0?
Overall planning, base system architecture, base design, version control and continuous integration setup.
Establish base system architecture and design, install version control and continuous integration setup.
Base system architecture and design.
There is no such thing as Sprint 0.
Requirements gathering, version control setup, and continuous integration setup.
The three pillars of empirical process control are?
Respect For People, Kaizen, Eliminating Waste
Planning, Demonstration, Retrospective
Inspection, Transparency, Adaptation
Planning, Inspection, Adaptation
Transparency, Eliminating Waste, Kaizen
To deliver a single product, three Development teams are formed. How many Product Owners are needed?
As many as recommended by the Scrum Master
Three
One
Explore all questions with a free account