PSM1 Q&A
"Done" ; definition of "done"
At the end of a Sprint an increment MUST be ___________, and usable meeting the Scrum Teams _______________.
Sprint Review
Based on what was done in a sprint and any changes to the Product Backlog during the Sprint, attendees of this meeting collaborate on the next things items to do for optimized value.
Fixed immediately
Bugs discovered in Sprint should be 1. Send to the Junior Developer to fix 2. Added to the bug tracking repository and left for a later Sprint 3. Ignored if not created by me 4. Fixed immediately
Reviewed with the Product Owner and added to the Product Backlog
Bugs discovered out of Sprint should be 1. Investigated and fixed immediately by the Development Team 2. Reviewed with the Product Owner and added to the Product Backlog
Development Team; Product Owner and Scrum Master ; Sprint Goal; Increment
By the end of Sprint Planning the _____________________should be able to explain to the _______and ________ how it plans to work as a self-organizing team to accomplish the ______________ and create the anticipated ____________.
Specification by Example
Calls for using realistic examples from past experience instead of untested or abstract statements in the description of the desired functional behavior
business requirements, market conditions, or technology
Changes in (3 blanks) may cause changes in the product backlog.
Scrum
Consists of Scrum Teams and their associated events, artifacts, and roles as defined in the Scrum Guide.
1. Allows teams to detect problems early 2. Less back-tracking to discover where things went wrong, so you can spend more time building features 3. Stop waiting to find out if your code's going to work
Continuous Integration (CI) provides the following advantages Select all that apply 1. Allows teams to detect problems early 2. Less back-tracking to discover where things went wrong, so you can spend more time building features 3. Stop waiting to find out if your code's going to work 4. Automatically eliminates all integration issues
simple integer
Cyclomatic complexity is expressed as a _________________.
Daily Scrum
Daily time-boxed event of 15 minutes, or less, for the Development Team to re-plan the next day of development work during a Sprint.
Incremental
Delivery of "done" that insures that there is always a useful version of working product available.
As needed, while taking into account a short term reduction in productivity.
Development Team membership should change: 1. Every Sprint to promote shared learning. 2. Never, because it reduces productivity. 3. As needed, while taking into account a short term reduction in productivity. 4. As needed, with no special allowance for changes in productivity.
Developers
Development Teams include which role(s)? Pick all that apply 1. Business Analysts 2. Testers 3. Software Architects 4. Developers
1. Skills 2. Mindset 3. Practices 4. Silo-Mentality
Devops bridges the gap between dev and ops in terms of (4) :
Sprint Retrospective
During each _______________ meeting, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of "done."
False
During the Daily Scrum, the Development Team must answer the 3 questions True False
Teach the Development Team to keep the Daily Scrum within the 15 minute time-box.
During the Daily Scrum, the Scrum Master's role is to: 1. Lead the discussions of the Development Team. 2. Make sure that all 3 questions have been answered. 3. Manage the meeting in a way that each team member has a chance to speak. 4. Teach the Development Team to keep the Daily Scrum within the 15 minute time-box. 5. All answers apply.
Sprint Review
During the _____________ the Scrum Team and stakeholders collaborate about what was done in the Sprint.
Sprint Review
During this meeting attendees take into account what was done during the Sprint, and any changes to the Product Backlog, in order to collaborate what items to do next for optimized value.
Increment ; Increments
Each __________ is additive to all prior ____________ and thoroughly tested, ensuring that all increments work together.
1. It is done by the actual developers who will carry out the work 2. It is done by a group 3. Estimates are made relative to similar things
Estimation is best when Pick all that apply 1. It is done by a group 2. Estimates are made relative to similar things 3. It is done by the Lead Developer alone 4. It is done by the actual Developers who will carry out the work
Self-Organizing; Sprint Goal ; Increment
Every day the Development Team should understand how it will work together as a _________________ team to accomplish the _______________ and create the anticipated ________ by the end of the Sprint.
Developer
Everyone on the Development Team is known as a _____________ regardless of the work being done by the person.
does not
Feature toggle ______________ impact the overall accessibility of the system by users.
1. Sprint Review 2. Sprint Retrospective 3. Sprint Planning
First is the _____________ meeting then the ______________ meeting then the_______________ meeting.
clear and detailed
Higher ordered PBIs tend to be more ______ and_______ than lower ordered ones.
As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of done.
How much work must a Development Team do to a Product Backlog item it selects for a Sprint? 1. As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of done. 2. As much as it can fit into the Sprint. 3. All development work and at least some testing. 4. Analysis, design, programming, testing and documentation.
Whenever new or changed code is checked into version control.
How often should the build be executed?
Continuous Integration
If multiple teams are working on the same product and it is taking a long time to debug integration issues, what engineering practice would be the best solution? 1. Collective Code Ownership 2. Test Driven Development 3. Continuous Integration 4. Version Control 5. Pair Programming
The Dev Team of an increment must define the definition of "done."
If the definition of "done" for an increment is NOT part of the conventions of the development organization then :
All Scrum Teams must follow it as a minimum.
If the definition of "done" for an increment is part of the conventions, standards, or guidelines of the development organization then :
The Dev Teams on all Scrum Teams must mutually define the Definition of "done"
If there are multiple Scrum Teams working on the system or product release, the development team then:
Unit Test
In _____________the definition and boundaries of a 'unit' generally depends on the context and is to be agreed by the Development Team
Everyone
In the Sprint Review _______ collaborates on what to do next, in order to provide valuable input to the subsequent Sprint Planning meeting.
The Product Owner
In the Sprint Review __________ projects the likely target and delivery dates for the Product Backlog as it stands.
The Development Team
In the Sprint Review ____________ demonstrates the work that is has "done" and answers questions about the increment.
The Product Owner
In the Sprint Review ____________ discusses the Product Backlog as it stands.
The Development Team
In the Sprint Review ______________ discusses what went well during the Sprint, any problems had, and how they were solved.
Sprint Review
In this meeting the marketplace/potential use of the product is reviewed in order to asses what is the most the most valuable thing to do next.
Sprint Review
In this meeting the timeline, budget, potential capabilities, and market place for the next anticipated releases of functionality/capability are reviewed.
False
It is mandatory that the product increment be released to production at the end of each Sprint. 1. True 2. False
Sprint Backlog
Makes the work that the Development Team identifies necessary to meet the Sprint Goal visible.
Class Coupling
Measures the coupling to unique classes through parameters, local variables, return types, method calls, generic or template instantiations, base classes, interface implementations, fields defined on external types, and attribute decoration.
Sprint Review
Meeting for presenting the increment for feedback and collaboration.
Scrum Master
Must coach the development team in self-organization and cross-functionality.
"Ready" for selection in Sprint Planning
PBIs that can be "Done" by the Development team within one Sprint are deemed what?
more precise estimates
PBIs with greater clarity and detail to tend to also have :
1. Volunteer for tasks 2. forecasts delivery of PBIs 3. Designs Software 4. Provides Estimates 5. Makes technical decisions
Pick 5 activities that are the responsibility of the development team in Scrum :
1. Performance testing 2. Unit testing 3. Regression testing 4. Integration testing
Pick all tests that SHOULD be automated 1. Exploratory testing 2. Performance testing 3. Unit testing 4. User Acceptance testing 5. Regression testing 6. Integration testing
1.Renaming things to be more logical 2. Extracting classes, interfaces, and methods 3. moving or deleting parameters
Pick all the examples of refactoring : 1. Changing APIs 2. Renaming things to be more logical 3. Extracting classes, interfaces, and methods 4. moving or deleting parameters 5. changing external interfaces
False
Planning Poker must be used by Development Teams 1. True 2. False
Scout Rule
Practice of always leaving the code base in a little better state than it was found before modifications. Progress towards clean code.
Unit Testing
Practice of testing certain functions and areas of code or individual units of source code.
The Development Team and the Product Owner
Product Backlog items are refined by: 1. The Development Team 2. The Business analyst and the Product Owner 3. The Development Team and the Product Owner 4. The Product Owner solely
10
Product Backlog refinement should consume no more than _____ percent of the capacity of the Development Team.
there is a product
Product Backlogs exist when :
1. Description 2. Estimate 3. Value 4. Order
Product backlog items have the attributes of ____________, __________, ____________, and __________.
Sprint Goal
Provides guidance to the Development Team on why it is building the Increment.
Scrum Master
Responsible for finding techniques for effective Product Backlog management.
Nothing. Its not an acronym
SCRUM stands for 1. Super Creative Really Useful Method 2. Safe Controlled Response Under Management 3. Nothing. Its not an acronym 4. Self organising 5. Collaborative & Reflective Universal Method
1. Theory 2. Practices 3. Rules 4. Values
Scrum Masters help everyone understand :
visible ; transparency
Scrum boards are optional within scrum and make information ________ and increase___________.
True
Scrum does not have a role called "project manager." 1. True 2. False
1. Executes fast 2. Code in each test is as small as possible 3. Each test is independent of other unit tests 4. Each test makes assertions about only one logical concept
Select four desirable characteristics of a unit test. 1. Code in each test is as small as possible while maintaining readability of the code. 2. Each test is independent of other unit tests. 3. They exercise the persistence layer of a solution. 4. Each test makes assertions about only one logical concept.
1. They allow frequent validation of the unit of software being worked on, ensuring that it remains in a potentially shippable state. 2. They support continuous integration. 3. The build process is clearly defined and scripted, making it easy, consistent, and repeatable.
Select three reasons why automated builds are important. 1. They allow frequent validation of the unit of software being worked on, ensuring it remains in a potentially shippable state. 2, They support continuous integration. 3. The build process is clearly defined and scripted, making it easy consistent and repeatable. 4. They eliminate the need for Build Engineers. 5. They ensure your product remains bug free.
1. causes team members to consider each other's work and context 2. leads to higher transparency and a rapid feedback to the team
Select two (2) benefits of continuous integration : 1. eliminates bugs completely 2. causes team members to consider each other's work and context 3. build is executed once every night and at least once a weekend 4. leads to higher transparency and a rapid feedback to the team
Sprint Review
Serves the Scrum Team and the stakeholder to inspect the Increment of the product resulting from the Sprint, asses the impact of the work on the progress, and update the Product Backlog to maximize value for the next period.
Sprint Retrospective
Serves the Scrum Team to inspect the past Sprint and plan for improvements to be enacted during the next Sprint.
Sprint Planning
Serves to inspect the work from the Product Backlog that is most valuable to be done next, and to design this work into the Sprint backlog.
If they are part of the Definition of "done"
Should User Stories be part of the documentation generated by a Scrum project? 1.If they are part of the Definition of "done". 2. Always. 3. Never. 4. If the architect requires it. 5. They must be provided to the Development Team as part of the user specifications documents.
1. Smoke Testing 2. White Box Testing 3. Black Box Testing 4. Unit Testing 5. Acceptance Testing
Some functional testing techniques include (5) :
the development team
Sprint backlog and all of its items are collectively owned by _____________________.
Sprint Review
Stakeholders are actively engaged with the Scrum Team a the _______________ meeting.
False
Tasks in a Sprint Backlog must be estimated in Days/Hours 1. True 2. False
1. B. 2. A. 3. E. 4. C. 5. D.
Test-driven development defines a series of steps that are to be followed strictly. Put them in order : A.validate that the test fails B. write a unit test for new functionality C. validate that the test passes successfully D. refactor and optimize your code E. implement code necessary to pass the test
Inform the Product Owner so he/she can work with the CEO.
The CEO asks the Development Team to add a "very important" item to a Sprint that is in progress. What should the Development Team do? 1. Add the item to the current Sprint without any adjustments. 2. Add the item to the current Sprint and drop an item of equal size. 3. Add the item to the next Sprint. 4. Inform the Product Owner so he/she can work with the CEO.
1. Sprint Goal 2. Sprint Backlog
The Daily Scrum inspects progress towards what two things?
Sprint Goal
The Daily Scrum optimizes the probability that the Development Team will meet the ____________.
True
The Definition of Done is a mandatory part of Scrum False True
False, this is only a recommendation
The Development Team must be no smaller than 3 and no larger than 9 members True False
The Sprint Backlog is fully formulated in the Sprint Planning meeting and does not change during the Sprint.
The Development Team should not be interrupted during the Sprint. The Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity. Based on this, which of the following is FALSE? 1. The Product Owner can help clarify or optimize the Sprint when asked by the Development Team. 2. The Sprint Backlog is fully formulated in the Sprint Planning meeting and does not change during the Sprint. 3. As a decomposition of the selected Product Backlog Items, the Sprint Backlog changes and may grow as the work emerges. 4. The Development Team may work with the Product Owner to remove or add work if it finds it has more or less capacity than it expected.
1. Features 2. Functions 3. Requirements 4. Enhancements 5. Fixes
The Product Backlog lists all (5 blanks) that will change in the product for future releases.
False, this is only if requested
The Scrum Master must facilitate the Daily Scrum 1. True 2. False
1. Flexibility 2. Creativity 3. Productivity
The Scrum Team Model is built to optimize ______________, _______________, and ___________.
8
The Sprint Planning event is time-boxed to a maximum of __________ hours.
3; shorter
The Sprint Retrospective has a ___ hour maximum, but can be __________ with Sprints under a month long.
4
The Sprint Review is at most ___ hour(s).
Scrum Master
The _______________ teaches everyone involved in the Sprint Review to keep it within the time-box.
Development Team ; Daily Scrum
The ________________ uses the ___________ to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.
Product Owner
The ___________________decides what makes the most sense to optimize the value of the work being done by the Development Team.
previous Sprint Reviews
The amount of work remaining is compared by the Product Owner with ______________ to asses progress.
measures the coupling to unique classes through parameters, local variables, return types, method calls, generic or template instantiations, base classes, interface implementations, fields defined on external types, and attribute decoration.
The code metric class coupling measures :
Scrum Guide
The definition consisting of scrum roles, events, artifacts, and the rules that bind them together.
Immediately raise the issue to the Scrum Master as an impediment.
The definition of "done" describes the work that must be completed for every PBI before it can be deemed releasable. What should the Development Team do when, during a sprint, it finds out that a problem is outside of their control blocks them from doing all of this work?
All of these answers are correct.
The length of a Sprint should be: 1. Short enough to keep the business risk acceptable to the Product Owner. 2. Short enough to be able to synchronize the development work with other business events. 3. No more than one month. 4. All of these answers are correct.
does not
The length of a daily Scrum is time-boxed at 15 minutes, it _________________ change with the length of a Sprint.
4 hours for a monthly Sprint. For shorter Sprints it is usually shorter.
The maximum length of the Sprint Review (its time-box) is: 1. 2 hours. 2. 4 hours for a monthly Sprint. For shorter Sprints it is usually shorter. 3. As long as needed. 4. 1 day. 5. 4 hours and longer as needed.
False
The more code a Developer writes the better 1. True 2. False
3-9 people
The optimal size for a development team is :
Sprint
The purpose of each __________ is to deliver increments of potentially releasable functionality that adheres to the Scrum Team's current Definition of "done."
Sprint Review
The result of this meeting is that the Product Backlog is revised to defines the probable PBIs for the next sprint.
Smoke Testing
The results of this test is used to decide if a build is stable enough to proceed with further testing.
Sprint Goal
The selected PBIs that will deliver one coherent function.
Inspection, Transparency, Adaptation
The three pillars of empirical process control are: 1. Respect For People, Kaizen, Eliminating Waste 2. Planning, Demonstration, Retrospective 3. Inspection, Transparency, Adaptation 4. Planning, Inspection, Adaptation 5. Transparency, Eliminating Waste, Kaizen
15 minutes
The time-box for a Daily Scrum is? 1. The same time of day every day. 2. Two minutes per person. 3. 4 hours. 4. 15 minutes. 5. 15 minutes for a 4 week sprint. For shorter Sprints it is usually shorter.
15 minutes.
The time-box for a Daily Scrum is? 1. The same time of day every day. 2. Two minutes per person. 3. 4 hours. 4. 15 minutes. 5. 15 minutes for a 4 week sprint. For shorter Sprints it is usually shorter.
8 hours for monthly Sprint. For shorter Sprints it is usually shorter.
The time-box for the Sprint Planning meeting is? 1. 4 hours. 2. 8 hours for a monthly Sprint. For shorter Sprints it is usually shorter. 3. Whenever it is done. 4. Monthly.
1. Analysis 2. Design 3. Decomposition
To refine Product Backlog items, the following activities will occur implicitly or explicitly: (Select all that apply) 1. Analysis 2. Programming 3. Testing 4. Design 5. Decomposition
1. Identify Failures to improve quality. 2. Easy to test Code produced 3. Prevent future changes from breaking functionality
Unit testing has what three advantages?
Empirical
Upon what type of process control is Scrum based? 1. Empirical 2. Hybrid 3. Defined 4. Complex
All of the above
What are different types of code coverage? 1. condition 2. statement 3. path 4. function 5. all of the above
1. Exposes integration issues 2. uncovers problems early 3. provides level of confidence in changes to software not having adverse affects
What are some of the advantages of smoke testing.
1. Code coverage does not ensure that the most important or highest risk areas of the code are being exercised by tests. 2. Code coverage does not necessarily provide functional coverage. 3. Could create incentives to write tests that simply increase code coverage, rather than tests that find
What are some shortcomings of code coverage as a measurement for how well a system or product is tested? (choose 3 answers) 1. Code coverage does not ensure that the most important or highest risk areas of the code are being exercised by tests. 2. Code coverage does not necessarily provide functional coverage. 3. Could create incentives to write tests that simply increase code coverage, rather than tests that find bugs without increasing coverage. 4. Code coverage metrics vary by development platform (e.g., .NET, Java) 5. It is too complicated to explain to management.
All of the above
What are the advantages of Behavior Driven Development (BDD) ? 1. BDD ensures single source of truth by merging specification and test documentation into a single document 2. BDD can derive concrete examples in a collaborative manner from the acceptance criteria defined for each story 3. BDD bring business, developers and testers together with a common language. 4. BDD acts as a living documentation 5. All of the above
1. Clear title and proper grammar in report. 2. One bug per report. Simple and repeatable reproduction steps. 3. Expected results and observed results. 4. Build/version where bug was found. 5. Screenshots or other pictures of bug in action when user interfaces are involved
What are the attributes of a good bug report? 1. Clear title and proper grammar in report. 2. One bug per report. Simple and repeatable reproduction steps. 3. Expected results and observed results. 4. Build/version where bug was found. 5. Screenshots or other pictures of bug in action when user interfaces are involved
1. By facilitating Development Team decisions 2. By removing impediments that hinder the Development Team
What are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity? 1. By facilitating Development Team decisions 2. By removing impediments that hinder the Development Team 3. By starting and ending the meetings at the proper time 4. By keeping high value features high in the Product Backlog
1. Broken builds are detected quickly 2. The software is generally kept in a buildable state 3. Know immediately how the check-in affected the build
What are three advantages of Continuous Integration? 1. Broken builds are detected quickly. 2. Readability of code is improved. 3. The software is generally kept in a buildable state. 4. Know immediately how a check-in affected the build.
1. The Development Team should have a set of guiding architecture principles that every Development Team member understands and follows when writing code. 2. The Development Team plans some time each Sprint to discuss the architecture needed for the features planned in that Sprint.
What are two (2) ways a Development Team can ensure a good application architecture? 1. The Development Team plans a Sprint 0 at the beginning of a project with the objective of developing an architecture model used during the following Sprints. 2. A Development Team doesn't need an architecture model in Scrum and should focus on adding functionality. The architecture will come into place without fail as the Development Team adds functionality. 3. The Development Team should have a set of guiding architecture principles that every Development Team member understands and follows when writing code. 4. The Development Team should assign someone to the role of software architect whose job it is to make sure a consistent architecture is developed. 5. The Development Team plans some time each Sprint to discuss the architecture needed for the features planned in that Sprint.
1. Automation improves the quality of software by making builds less error-prone. 2. To get feedback on changes to the code early and often.
What are two reasons to automate the software build process? 1. Code reviews are much faster if you automate your build. 2. Automation improves the quality of software by making builds less error-prone. 3. To get feedback on changes to the code early and often. 4. You can't run automated tests without an automated build.
Code being exercised by tests
What does Code Coverage show? 1. Code being exercised by tests 2. The quality of unit tests being written 3. The absence of defects in code 4. The ratio of number of tests to lines of code in the system being tested 5. When a feature is done
The process is understandable by all stakeholders.
What does Scrum mean by Transparency?
A technical requirement that must be satisfied.
What does a test written with Test Driven Development represent? 1. A bug that will be uncovered. 2. A technical requirement that must be satisfied. 3. Something that completes the test coverage of a system. 4. An assignment from the lead quality engineer.
The event can take no more than a maximum amount of time.
What does it mean to say that an event has a time-box? 1. The event must happen at a set time. 2. The event must happen by a given time. 3. The event must take at least a minimum amount of time. 4. The event can take no more than a maximum amount of time.
There is no such thing as Sprint 0
What happens during Sprint 0.
The Product Owner typically accepts it.
What happens if part of the work in a cancelled Sprint is potentially releasable.
The Sprint ends on time and the team learns what is possible to accomplish in that sprint length.
What happens if the Development Team cannot complete its work by the end of the Sprint?
product owner should cancel the sprint
What happens if the customer no longer wants the feature that the Sprint Goal intended to meet? 1. executive stakeholders should determine if the Sprint should continue 2. development team should determine if there is value in the Sprint 3. product owner should cancel the sprint 4. scrum master should cancel the sprint
they expand to include stringent criteria for higher quality.
What happens to the Definitions of "done" as Scrum Teams mature?
The practice of writing unit tests prior writing the implementation code
What is Test Driven Development? 1. The practice of writing unit tests prior writing the implementation code 2. Appointing the QA Tester as the Lead Developer 3. The process of motivating Testers 4. Integrating Testers and Developers
a test that isolates and verifies individual units of source code.
What is a unit test?
all of the above
What is an effective way to prevent technical debt? 1. code reviews 2. static code analysis 3. refactor technical debt away 4. improve your definition of done 5. coding standards 6. all of the above
The degree to which the system under test has been exercised by tests
What is code coverage? 1. The number of developers that understand how the code works. 2. The percent of code in version control included in a build. 3. The degree to which the system under test has been exercised by tests. 4. An insurance policy that covers the code for defects
Two developers writing code together, providing constant peer review.
What is pair programming?
a term representing the eventual consequences of poor technical choices.
What is technical debt? 1.The money an organization owes to tool and hardware vendors. 2. term representing the eventual consequences of poor technical choices. 3. Code that has not been commented or documented. 4. The average time or money a Scrum Team spends per Sprint on bug fixes.
Designing tests before satisfying them.
What is test first development?
To make the code more readable.
What is the benefit of establishing naming standards for code?
He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum.
What is the main reason for the Scrum Master to be at the Daily Scrum? 1. To make sure every team member answers the three questions. 2. He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum. 3. To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down. 4. To gather status and progress information to report to management.
3 to 9
What is the recommended size for a Development Team (within the Scrum Team)? 1. Minimal 7 2. 3 to 9 3. 7 plus or minus 2 4. 9
Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to cause organizational change that fosters empiricism, self-organization, bottom-up intelligence, and intelligent release of software.
What is the role of Management in Scrum? 1. Continually monitor staffing levels of the Development Team. 2. Monitor the Development Team's productivity. 3. Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to cause organizational change that fosters empiricism, self-organization, bottom-up intelligence, and intelligent release of software. 4. Identify and remove people that aren't working hard enough.
To improve readability and maintainability
What is the value of refactoring code? 1. To have all code in a single file for easy printing and code reviews. 2. To improve readability and maintainability. 3. To keep the code moving. 4. To make the software faster at runtime.
improvements that will be implemented for the next Sprint
What should the Scrum Team have identified by the end of the Sprint Retrospective.
The person who broke the build.
When a Continuous Integration build fails, who ideally ensures the build is repaired? 1. The person who broke the build 2. The person assigned to the configuration management role within the team 3. The tester responsible for validating builds 4. The next person who needs the build to complete successfully
From the beginning and throughout all Sprints.
When are testers and quality experts ideally included in a project? 1. From the beginning and throughout all Sprints 2. After Sprint Review 3. When the product is feature complete 4. After developer hand off
1. Mid Sprint 2. Every Sprint 3. Every Day 4. Multiple times per day
When could a release to Production occur if a Scrum Team produced a Done increment multiple time each day? 1. Mid Sprint 2. Every Sprint 3. Every Day 4. Multiple times per day
Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one may be done by an individual
When do Development Team members become the exclusive owner of a Sprint Backlog item? 1. At the Sprint planning meeting. 2. Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one may be done by an individual development team member. 3. Whenever a team member can accommodate more work. 4. During the Daily Scrum.
Anytime during the Sprint.
When does the Development Team participate in Product Backlog refinement? 1. Anytime during the Sprint. 2. Only during refinement meetings planned by the Product Owner. 3. As Part 1 of the Sprint Planning meeting. 4. Never. It is the sole responsibility of the Product Owner to refine the Product Backlog.
Immediately after the conclusion of the previous Sprint.
When does the next Sprint begin? 1. Next Monday. 2. Immediately following the next Sprint Planning. 3. When the Product Owner is ready. 4. Immediately after the conclusion of the previous Sprint.
removed
When elements of the Sprint Backlog plan are no longer deemed necessary, they should be ______________ by the development team.
When the time-box expires.
When is a Sprint over? 1. When all Product Backlog items meet their definition of done. 2. When the Product Owner says it is done. 3. When all the tasks are completed 4.When the time-box expires.
All Development Teams must have a definition of "done" that makes their combined work potentially releasable.
When many Development Teams are working on a single product, what best describes the definition of "done?" 1. Each Development Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint. 2. Each Development Team uses its own but must make their definition clear to all other Teams so the differences are known. 3. All Development Teams must have a definition of "done" that makes their combined work potentially releasable. 4. It depends.
When the Sprint Goal becomes obsolete.
When might a Sprint be abnormally terminated? 1. When it becomes clear that not everything will be finished by the end of the Sprint. 2. When the Development Team feels that the work is too hard. 3. When the sales department has an important new opportunity. 4. When the Sprint Goal becomes obsolete.
False, single source of truth is what the Product backlog is for.
When multiple teams work together on the same product, each team should maintain a separate Product Backlog. 1. True 2. False
1.It promotes good design and separation of concerns. 2. It improves quality and reduces bugs. 3. It causes you to construct a test harness that can be automated. 4. It speeds the overall development process.
Which are the benefits of Test Driven Development? 1.It promotes good design and separation of concerns. 2. It improves quality and reduces bugs. 3. It causes you to construct a test harness that can be automated. 4. It speeds the overall development process.
1. Generic Titles 2. Vague Statements 3. Assigning blame
Which are three attributes of a BAD bug report? 1. Generic titles. 2. One bug per report. 3. Simple and repeatable reproduction steps. 4. Vague statements or untested assumptions. 5. Assigning blame.
1. Have the development team establish a definition of done that is actually possible 2. coach the development team to improve its skills, tools and infrastructure over time and adjust the definition of done accordingly.
Which are two things that are appropriate for a scrum master to do if the development team doesn't have the engineering tools and infrastructure to completely finish each selected product backlog item? 1. have the development team establish a definition of done that is actually possible 2. coach the development team to improve its skills, tools and infrastructure over time and adjust the definition of done accordingly. 3. refocus the current sprint on establishing the development team's infrastructure instead of delivering an increment. 4. declare the development team not ready for scrum 5. encourage the product owner to accept partially done increments until the situation improves
Acceptance Test Driven Development
Which describes the practice of expressing requirements as acceptance tests? 1. Regression Testing 2. Acceptance Test Driven Development 3. Quality Oriented Requirements Definition. 4. Object Driven Requirements Definition.
Whenever a new or changed code is checked into version control.
Which is the best answer for how often the build should be executed? 1. Once per day. 2. Whenever new or changed code is checked into version control. 3. Whenever the QA group becomes uncertain that the system works. 4. As often as possible, and certainly prior to the end of the Sprint.
1. Development Team 2. Product Owner 3. Scrum Master
Which of the below are roles on a Scrum Team? 1. Development Team 2. Users 3. Customers 4. Product Owner 5. Scrum Master
1. it involves minimum planning and maximum test execution 2. it is unscripted testing
Which of the following are 2 attributes of exploratory testing : 1. it involves minimum planning and maximum test execution 2. it is often the sole testing technique 3. it is typically automated 4. it is unscripted testing
Testing existing software before developing any new software
Which of the following is NOT an attribute of Test-Driven Development? 1. software development technique based on automated test 2. incremental and emergent approach to software design 3. a predictable way to develop working, clean code 4. Testing existing software before developing any new software
Charactersitics
Which of the following is NOT part of the Scrum framework? 1. characteristics 2. events 3. artifacts 4. roles
1. There are no individual tester roles in scrum 2.everyone on the team is responsible for quality
Which of the following statements are true regarding the responsibilities of Scrum Testers on a Development Team? 1. preventing and finding defects 2. performing acceptance testing 3. there are no individual tester roles in scrum 4. updating the defect log 5. everyone on the team is responsible for quality
None of the Above
Which of the following tools or techniques are mandatory with Scrum? 1. Automated Builds 2. Pair Programming 3. Test Driven Development 4. Unit Testing 5. Collective Code Ownership 6. Burndown Chart 7. None of the Above
a way to ensure automated testing occurs
Which of these is NOT a benefit of a well written definition of "done"? 1. a way to ensure automated testing occurs 2. a shippable increment is created by the end of the Sprint 3. a way to express the coding standards to address and proven technical debt 4. clear understanding of the quality expectations of the team
a framework within which complex products in environments are developed
Which statement best describes Scrum? 1. A complete methodology that defines how to develop software. 2. A cookbook that defines best practices for software development. 3. A framework within which complex products in complex environments are developed. 4. A defined and predictive process that conforms to the principles of Scientific Management.
Optimizing the value of the work the Development Team does.
Which statement best describes a Product Owner's responsibility? 1. Optimizing the value of the work the Development Team does. 2. Directing the Development Team. 3. Managing the project and ensuring that the work meets the commitments to the stakeholders. 4. Keeping stakeholders at bay.
The team has all competencies needed to accomplish the work
Which statement best describes a cross-functional team? Pick 1 1. The team has a good mix of skills 2. All members of the team have all the skills required to create the Product 3. The team has all competencies needed to accomplish the work
It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.
Which statement best describes the Sprint Review? 1. It is a mechanism to control the Development Team's activities during a Sprint. 2. It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next. 3. It is a demo at the end of the Sprint for everyone in the organization to check on the work done.
1. Deliver an increment of releasable software. 2. Develop and deliver at least one piece of functionality.
Which two (2) things does the Development Team do during the first Sprint? 1. Deliver an increment of releasable software. 2. Determine the complete architecture and infrastructure for the product. 3. Develop and deliver at least one piece of functionality. 4. Develop a plan for the rest of the release. 5. Create the complete Product Backlog to be developed in subsequent Sprints.
Fix the bug if it is critical or easily fixed. Otherwise, put the new bug into the Product Backlog to be prioritized and fixed in an upcoming Sprint.
While changing software, you find a bug in a previously delivered piece of functionality. What should you do? 1. Fix the bug if it is critical or easily fixed. Otherwise, put the new bug into the Product Backlog to be prioritized and fixed in an upcoming Sprint. 2. Stub out the code that caused the bug so it no longer occurs. 3. Revise the tests so that the bug no longer appears on the bug report. 4. Fix the bug.
1. Scrum Team 2. Key Stakeholders 3. Product Owner
Who attends the Sprint Review?
1. The Development Team, with support from the Product Owner who is still accountable for it 2. The Product Owner
Who can do the work to ensure the Product Backlog is refined to a state that it is useful? Pick 2 1. The Product Owner 2. The Business Analyst 3. Stakeholders 4. The Development Team, with support from the Product Owner who is still accountable for it
The Product Owner
Who can tell the Development Team what to work on 1. The Scrum Master 2. The COO, CEO and CTO 3. The Product Owner 4. The Project Manager
Scrum Team
Who decides when/how Product Backlog refinement will occur?
The Development Team
Who determines the structure of the daily scrum?
The Product Owner
Who has the final say on the order of the Product Backlog? 1. The Stakeholders 2. The Development Team 3. The Scrum Master 4. The Product Owner 5. The CEO
1. The Scrum Master 2. The Product Owner 3. The Development Team
Who is on the Scrum Team? 1. The Scrum Master 2. The Product Owner 3. The Development Team 4. Project Manager 5. None of the above
The Development Team
Who is required to attend the Daily Scrum? 1. The Development Team. 2. The Scrum team. 3. The Development Team and Scrum Master. 4. The Development Team and Product Owner. 5. The Scrum Master and Product Owner.
The Development Team
Who is responsible for managing the progress of work during a Sprint? 1. The Development Team 2. The Scrum Master 3. The Product Owner 4. The most junior member of the Team
Development Team
Who is responsible for monitoring the progress of work during a Sprint? Pick 1 1. Product Owner 2. Project Manager 3. Scrum Master 4. Development Team
The Development Team
Who is responsible for testing in Scrum? 1. The Product Owner 2. The Development Team 3. Stakeholders 4. The Scrum Master
The Development Team
Who is responsible for the system architecture of a product being developed using Scrum? 1. The corporate architect. 2. The software architect. 3. The Development Team. 4. The architect chosen by the Development Team.
The Development Team
Who manages the Sprint Backlog? 1. The Product Owner 2. The Development Team 3. The Scrum Master 4. The Scrum Team
The Development Team
Who must be present at the Daily Scrum meeting? 1. The entire Scrum Team 2. The Scrum Master and the Development Team 3. The Development Team 4. No one is required, anyone who wishes to attend is welcome 5. Anyone who wants to attend
Developers
Who performs unit testing?
Product Owner
Who represents the Stakeholders?
The Development Team and the Product Owner
Who should decide who will be the Scrum Master for a new Scrum Team? 1. Stakeholders 2. The Product Owner 3. The Development Team 4. The Development Team and the Product Owner
The Product Owner
Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly? 1. The Product Owner 2. The Development Team 3. The Scrum Master 4. The Project Manager
so that any one item can reasonably be "done" for the Sprint time-box.
Why are PBIs for the upcoming Sprint refined?
They provide rapid assurance that defects and configuration management issues have not been introduced.
Why are automated builds so important? 1. They are part of your "done" criteria. 2. They provide rapid assurance that defects and configuration management issues have not been introduced. 3. Without them you can't tell if your code works. 4. You are unable to check-in code without one
It provides rapid assurance that defects and configuration management issues have not been introduced.
Why is automation important?
The consistency reduces complexity.
Why is the Daily Scrum held at the same time and same place? 1. The place can be named. 2. The consistency reduces complexity. 3. The Product Owner demands it. 4. Rooms are hard to book and this lets it be booked in advance.
Scrum Master
Will help the development Team to create high-value products.
The full history of retrospective plans and lessons learned.
You are on a Scrum Team that is enhancing an existing product. Which is the LEAST useful piece of documentation you want to have at your disposal? 1. Acceptance tests. 2. Detailed designs. 3. Well-structured and named code. 4. The full history of retrospective plans and lessons learned.
Scrum Master
_________ ensures that the Sprint Retrospective takes place and is understood.
High
___________ class coupling indicates a design that is difficult to reuse and maintain because of its many inter dependencies on other types.
Development Team
___________ is responsible for all estimates for the PBIs.
Scrum Master
___________ teaches the team to keep the Sprint Retrospective within the time-box.
Product Backlog
____________ is dynamic, changing constantly with the product to be appropriate, competitive, and useful.
Scrum Master
____________ must ensure that the Sprint Retrospective remains positive and productive, and that attendants understand the purpose.
Development Team
____________ tracks the velocity for use within the Scrum Team.
Code Coverage
_____________ does not ensure that the most important or highest risk areas of the code are being excised by tests.
Sprint Review
_____________ held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed.
Scrum Master
_____________ helps everyone in the team apply the most appropriate practices in the absence of complete transparency.
Scrum Master
_____________ is responsible for increasing transparency in artifacts by work that involves learning, convincing, and change.
Development Team
_____________ manages the Sprint Backlog
Product Owner; Development Team
_____________ may influence PBI estimates, but it is ultimately up to _______________.
Scrum Master
_____________ must work with all involved parties to understand if artifacts are completely transparent.
Scrum's artifacts
_____________ represent work or value to provide transparency and opportunities for inspection/adaption.
Product Owner
_____________ tracks total work remaining in at least every Sprint Review.
User Stories
_____________ typically have a format like : As a <User / type of user> I want to <Some achievable goal / target> To achieve <some result or reason of doing the thing>
Sprint
______________ a time-boxed event of a month or less during which a "done," usable, and potentially releasable product increment is created.
Emergence
______________ in the Sprint Backlog occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal.
Product Owner
______________ is responsible for the Product Backlog, it's content, availability, and ordering.
Increment; increments
______________ is the sum of all the PBIs completed during a Sprint and the value of all _____________ of all previous Sprints.
Sprint Retrospective
______________ meeting should create a plan for implementing improvements to the way the Scrum Team does its work.
Sprint Retrospective
_______________ meeting should identify and order the major items that went well and potential improvements to the way the Scrum Team does work.
Product Backlog
________________ an ordered list of everything that is known to be needed in the product.
Product Backlog
________________ lists all features, functions, requirements, enhancements, and fixes that constitute changes to the product for future release.
Scrum Master
_________________ can detect lack of complete transparency by inspecting artifacts, sensing patters, listening closely to what is said, and detecting differences between expected and real results.
Definition of "done"
__________________ used by the Scrum Team to assess when work is complete on the product Increment.
Sprint Retrospective
____________________ meeting must inspect how the last Sprint went with regards to people, relationships, process, and tools.
Code Coverage
______________________ could create incentives to write tests that simply increase coverage, rather than tests that find bus without increasing coverage.
Code Coverage
______________________ does not necessarily provide functional coverage.
Burn-Up Chart
a chart showing the evolution of remaining effort against time. Optional, increases transparency.
Smoke Testing
a non-exhaustive set of tests that aim at ensuring that the most important functions work.
Scrum Board
a physical board to visualize info for and by the Scrum Team, often used to manage Sprint Backlog.
Increment
a piece of working software that adds to previously created Increments, where the sum of all Increments - as a whole- form a product.
Engineering Standards
a shared set of development and technology standards that a Development Team applies to create releasable Increments of software.
Ready
a shared understanding by the Product Owner and the Development Team regarding the preferred level of description of PBIs introduced at Sprint Planning.
Definition of "Done"
a shared understanding of expectations that software must live up to in order to be releasable into production.
Continuous Deployment
a software delivery practice in which the release process is fully automated in order to have changes promoted to the production environment. No human intervention.
Continuous Delivery
a software delivery practice similar to Continuous Deployment except a human action is required to promote changes into a subsequent environment along the pipeline.
Collective Code Ownership
a software development principle popularized by Extreme Programming holding that all contributors to a given code base are jointly responsible for the code in its entirety.
Sprint
a time boxed event of 30 days or less
Product Backlog Refinement
adding detail, estimates, and order to items in the Product Backlog.
Extreme Programming (XP)
agile software development framework with an extreme focus on programming and taking engineering practice to an extreme in order to create and release high quality code.
Behavior Driven Development (BDD)
agile software development practice adding to TDD the description of the desired functional behavior.
Specification by Example
agile software development practice based on TDD and ATDD
1. Continuous Integration (CI) 2. Pair Programming 3. Refactoring 4. User Story 5. Collective Code Ownership
agile software development practice popularized by Extreme Programming
User Story
agile software development practice to express requirements from an end user perspective, emphasizing verbal communication.
Sprint Retrospective
an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
Product Backlog
an ordered list of the work to be done in order to create, maintain, and sustain a product Managed by the Product Owner.
Developer
any member of the Development Team regardless of technical, functional, or other specialty.
Increment
body of inspectable, done work that supports empiricism at the end of a Sprint.
Cross-functional
characteristic of a team holding that all the skills required to successfully produce a releasable increment in a sprint are available within the team.
Refactoring
code is adjusted within the code base without impacting the external, functional behavior of that code.
Clean Code
code that is expressed well, formatted correctly, and organized for later coders to understand.
Branching
creating a logical or physical copy of code within a version control system so that this copy might be changed in isolation.
Increment
delivery of product in 'done' segment in order to ensure a potentially useful version of the product always available.
Cohesion
describes how related the functions within a single module are. High >
Agile development
feature-driven development with the core values for all methodologies under its umbrella.
respect
for the product owner to succeed the entire organization must ______________ his/her decisions.
Sprint Backlog
forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver the functionality into a "done" increment.
Scrum
framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
Scrum
framework within which you can employ various process and techniques.
Increment
fully functional piece of working software, that adds a to previously created increments.
Application Lifecycle Management (ALM)
holistic view on the management of software applications and systems, accounting for all stages of the existence of a software product.
Transparency
increases the value and control risk of the decisions made to optimize value in Scrum.
Velocity
indication of the amount of Product Backlog turned into an increment of product during a Sprint.
Integration Testing
individual units are combined and tested as a group in order to expose faults in the interaction of units.
Scrum
initially developed for managing and developing products.
Empiricism
knowledge comes from experience, decisions are based on what is known.
Unit Test
low-level test focusing on small parts of a software system that can be executed fast and in isolation.
Continuous Integration (CI)
newly checked-in code is built, integrated, and tested frequently, generally multiple times a day.
User Story
often used to express functional items on the Product Backlog.
DevOps
organizational concept that bridges the gap between development and operations.
Sprint Backlog
overview of the development work to realize a Sprint's goal. Typically a forecast of functionality, and work needed to deliver it.
Stakeholder
person external to the Scrum Team with a specific interest in and knowledge of a product that is required for incremental discovery.
Sprint Backlog
plan for delivering the product increment to realize the Sprint Goal
DRY (Don't repeat yourself)
principle to avoid repetition of the same information in one system, preventing the same code from being produced multiple times on code base.
Regression Testing
process of testing changes to computer programs to make sure that the older programming still works with the new changes.
User Stories
requirements or feature which has to be implemented.
The Development Team
self-organizing role within the Scrum Team accountable for managing, organizing, and doing all work required to create a releasable increment of product every sprint.
Scrum Team
self-organizing team consisting of the PO, Dev Team, and Scrum Master.
Sprint Backlog
set of the Product Backlog items selected for the Sprint.
Sprint Goal
short expression of the purpose of a Sprint, often a business problem addressed.
Product Backlog
single source of truth for the requirements and changes to the product.
Clean Code
software code that is expressed well, formatted correctly, and organized for later coders to understand. Clarity> cleverness.
Feature Toggle
software development practice that allows dynamically turning functionality on and off.
Functional Testing
software is tested to ensure that it conforms with all specified functional requirements.
Acceptance Test Driven Development (ATDD)
test-first software development practice in which acceptance criteria for new functionality are created as automated tests. The failing tests are constructed to pass as development proceeds and acceptance criteria are met.
Test-Driven Development (TDD)
test-first software development practice in which test cases are defined and created first, and executable code is created to make the test pass.
Product Backlog Refinement
the activity in a Sprint through which the Product Owner and the Development Team add granularity to the Product Backlog
Scrum Guide
the definition of Scrum, written and provided by Ken Scwaber and Jeff Sutherland, co-creators of Scrum.
Self-Organization
the management principle that teams autonomously organize their work. This happens within boundaries and against given goals.
Empiricism
the process control type in which only the past is accepted as certain and in which decisions are based on observation, experience, and experimentation.
Performance Testing
the process of determining the speed or effectiveness of a computer, network, software program or device.
Product Owner
the product backlog is managed by :
Product Owner
the 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 Development Team(s).
Scrum Master
the role within a Scrum Team accountable for guiding, coaching, teaching and assisting Scrum Team and its environments in properly understanding Scrum.
Development Team
the role within the Scrum Team accountable for managing, organizing, and doing all development work required to create a releasable Increment of product every Sprint.
Forecast (of functionality)
the selection of items form the Product Backlog a Development Team deems feasible for implementation in a Sprint.
Sprint Planning
time-boxed event of 8 hours or less to start a Sprint.
Technical Debt
unpredictable overhead of maintaining the product, often caused by less than ideal design decisions, contributing to the total cost of ownership.
Epics
user stories which are not defined and are kept for future sprints, not yet detailed.
True
(T/F) Can the daily scrum structure be changed.
True
(T/F) It is important that everyone understands what "done" means when used to describe an Increment or PBI.
True
(T/F) Modeling may be useful to increase shared understanding
True
(T/F) Most features begin as epics then get broken down into stories that can be implemented.
True
(T/F) New definitions of "done" may uncover additional work in previously "done" increments.
False, multiple scrum teams often work together on the same product.
(T/F) Only one scrum team can work on a product.
False
(T/F) Only technical writers can create documentation during a Sprint.
False, everyone contributes to the documentation effort during a sprint.
(T/F) Only technical writers can create documentation during a sprint.
False, only the product owner is responsible for product backlog management, but can assign sub-tasks to the development team.
(T/F) Only the Product owner can do Product Backlog Management.
True
(T/F) Refactoring is a key way of preventing technical debt.
False, they tend to be 4 hours for a month long sprint, but can be shorter with shorter sprints.
(T/F) Sprint Review meetings must be 4 hours long at the end of the sprint.
True
(T/F) Sprints are done consecutively, without intermediate gaps.
Architecture Spike
A small development activity to learn about technical elements of a proposed solution.
Product Backlog Management
Clearly expressing Product Backlog items is part of ____________.
Cyclomatic Complexity
Code complexity measure based on the # of independent logical branches through a code base.
Cross-Functional Team
Development team having all of the skills necessary to create a product increment makes them a _____________________.
Product Owner
In the Sprint Review______________ explains what Product Backlog items have been "done" or not "done."
Scrum Master
Must remove impediments to the Development Team's progress.
Transparency
Requires that those performing the work and those inspecting it share a common definition of "done."
Turn the Product Backlog items it selects into an increment of potentially releasable product functionality.
The Development Team should have all the skills needed to: 1. Complete the project as estimated when the date and cost are committed to the Product Owner. 2. Do all of the development work, except for specialized testing that requires additional tools and environments. 3. Turn the Product Backlog items it selects into an increment of potentially releasable product functionality.
Whatever is deemed most appropriate by the Product Owner.
The Product Backlog is ordered by: 1.Size, where small items are at the top and large items are at the bottom. 2. Risk, where safer items are at the top, and riskier items are at the bottom 3. Least valuable items at the top to most valuable at the bottom. 4. Items are randomly arranged. 5. Whatever is deemed most appropriate by the Product Owner.
Sprint Goal ; Development Team
The ____________ gives the __________ flexibility regarding the functionality implemented within the Sprint.
Emergence
The process of the coming into existence or prominence of new facts or new knowledge of a fact or knowledge of a fact becoming visible unexpectedly.
True
The purpose of a Sprint is to produce a done increment of working product. 1. True 2. False
1. Product Backlog 2. Projected Development Capacity 3. Past Development Performance
The three Sprint Planning meeting inputs are :
Increment
Typically the result of a sprint.
The Development Team
Velocity is tracked by ______________ for use within the Scrum Team.
1. Analysis 2. Design 3. Decomposition
What activities must occur in order to refine product backlog items?
1. the software is generally kept in a buildable state 2. know immediately how a check-in affected the build 3. broken builds are detected quickly
What are the benefits of Continous Integration? 1. Readability is improved 2. the software is generally kept in a buildable state 3. know immediately how a check-in affected the build 4. broken builds are detected quickly
Testing existing software before developing any new software.
What is NOT Test-Driven Development? 1. A software development technique based on automated tests. 2. An incremental and emergent approach to software design. 3. A predictable way to develop working, clean code. 4. Testing existing software before developing any new software.
Testing existing software before developing any new software.
What is NOT Test-Driven Development? 1. software development technique based on automated tests. 2. An incremental and emergent approach to software design. 3. A predictable way to develop working, clean code. 4. Testing existing software before developing any new software.
To defer a story until a later Sprint while still showing progress to the Product Owner.
What is NOT a reason to perform a Spike? 1. to perform basic research to familiarize the team with anew technology or domain 2. to analyze the expected behavior of a large story so the team can splt the story into estimable pieces 3. to defer a story until a later Sprint while still showing progress to the Product Owner. 4. to do some prototyping to gain confidence in a technological approach
Scrum Development Teams with excellent technical practices will likely be more sucessful.
What relationship does Scrum have to technical practices?
Every Day of the Sprint.
When/how often is the Daily Scrum held?
1. Lines of Code 2. Cycle time per feature
Which of the following are NOT metrics of code quality? 1. Class Coupling 2. Depth of Inheritance 3. Cyclomatic Complexity 4. Lines of Code 5. Cycle time per feature
A software development practice where members of a development team integrate and verify their work frequently, often multiple times each day, to detect integration errors as quickly as possible.
Which of the following best describes Continuous Integration? 1. A software development practice where members of a development team integrate and verify their work frequently, often multiple times each day, to detect integration errors as quickly as possible. 2. A software development practice where members of a development team all work on the same computer to ensure a common code base. 3. A software development practice that continuously integrates feedback from users into software design. 4. A software development practice used by Integration Teams to create best practice branching and merging strategies.
High Coupling and Low Cohesion
Which of the following is NOT a clean code principles/best practices? 1. common closure principal 2. single responsibility principal 3. high coupling and low cohesion 4. decouple construction form runtime
1. Unit 2. Integration 3. Smoke 4. Functional 5. Performance
Which types of tests can be automated? 1. Unit 2. Integration 3. Smoke 4. Exploratory 5. Functional 6. Performance
1. The Development Team 2. The Product Owner
Who should be present during Product Backlog refinement?
The Development Team
Who writes tests in a Scrum Team? 1. The Development Team 2. The Scrum Master 3. QA specialists 4. Coders
Sprint Goal
______________ is an objective that will be met within the Sprint through the implementation of the Product Backlog.
Scrum
a framework to support teams in complex product development.
Velocity
indication of the average amount of Product Backlog turned into an Increment of the product during a Sprint by the Scrum team.
DevOps
the underlying idea is that developers are aware of and consider implication on operations in daily work and visa versa.
Artifacts
this is defined by Scrum and designed to maximize transparency of key information so that everybody has the same understanding.
Sprint
time-boxed event of 30 days or less that serves as a container for the other Scrum events and activities.
Sprint Review
time-boxed event of 4 hours, or less, to conclude the development work of a Sprint.
1. Burn- Up Chart 2. Burn-Down Chart 3. Cumulative Flows
(3 blanks) are protective practices used to forecast progress.
False, only the Development Team can change the Spring Backlog during a Sprint.
(T/F) Any Scrum Team member may change the Sprint Backlog during a sprint if needed.
True
(T/F) Automated tests should be run every time there is an automated build.
True
(T/F) Class coupling measures each class only once for this metric no matter how many times it gets used.
True
(T/F) During the Sprint Review the Product Backlog may be adjusted to meet new opportunities.
True
(T/F) Even if the PO does not decide to release the increment it needs to be "done" at the end of a Sprint.
True
(T/F) External management has no active role in the actual product development through Scrum, but can help guide the overall direction of the organization.
False, this can be done anytime, however, it provides a formal opportunity to focus on this inspection/adaption.
(T/F) Improvements can only be implemented at the Sprint Retrospective.
True
(T/F) In regression testing before a new version of software is released, the old test cases are run against the new version to make sure that old capabilities still work.
False, this is an ongoing process between the PO and Development Team and can be updated at any time at the PO's descretion.
(T/F) Product Backlog Refinement is done once a Sprint.
False
(T/F) Programmers and testers should not be included in refining PBIs
True
(T/F) Smoke testing covers most major functions of software, but none in depth.
True
(T/F) Stakeholders are actively engaged with the Scrum Team at the Sprint Review.
False, it is held at the same time/place every day to reduce complexity.
(T/F) The Daily Scrum can be held in any time place so long as it happens every day.
False, some will also use discussion based daily scrums.
(T/F) The Daily Scrum can only be question based.
True
(T/F) The Development Team may invite other people to attend the Sprint Planning meeting to provide technical or domain advice.
False, they often do this immediately after the daily scrum.
(T/F) The Development Team shouldn't meet after the Daily Scrum for more discussions on how to adapt, or replan, the rest of the Sprint.
True
(T/F) The Product Backlog evolves as the product/environment evolve.
True
(T/F) The Scrum Master participates a peer team member in the Sprint Retrospective as is he/she is accountable for the Scrum process.
True
(T/F) The Sprint Backlog is modified throughout the sprint by the Development Team.
False, they must be usable so that the PO can make this choice.
(T/F) The increment at the end of each sprint only has to be usable if the Product Owner has decided to release it.
False, this becomes larger and more exhaustive with the marketplace feedback.
(T/F) The product backlog shrinks as it gains value and is used.
False, this is never complete.
(T/F) The product owner gets to determine when the product backlog is complete.
False, Unit testing is performed before integration testing as it is the first level of testing.
(T/F) Unit testing occurs after integration testing.
True
(T/F)The Definition of "done" helps guide the Development Team in knowing how many PBIs it can select during Sprint Planning.
Scrum
- Lightweight - Simple to Understand - Difficult to master
Scrum Values
1. Commitment 2. Courage 3. Focus 4. Openness 5. Respect
Daily Scrum
1. Improves Communication 2. Eliminates other meetings 3. Identify impediments to Development for removal 4. Highlight and promote quick decision-making 5. Improve the Development Team's knowledge
Daily Scrum
15 minute time-boxed event for the Development Team.
1. Transparency 2. Inspection 3. Adaption
3 Pillars of Empiricism
Burn-Down Chart
A chart showing the evolution of remaining effort against time. This is optional and makes progress more transparent.
Daily Scrum
A key inspect and adapt meeting.
Class Coupling
A measure of how many classes a single class uses. High is bad, low is good.
Sprint Backlog
A plan with enough detail for a Sprint that changes in progress will be understood in the Daily Scrum.
When should a process adjustment occur?
After it is deemed necessary as soon as possible in order to avoid deviation.
1. Individuals and their interactions 2. Delivering working software 3. Customer collaboration 4. Responding to change
Agile development four core values :
Sprint Review
An informal meeting, not a status meeting.
Sprint Goal
An objective set for the Sprint that can be met through the implementation of the Product Backlog.
All answers apply.
An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done? 1. Without a new vocabulary as a reminder of the change, very little change may actually happen. 2. The organization may not understand what has changed with Scrum and the benefits of Scrum may be lost. 3. Management may feel less anxious. 4. All answers apply.
Sprint Goal
Any coherence that causes the Development Team to work together rather than on separate initiatives.
1. Write Tests 2.See the Test Fail 3. Develop just enough code to pass the test 4. refactor code
Arrange the following steps in ascending order while implementing TDD cycle : 1. See the test fail 2. write tests 3. refactor code 4. develop just enough code to see the test fail
Development Team
As new work is required, ________________ adds it the Sprint Backlog.
Estimated remaining work should be updated.
As work is completed in a Sprint what should happen for the Sprint Backlog?
priority process improvement
At least one _________________ identified in the Sprint Retrospective is added to the Sprint Backlog.
As a development team, specify a shared definition of "done"
At sprint planning, the development team has NO clear standard to meet for releasable software. what should the development team do? 1. ask the scrum master what they should do 2. create a unique completion checklist for each item in the sprint 3. as a development team, specify a shared definition of "done" 4. ask the product owner to specify a definition of "done"
24 hours
At the Daily Scrum the Development Team plans the work for the next _________.
True
(T/F) A new Sprint starts immediately at the conclusion of the previous Sprint.
True
(T/F) During the Sprint no changes that could endanger the Spring goal are made.
False, quality goals do not decrease during the Sprint.
(T/F) During the Sprint the Development team may need to produce lower quality to meet the goal.
True
(T/F) During the Sprint the scope may be clarified/re-negotiated between the Product Owner and the Development team as more is learned.
True
(T/F) Events in a sprint may end when the purpose of the even has been achieved.
False, only the Development Team can assess what it can accomplish over the upcoming Sprint.
(T/F) The Product Owner gets to determine what items from the Product Backlog will be accomplish?
False, he/she should ensure the the Product Backlog is visible, transparent, and CLEAR TO ALL so that the Scrum Team can see what to work on next. The Product Owner is ultimately responsible for the Product Backlog content.
(T/F) The Product Owner should ensure that the Product Backlog is visible, transparent, and editable by all so that the Scrum Team knows what to work on next.
False, the scrum master can also work with those outside the Scrum Team to help teach what interactions are or aren't helpful.
(T/F) The Scrum Master works only with individuals internal to the Scrum project.
True
(T/F) The entire Scrum Team must collaborate to understand the work of the Sprint.
False, sprints have consistent duration during development efforts.
(T/F) The length of a sprint can be determined during development based on the the amount of work in that sprint.
True
(T/F) The scrum master is responsible for ensuring that the product backlog management by prodtuct owner will optimize the value of the work the Development team performs.
False, development teams are self-organizing, therefore no one can tell them how to do this.
(T/F) While development teams are expected to self-organize they are told by the Product Owner how to turn Increments from the Product Backlog into potentially releasable functionality.
Scrum Team
1. Product Owner 2. Development Team 3. Scrum Master
Scrum
1. Research and Identify viable market. 2. Develop/Release products/enhancements. 3. Develop & sustain Cloud/operational environments 4. Sustain/Renew Products
Four Events of Inspection & Adaption
1. Sprint Planning 2. Daily Scrum 3. Sprint Review 4. Sprint Retrospective
Three Pillars of Empirical Process Control
1. Transparency 2. Inspection 3. Adaption
The Scrum Master is responsible for ensuring that the product backlog management does this.
1. Visible 2. Transparent 3. Clear to all 4. Shows the next item the Scrum team should work on
Obsolete
A Sprint may be cancelled if the Sprint Goal becomes __________.
Self-Organized
Development teams decide how to turn the Product Backlog into an increment of potentially releasable functionality.
Scrum
Framework for developing, delivering, and sustaining complex products.
Scrum Master
Helps Stakeholders/employees understand and enact scrum and empirical product development.
Scrum Master
In charge of facilitating scrum events as requested or needed.
False, they must first address the Product Owner
In order to change the priority of an item in the product backlog any member of the scrum team may simply change it.
The Development Team as a whole
In the Development Team accountability belongs to _____________.
Empirical Process Control
Iterative, incremental approach used by scrum to optimize predictability and control risk.
Scrum Master
Leads the coaching of the organization in its Scrum adoption. b
Scrum Master
Must ensure that the Product Owner knows how to arrange the Product Backlog to maximize value.
Scrum Master
Must help the Scrum Team understand the need for clear and concise Product Backlog Items.
Scrum Master
Must understand product planning in an empirical environment.
Product Owner
Only ______________ has the authority to cancel the Sprint.
Scum Master
Plans Scrum Implementations within the organization.
Events
Present an opportunity in the Sprint for something to be inspected or adopted.
1. Iterative 2. Incremental
Scrum teams deliver products in what two ways to maximize opportunities for feedback ?
Shorter
Shorter Sprints usually result in ______________ Sprint Planning time-boxes.
Transparency
Significant aspects of the process must be defined by a common standard and visible to those responsible for the outcome.
1. What can be delivered in the Increment for this Sprint? 2. How will required work be achieved?
Sprint Planning answers what two questions?
1. Sprint Planning 2. Daily Scrums 3. Development Work 4. Sprint Review 5. Sprint Retrospective
Sprints contain and consist of what five parts?
Self-Organizing
Teams that choose how to best accomplish work, rather than having external direction.
True
The Product Owner can delegate Product Backlog Management work
True
The Product Owner is ultimately accountable for the Product Backlog Managment.
Product Backlog Management
The ____________ includes ensuring the development team understand the items in the Product Backlog.
Development Team
The _________________ approaches the "how" of getting the work done by designing the system/work needed to convert the Product Backlog into a working product Increment.
Sprint Backlog
The combination of the Product Backlog items selected for this Sprint plus the plan for delivering them is called :
Transparency
This can be created by having a common language referring to the process that is shared by the participants.
Inspection
This is most beneficial when done at the point of work by skilled inspectors.
Time-boxed
This means that an event has a maximum duration that is fixed and cannot be shortened or lengthened once the sprint has begun.
Inspection
This should be done with artifacts/progress frequently enough to detect undesirable variances, but not so frequently that it becomes an obstruction.
Completed/"Done" PBIs are reviewed. Incomplete PBIs are re-estimated and put back on the Product Backlog.
What happens when a Sprint is cancelled?
Adaption
When an inspector determines that one or more aspects of the process deviate outside the acceptable limits, the product becomes unacceptable. This process/material must then be adjusted.
Product Owner
Who can the Development Team negotiate with if it determines that there is too much/too little work in a sprint?
Development Team
Who decides how to turn the Sprint Goal and Product Backlog items into a "done" product increment during the Sprint?
The Development Team
Who does the work that will deliver a releasable increment of "done" at the end of each sprint.
Only the people executing the work in the Sprint Backlog, usually excludes the Product Owner and Scrum Master.
Who is included when counting the size of the development team?
The Scrum Master
Who is responsible for promoting and supporting Scrum.
Scrum Master
Who must ensure the goals, scope, and product domain are understood by everyone in the Scrum team?
Product Owner
__________ clarifies the selected PBIs.
Scrum Master
__________ coaches the development team in organizational environments in which Scrum is fully adopted and understood.
Sprint Goal
___________ provides guidance to the Development Team on why it is building an Increment.
The Development Team
___________ structured and empowered by the organization to organize and manage own work.
Events
____________ are designed to enable transparency and inspection.
The Product Owner
____________ discusses the objective that the Sprint should achieve the Product Backlog items that would achieve the Sprint's Goal.
The Development Team
____________ works to forecast the functionality that will be developed during the Sprint.
Scrum Master
___________________ ensures that the Sprint Planning event happens and that the attendants understand its purpose.
Sprint Planning
___________________ period where the work to be performed in the Sprint is determined.
Product Backlog Management
___________________ requires the the items of the Product Backlog be ordered to best achieve goals/missions.
Development Team
____________________ self-organizes to undertake the work in the Sprint Backlog during the Sprint Planning and (as needed) throughout the Sprint.
Product Owner
role responsible for maximizing the value of the product as delivered by the development team.
Cross-Functional
teams having all competencies needed to accomplish work without depending on external resources.
