Das ist ein zeitlich begrenztes Quiz.
Du hast 1 Stunde um die 82 Fragen in diesem Quiz zu beantworten.
Which three of the following are true about Scrum?
Each component of Scrum serves a specific purpose and is essential to Scrum's success.
Scrum is like traditional processes but with self-organization to replace Project Managers
Scrum is a methodology, where you can pick and choose which parts of Scrum you think will work for your environment
Scrum is a framework for developing and maintaining complex products.
Scrum is based on empiricism and lean thinking.
What are the consequences if the team doesn't have a consistent Definition of Done?
The Developers may not know how many items they can accomplish in a Sprint
The Product Owner may be unable to get gauge the progress toward his/her goals.
The Developers may not know what work is entailed in completing selected Product Backlog items.
The stakeholders may not know what they are inspecting at the Sprint Review.
All of the above.
What is the commitment for the Scrum Team that is expected for the Sprint Backlog?
Sprint Goal
Product Goal
Definition of Done
Product Release Date
What is the commitment by the Scrum Team that is expected for the Increment?
Product release date
The Backlog ______________ is to the Product Backlog what a Sprint Goal is to Sprint Backlog.
Commitment
The Developers need to answer the 3 questions at the Daily Scrum:
True
False
What is one way a Scrum Team can address non-functional requirements (NFRs) on a Scrum project?
Add them the Definition of Done
There are no NFRS on Scrum Projects
Have a separate Kanban team work on them
Address them during hardening or release Sprints
The Scrum Team is continuously arguing about which with Agile Tool to use for requirements. What should the Scrum Master do to resolve the issue? (pick two)
Pick a tool for the team and tell them to pilot it for three months
Use coaching techniques to get to the root cause of the disagreement
Call a meeting of the Developers' functional managers to make a decision
Involve the entire Scrum Team in the decision-making process
After a backlog refinement meeting, the Developers complained that they don't have the specialized skills to accomplish the upcoming work. What should be the Scrum Master's approach to solving the problem?
Do whatever it takes to keep the team busy
Identify options to ensure fully integrated increments
Have the Product Owner re-order the work to maintain the velocity of the team
Involve the Developers in the decision-making process
The Developers no longer have to answer the same 3 questions every day during the Daily Scrum:
There are 3 topics covered in the Sprint Planning meeting. What questions are supposed to be addressed?
Incorrect, there are only two required topics, what, and how.
Why is this Sprint valuable? What can be Done this Sprint? How will the chosen work get done?
When is the next release? Who will be working on what? Why should we do it?
What is the budget? What is the scope? What is the timeline?
Which 3 topics are NOT covered in the Sprint Planning meeting.
Why is this Sprint valuable?
What can be Done this Sprint?
How will the chosen work get done?
Who is taking ownership for which story?
What is the duration until the next release?
What is the budget for this Sprint?
There is only one increment per Sprint:
There can be multiple increments delivered per Sprint:
Who is responsible for creating the Definition of Done?
Developers
Scrum Master
Product Owner
Scrum Team
Which two criteria should always be part of the Definition of Done?
Ready for release
Fully integrated
Ready for integration
Product Owner sign-off
Whatever the developers were able to accomplish
Which one is NOT a Pillar of Scrum?
Transparency
Inspection
Adaptation
Empiricism
The Product Owner is not required at the Daily Scrum.
The optimum size of a Scrum Team is:
It depends
Less than 10
7
5
7 plus or minus 2
A Product Owner should have a single metric to measure the value it is delivering each Sprint
The total cost of ownership (TCO) for a product is the sum of all investments required to design, develop, run and support the product
Pick which 3 activities are the responsibilities of the Product Owner in Scrum.
Provide Estimates
Order the backlog
Commit to the Sprint
Perform user acceptance
Facilitate meetings
Champion Scrum
Perform release planning
Design the software
What is the most effective way to order the Product Backlog?
Risk
It is up to the Product Owner to decide
Size
Complexity
Product Backlog Items should always be expressed as User Stories.
The Product Owner can delegate the ordering of the Product Backlog
How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog?
The Developers pull in work in agreement with the Product Owner
Each Scrum Team takes an equal number of items.
The Product Owner should provide each team with its own Product Backlog
The Scrum Team with the highest velocity pulls Product Backlog items first.
The Product Backlog is ordered by:
Cost
Importance
The Product Owner is responsible for the Definition of Done.
Non-functional requirements (NFRs) must be captured in the Definition of Done.
The Product Owner actively asks for stakeholder input into the Product Backlog.
The Product Owner should be with the Developers full time.
How does the Product Owner measure success and measure that they are delivering value? (Pick Three)
Delivery of all promised requirements
Customer Satisfaction
Delivery within the planned time
Release Frequency
Within allocated budget
Time to Market
Velocity
Which best describes the Product Backlog?
It is allowed to grow and change as more is learned about the product and its customers.
It is baselined to follow change management processes.
It contains all foreseeable tasks and requirements from which the Scrum team can develop and maintain a complete project plan.
It provides just enough information to enable a Scrum team to start the design phase of a product.
Which phrase best describes a Product Owner?
Business Analyst
Requirements Specialist
Value Optimizer
Team Lead
The Product Owner needs to be aware of which three things to effectively maximize the value of the product?
Team Velocity
Competitive Research
Customer Feedback
Unit Testing Results
Product Vision
In what ways does the Product Owner manage the value of the product? (Pick two)
MoSCoW Analysis
Product Backlog Order
Customer Feedback via Frequent Releases
User Acceptance Testing
Organizational value is captured through which three evidence-based metrics?
Current Value
Ability to Innovate
Scrum does not use evidence-based metrics
Revenue generation is the primary factor in determining value.
If your Product Owner will not be available for the entire Sprint, what should you do?
The team can work without the Product Owner for one Sprint if they are mature
A new Product Owner should be assigned
The Scrum Master should play the role
Work on technical user stories only
Who hires the Product Owner?
The Scrum Master
The Development Lead
Whoever is accountable for the product ROI
The entire team
A Product Owner and project manager are basically the same thing in Scrum.
Which term best describes the role of the Product Owner?
Agile Program Manager
Portfolio Manager
Value Maximizer
Scope Minimizer
Servant Leader
The Product Owner is an optional attendee of the Sprint Retrospective
The Product Owner must provide transparency to the status of the Product Backlog using a:
Sprint Burndown Chart
Release Burndown Chart
Any means necessary to reflect work finished and work remaining
Cumulative Flow Diagram
A baseline Product Backlog is called:
Ready
Sprint Backlog
It is never baselined, it is a living artifact
Release Plan
Product Roadmap
The authority of the Product Owner is limited by:
The Shareholders
The Customer
The Chief Product Owner
Nothing
Customer Satisfaction is a key metric for the Product Owner, how often should it be measured?
Once a Year
Every Day
Once a Month
Frequently as needed
The Product Owner should invite stakeholders to the retrospective.
An important customer wants a new feature as soon as possible, what should the Product Owner do?
Cancel the Sprint and start over
Add the features to the Product Backlog
Add the feature to the current Sprint
Discuss with the team the correct approach
Acceptance criteria is a requirement for every Product Backlog item to be "Ready" for development.
What should the Product Owner focus on to ensure value is being delivered to the customer? (Pick 3)
Ease of use by customers
Velocity of Developers
Percentage of functionality used by customers
Cost per feature delivered
A key measure of success for the Product Owner to track is the Developers' velocity.
Pick the two most important roles of the Product Owner.
Be available to the Scrum team for questions
Provide Project Status Reports
Create and clarify valuable requirements with customers
In the Sprint Review, the upcoming Product Backlog is reviewed by the stakeholders.
Software dependencies can influence how the Product Owner orders Product Backlog items
The Product Backlog is updated only during backlog refinement and Sprint Planning.
What is the benefit of ordering the Product Backlog using value points?
Value points are never used in Scrum
Value points are not mandatory but are a best practice for providing transparency in the order of the Product Backlog
Value points are the only way to ensure value is being measured in the Product
Backlog
There are 5 teams working on a product, how many Product Owners would there be?
1
Let the team decide
When does the second Sprint start?
Immediately following the first Sprint.
It depends on how many issues were raised at the Retrospective.
After the Sprint Backlog has been created.
Once the customer accepts the first Sprint Increment.
At the end of a Sprint a Product Backlog item worked on during the Sprint does not meet the Definition of Done. What two things should happen with the undone Product Backlog item?
Leave it up to the stakeholder to decide if they should accept it.
Add it to the Product Backlog for prioritization by the Product Owner.
Remove it from the Sprint Review.
Change the Definition of Done during the Sprint.
Give the team partial credit for their effort and add it to the next Sprint Backlog.
Which of the following is required by Scrum?
Sprint Retrospectives
Standing up at the Daily Scrum
Burndown Charts
Release Planning Meetings
All of the above
Which three of the following are feedback loops in Scrum?
Backlog Refinement
Daily Scrum
Sprint Review
Sprint Retrospective
Release Planning
The Product Owner determines how many Product Backlog items the Developers select for a Sprint:
When can the Developers cancel a Sprint?
Whenever they can't complete the forecast
Never
With permission from the Scrum Master
If a key resource leaves the team
What are two responsibilities of testers in a Scrum Team?
There are no tester roles on Scrum
Everyone on the Team is responsible for quality
Updating the defect log
Performing acceptance testing
Preventing and finding defects
When is a Sprint over?
When the timebox expires
When the Sprint Backlog is complete
Whenever the Product Owner decides
When the tasks are complete
What is the tactic a Scrum Master should use to divide a group of 100 people into multiple Scrum Teams?
Implement SAFE
Create teams based upon skills sets and/or location
Ask the developers to divide themselves into teams.
Divide teams by features
When should a Sprint Goal be created?
It must be established before Sprint Planning
During Sprint Planning
During the Sprint
A Sprint Goal is not necessary
Sprint burndown charts are an efficient tracking tool because they show:
Estimate of work remaining over the rest of the Sprint
Performance of the Developers.
Hours spent on backlog items.
The level of effort accomplished to date.
Of the following choices, what is the most effective way a Scrum Master can keep the Developers working at its highest level of productivity?
Facilitate decision making and removing impediments.
Ensuring high value items are prioritized.
Preventing change to the Sprint Backlog.
Making sure meetings start and end on time.
Which three phrases best describe the purpose of a Definition of Done?
Defines what is takes to get an Increment of work ready for release.
Helps the Developers forecast what they can accomplish in a Sprint.
Creates transparency as to what was accomplished at the Sprint Review.
Is a checklist for what needs to be included in technical documentation.
Ensure developers accomplish all their tasks.
A Scrum Master is introducing Scrum to a new Scrum Team. The Developers have decided that a retrospective is unnecessary. What action should the Scrum Master take?
Cancel them
Hold them every other Sprint
Facilitate effective Sprint Retrospectives
Escalate to management
Every Scrum Team should have:
The technical lead.
People with the skills necessary to create a releasable Increment.
At least one developer and tester.
The Product Owner makes sure the team selects enough from the Product Backlog for a Sprint to satisfy the stakeholders.
What is the best Scrum Team structure to produce a fully integrated product?
Each team members focuses on their area of specialty: UI, Data, QA.
Each member designs, codes, and tests functionality from beginning to end.
A new developer has joined the existing Scrum team. He/she is having continuing conflicts with existing members and is making the environment hostile. If necessary, who is responsible for removing the new team member, and why?
The manager to whom he/she reports is responsible, because he/she has authority for hiring and firing
The Scrum Team is responsible because it is a self-managing Team.
Scrum Master is responsible because he/she needs to remove impediments
Product Owner is responsible because he/she controls the return on investment (ROI) of the work
The best describes the topics covered in Sprint Planning?
Who is on the team and what team member roles will be
Why is this Sprint valuable, what can be done and how to do it
How conditions have changed and how the Product Backlog should evolve
What went wrong in the last Sprint and what to do differently this Sprint
When may a Scrum Team change its engineering practices?
Prior to starting a new project
Whenever needed
During the Sprint Retrospective
Prior to starting a new Sprint