ScrumMaster Review Test

independent, negotiable, valuable, estimable, small, testable

5 attributes of a PBI

1. product backlog 2. reminder 3. future conversations 4. who 5. what 6. why 7. description 8. estimate 9. value 10. order

a _______(1)_________ is a ___(2)_______ for _____(3)__________ . it describes_(4)___, ___(5)_____, ___(6)_____. Each PBI includes a __(7)__________, an ____(8)_____, a __(9)______ and an ___(10)____

1. product backlog 2. list 3. unsolved problems 4. unmet needs 5. priority 6. force ranked 7. maximize 8. what 9. how

a _______(1)_________ is a ___(2)_______ of _____(3)__________ and ___(4)___ in___(5)_____ order. It is___(6)_____by the Product Owner to __(7)__________ ROI. The product backlog describes ___(8)________ but not___(9)____

see the progress being made and determine whether the Team needs help

a product owner might attend the daily scrum to 1. comment on the team's progress 2. tell the team which tasks to work on next and update the product backlog 3. make sure the team is still on target for its Sprint goals 4. see the progress being made and determine whether the Team needs help

the timebox expires

a sprint is over when -committed items have met definition of done -all tasks are done -timebox expires -product owner determines its done based on team size

3 hours

according to the "agile software development with Scrum" for a 30 calendar day sprint, sprint retro should never be longer than this...

8 hours

according to the scrum guide, a 30 calendar day sprint, sprint planning cannot be longer than this

4 hours

according to the scrum guide, for a 30 calendar day sprint the review should never be longer than this amount of time

do whatever is necessary to achieve the goal

after team has committed to a sprint goal, they are given authority to... -work according to the priorities set by the scrummaster, as the scrummaster is committed to the scrum framework -work under the direction of the product architect, who has set the definition of done -do whatever is necessary to achieve the goal -swap sprint backlog items with product backlog items if it cannot finish them

in an ongoing dialogue throughout the project

agile approach involves both business people and developers... 1. in an ongoing dialogue throughout the project 2. at the kickoff meeting and the final review 3. during the preliminary phases of development 4. in the release planning meeting

the ability to steer

agility is mainly about: -going fast -the ability to steer -predictability -micromanagement

the team's collective opinion

amount of work an experienced team takes on each sprint should be based on -available team hours minus task hours -estimates done by the team lead -desires of the product owner -the team's collective opinion

increases

as stakeholders react to an emerging product from sprint to sprint, the total number of items in the product backlog generally -increases -decreases -remains the same -gets locked by the product owner

small

attribute of PBI that captures idea that: items are right sized to satisfy 4 or 5 each week

negotiable

attribute of PBI that captures idea that: we can do it however

independent

attribute of PBI that captures idea that: we can do it whenever

testable

attribute of PBI that captures idea that: we have an idea what done means and "done right"

estimable

attribute of PBI that captures idea that: we know which things are easier or harder

valuable

attribute of PBI that captures idea that: we know which things are more valuable or less valuable

emergent

based on Agile principles, architecture is... -implemented in the first iterations -planned and built out in sprint 0-not important, only functionality is important -emergent

meet with the team member to determine a solution

best approach to take if team member is consistently late for the daily scrum -report team member to his or her manager -ask scrummaster to move team member off the scrum team -meet with team member to determine a solution -have team member do the testing

usually ignores the real problems

changing or removing Scrum rules to fit an organization 1. is the main activity of the first Sprint 2. is best done with coaching from an experience ScrumMaster 3. usually ignores the real problems 4. is done by the Scrum Transition Team during rollout

required documentation is usually part of a product wide definition of "done"

do scrum teams document products? -yes all documentation is written after a product is fully developed -required documentation is usually part of a product wide definition of "done" -no, scrum does not value documentation -never, documentation is done by the tech writer

yes, and it values responding to change even more

does the Agile manifesto place any value on planning? 1. yes, and it values responding to change even more 2. yes, an agile method is an efficient plan-driven approach 3. no traditional planning is replaced by the sprint burndown chart 4. no planning has no value at all in Agile approach

presents the highest priority stories to consider including in the sprint

during a sprint planning meeting, the product owner -determines how the team accomplishes its work -divides selected stories in to specific tasks -decides how many stories will be delivered by the end of the sprint -presents the highest priority stories to consider including in the sprint

after the daily scrum meeting is held, the necessary team members have a discussion about the solution

during daily scrum, team member identifies a solution to a teammate's impediment. she wants to implement immediately. what is best next step? -scrum development team is told to evaluate the solution and report back at the next daily scrum meeting -scrummaster tells her to prepare an example and show the scrum development team so they can consider using the code -product owner notes the impediment and solved the problem after the meeting -after the daily scrum meeting is held, the necessary team members have a discussion about the solution

contains a mix of activities

every sprint 1. is focused on delivering artifacts for the current phase 2. is either a development sprint or a research sprint 3. contains a mix of activities 4. works like a mini waterfall

the timebox begins

every sprint, sprint planning occurs as soon as

do not perform as well as co-located teams

geographically dispersed teams usually... 1. outperform co-located teams because of reduced costs 2. are not permitted in Scrum 3. do not perform as well as co-located teams 4. perform just as well as co-located teams given the right tools

the highest value items discovered during the project, which may exclude some of what was originally planned

given a three month release cycle using two week sprints, an effective scrum team will probably deliver -the highest value items discovered during the project, which may exclude some of what was originally planned -everything in the original statement of work on time and on budget -all features originally planned for the release, plus all the new features discovered along the way -one quarter of what was originally planned because scrum teams' estimates are usually wrong

the product owner adds them wherever he wants on the product backlog

how do scrum teams handle changing requirements during a sprint 1. a senior team member adds them to the product backlog based on technical feasibility 2. the scrummaster puts them at the bottom of the sprint backlog 3. the team asks the stakeholder making the request to schedule a change control meeting 4. the product owner adds them wherever he wants on the product backlog

they find a way to divide the work into potentially shippable product increments without increasing Sprint length

how does a scrum team deal with initial infrastructure and architecture work that will take eight (8) weeks to complete? -by increasing the team size so one team can complete the infrastructure and architecture without increasing Sprint length -they ask the architecture team to provide the architecture and infrastructure up front -by doing the infrastructure and architecture work in the first two sprints -they find a way to divide the work into potentially shippable product increments without increasing Sprint length

ideally around 4 or 5

how many items at the top of the product backlog should a team be able to complete in a single sprint 1. only 1 2. no more than 3 3. it depends on team size 4. ideally around 4 or 5

there is no time "between" sprints

how much time should be allocated between sprints for bug fixing, system testing, etc. 1. no more than 5 days 2. there is no time "between" sprints 3. it depends on team velocity 4. at least one full day

every sprint

how often should the scrum development team normally accept changes in their goals? 1. at least once a day 2. each release cycle 3. every sprint 4. once, at product kickoff

is independent, negotiable, valuable, estimable, small and testable

ideally each product backlog item (PBI) -is categorized by development phase -is independent, negotiable, valuable, estimable, small and testable -has an exact estimate in hours -contains the test "as a...I want...so that...."

inform the product owner

if a CEO were to request to add a story to the current Sprint, should the Team - put the story at the top of the product backlog -add the story to the current Sprint and drop a story of equal size -add story to current sprint without adjustments -inform the product owner so they can work with the CEO

product owner, scrummaster, and team

if team determines that it has over-committed itself for a sprint, who should be present when reviewing and adjusting the sprint goal and work? 1. product owner, scrummaster, and team 2. product owner and stakeholders 3. team 4. scrummaster, project manager and team

not longer than 4 hours

in 30 day sprint, how long is sprint review -not longer than 4 hours -not longer than 2 hours -at least 1 hour -as long as required

end users

in addition to the entire scrum team, these people are essential for a productive sprint review

product increment

in addition to the right people, a successful sprint review requires a potentially shippable one of these

the scrum development team

in scrum, who manages the team members? 1. their functional managers 2. the scrum development team 3. team lead 4. scrummaster

for the team to manager their work during the sprint

main purpose of a sprint backlog is -so product owner understands what the scrum development team has committed to for a sprint -so team can manage the number of hours spent on tasks in the sprint -for team to manage their work during the sprint -progress tracking by scrummaster during the sprint

product increment

makes an "emerging" product visible to stakeholders

product backlog

makes product owner priorities visible to everyone all at once all the time

sprint plan

makes the current plan and progress toward the sprint goal visible to scrum development team

Team members scrummaster

members of a scrum team that attend the daily scrum every day

scrummaster and team members

members or the scrum team who must attend the sprint retrospective

scrum team

necessary attendees for sprint planning

product owner

optional attend at sprint retrospective

identifying appropriate release dates

product owner responsibility includes: -setting sprint length -identifying appropriate release dates -determining technical solution for project -understanding team member skills necessary for success

sprint goal and sprint backlog

purpose of sprint planning is to establish these

product increment and the product backlog

purpose of the sprint review is to inspect this and adapt this

scrum development team

responsible for achieving a sprint goal

just before sprint timebox expires

retrospective always occurs at this time

team member

role most likely to communicate an impediment during a sprint -stakeholders -product owner -team member -stakeholders

product owner

role responsible for maintaining product backlog -ScrumMaster -Product Owner -Scrum Development Team -stakeholders

sprint review

scrum event that -requires entire scrum master -occurs before sprint retrospective -lasts 1 hour for each week the timebox is (e.g. 4 hours max for a 4 week sprint)

sprint retrospective

scrum event that -requires entire scrum master and team members attend -occurs last before the timebox ends -lasts 1 hour for each week the timebox is (e.g. 4 hours max for a 4 week sprint)

daily scrum

scrum event that -requires entire scrum team and team members to attend -occurs daily -lasts 15 minutes max

sprint planning

scrum event that -requires entire scrum team to attend -occurs first, once timebox starts -lasts 2 hours for each week the timebox is (e.g.: 8 hours max for 4 week sprint)

framework for learning about products and processes

scrum is a 1. defined process that prescribes what to do in any situation 2. lightweight approach that does not disrupt an organization's current habits 3. predictive process that fits easily with traditional project management 4. framework for learning about products and processes

with somewhat unknown requirements and technological challenges

scrum is intended for work... 1. with somewhat unknown requirements and technological challenges 2. that has a high degree of certainty 3. when there is a tight deadline 4. that is simple

when planning any sprint early or late in development

scrum teams welcome changing requirements -during release planning -before the construction phase begins -only during sprint planning -when planning any sprint early or late in development

facilitate the team's search for improvements

scrummaster's role in sprint retrospective is to -provide answers to challenges the team identifies -facilitate the team's search for improvements -determine the re-composition of the team -lead the team in the evaluation of each individual team member

scrum development team's process

sprint retrospective exists to inspect and adapt this

sprint retrospective

sprint review occurs just before this

product owner

team member is optional

daily

the "scrum" happens this often

may be a natural outcome of implementing scrum well

the loss of some staff and management -mostly occurs when implementing scrum poorly -may be a natural outcome of implementing scrum well -can be prevented by implementing scrum gradually -does not generally occur when implementing scrum

working software

the primary measure of progress according to Agile development principles

a one-dimensional list in priority order

the product backlog is... 1. arranged by relative size, with large risky items at the top 2. grouped into sections P1 through P5, representing priority order 3. a one-dimensional list in priority order 4. randomly arranged

continually throughout the project

the product backlog should be re-prioritized 1. when stakeholders approve a change order 2. only as a last resort when things go wrong 3. continually throughout the project 4. during release planning and then locked down

t

the purpose of the scrum is to inspect and adapt these

15 minutes

the scrum can never be longer than this amount of time

is the team's scrum expert

the scummaster -prioritizes the team's backlog -creates, refines, and communicates customer requirements to the Scum development team -is the team's scrum expert - is the keeper of the product vision

stakeholders

these people may be useful during sprint planning but no necessary

complex

type of work scrum is most suitable for -low-risk -simple -pre-defined -complex

describes why the project is pursued and the product desired end state

what are some desired qualities of a product vision? -features a detailed overview that enlightens and inspires -outlines traceability back to overall corporate governance in IT investment -provides a complete breakdown structure of the ROI formula -describes why the project is pursued and the product desired end state

transparency, inspection, adaptation

what are three components of an empirical process

create a potentially shippable product increment

what does a scrum team attempt to do during the first sprint? 1. create a potentially shippable product increment 2. build a sellable product 3. develop the preliminary product backlog 4. focus on requirements analysis, architecture and infrastructure

a thin vertical slice of functionality

what does a scrum team try to develop every sprint? -it depends on the phase -a thin vertical slice of functionality -a working prototype -whatever the product owner requests

accomplish the sprint goal

what does scrum team try to do during the first sprint? -predetermine the complete architecture and infrastructure -deliver design documents -develop a plan for the rest of the sprints -accomplish the sprint goal

together with the product owner, focus on what can be done and identify a way to deliver something valuable at the end of each sprint

what is the approach that scrum encourages when a team determines it will be difficult to deliver any value by the end of a sprint? 1. extend the sprint by a few days to accommodate the extra work 2. immediately escalate to senior management 3. suggest the product owner abnormally terminate the sprint 4. together with the product owner, focus on what can be done and identify a way to deliver something valuable at the end of each sprint

30 days at most, preferably shorter

what is the longest allowable timebox for a sprint? 1. up to six weeks 2. as longa s necessary to meet sprint commitments 3. one day starting with a "daily scrum" 4. 30 days at most, preferably shorter

collective knowledge and experience

what scrum teams are guided by during a sprint -product owner -scrummaster -project documentation and daily stand up -collective knowledge and experience

the entire item is returned wherever the product owner wants within the product backlog

what should happen when a product backlog item (PBI) does not meet the definition of "done" at the end of a sprint? -entire item is returned to the top of the Product backlog -entire item is returned wherever the product owner wants within the product backlog -team is given partial credit and documents the technical debt -team is given zero credit and a new PBI is written for the uncompleted portion

continual small improvements to engineering practices

when applied to development, what does Scrum require? -improvements to engineering practices determined by management -no changes in engineering practices -improvements to engineering practices before sprinting begins -continual small improvements to engineering practices

when it meets the agree upon definition of "done"

when is a product backlog item considered complete 1. once all tasks in the sprint backlog are completed 2. when QA reports that it passes all acceptance criteria 3. when the timebox expires 4. when it meets the agree upon definition of "done"

scrum teams place value in following a plan, but they value responding to change even more

which of following statements is true about scrum teams and planning? -scrum teams place value in following a plan, but they value responding to change even more -planning is not important in scrum -traditional planning is replaced by the sprint burndown chart -scrum is intended to be an efficient way to carry out plans that have already been made

the team is self-organizing

which of the following is a characteristic of a good Scrum Development team? -members all have similar level technical skills -they seek direction from the ScrumMaster -the team is self-organizing -team members wait for tasks to be assigned to them

free the product owner from other responsibilities

which of the following is the best option for an overworked product owner 1. limit the amount of time the product owner spends with the scrum team 2. ask the project manager to pick up some of the product owner's responsibilities 3. split the product owner role and distribute the duties among more people 4. free the product owner from other responsibilities

the gap between current practices and prescribed practices is a measure of incompetence and competitive risk

which of the following is usually true when organizations change or only partly implement scrum's rules? 1. the gap between current practices and prescribed practices is a measure of incompetence and competitive risk 2. they are acting in the adaptable spirit of the Agile Manifesto 3. the nature of real projects prevents strict adherence to the Scrum framework

the product owner's participation is defined by the team

which statement about the role of the product owner during the daily scrum? 1. the product owner's participation is defined by the team 2. the product owner ensures the burndown rate is maintained at the estimated rate 3. the product owner outlines the additional changes that must be absorbed by the Team in the Sprint 4. the product owner provides instruction to the Team on how to implement a workable solution

scrum development team

who determines how team accomplishes work after creating Sprint Backlog and committing to Sprint goal -scrum development team -scrummaster -team lead -project manager

scrummaster

who is primarily responsible for enforcing scrum's rules and practices? -scrum development team by consensus -product owner -each individual team member -scrummaster

product owner

who is primarily responsible for maintaining the product backlog -scrummaster -stakeholders -scrum development team -product owner

product owner

who is responsible for the ROI achieved by a scrum team -product owner -program sponsor -project manager -scrummaster

scrummaster

who is usually responsible for facilitating the sprint retrospective -product owner -any team member -scrummaster -no one

the product owner

who prioritizes the product backlog 1. stakeholders with help from the scrummaster 2. senior functional manager 3. scrummaster, with input from team members 3. the product owner