Early feedback gives developers more time to develop new system features because they spend less time on reworking

Early feedback enables agile teams to deliver features with high business value because customer maintain focus on high business value

Early feedback reduces cost because it reduces the time needed for testing

Early feedback make it more likely that the system built is what customer wanted because they are given opportunity to make changes

Have the developers discuss ,choose and introduce suitable communication tools

Introduce the tools in use elsewhere in the organization that have helped other teams

Raise the impediment with management and discuss the challenges of the distributed nature of team

Wait for developers to choose and implement a solution

Sprint Goal emerges as the developers work through the plan and learns more about the work

Scope may be clarified as more is learned

Scope may be re-negotiated as more is learned

Developers focus on finishing all sprint backlog items as their commitment from sprint planning

A potentially shippable product increment

A formulated plan for subsequent sprints

At least one piece of working software

A proof of concept

Sprint is timeboxed to 4 Wks or less ; Sprint Planning is is timeboxed to 8 hrs for a 1 month sprint ; Daily Scrum is timeboxed to 15 mins

Daily Scrum is timeboxed to 15 mins; Sprint Review is timeboxed to 4 hrs for a 1 month sprint ;Sprint Retrospective is timeboxed to 3 hrs for a 1 month sprint

Sprint Review is timeboxed to 6 hrs for a 1 month sprint ;Sprint Retrospective is timeboxed to 8 hrs for a 1 month sprint; Sprint Planning is is timeboxed to 8 hrs for a 1 month sprint

Sprint Retrospective is timeboxed to 4 hrs for a 1 month sprint; Daily Scrum is timeboxed to 15 mins ;Sprint is timeboxed to 1 to 6 Wks

An event that starts at a specific time

An event with a minimum set time

An event that cannot take more than the maximum amount of time

An event that must happen by a specific time

A previously agreed period of time during which team works towards completion of some goal and stopping when the time limit is reached

Everyone is clear on next steps towards sprint goal

PO is informed of the progress

Impediments are discussed and possible solutions selected

Impediments to be addressed are discussed

Competence

Decision making ability

Mutual trust and respect

Openness

Anytime before sprint planning

During Product Backlog refinement

Atleast 1 or 2 sprints ahead

During sprint planning

It refers to internally deciding who does what, when and how in order to achieve best results

It refers to achieving maximum business value in minimum time span

It refers prioritizing creation of high value deliverables over lower value deliverables

It refers to allowing all facets of scrum process to be observed by everyone

Use of a Scrumboard to ensure clear visibility of the team's progress

Use of a Release planning schedule to ensure coordination across multiple scrum teams

Use of a prioritized product backlog to be viewed by internal and external stakeholders

Use of a fixed amount of time for each process and activity in a scrum project

An opportunity for developers to find ways to incrementally improve velocity

An activity for developers to demonstrate their work to PO

When the scrum team and stakeholders inspect the increment produced in the sprint and adapt the product backlog accorgingly

PO , SM and Developers

PO and Stakeholders

PO and Product Lead

Scrum Team and stakeholders

PO ,Technical Leads and Stakeholders

Scrum Team's process and any suggested improvements to the process

Sprint Results

Productivity and Utilization of Developers

All of the above

Minimum 2 hrs

As long as required to update Product Backlog

2 Hrs for a monthly sprint

4 Hrs for a monthly sprint

As long as required to inspect the increment

Needed skills and knowledge

The process the scrum team does the scrum events

The way the team members interact

The Definition of Done

All of the options

PO is optional. He/She will attend when needed or requested by Developers

PO is not allowed to attend and is only for Developers

PO is Mandatory. It is opportunity for the entire scrum team to inspect and adapt the way they work

PO is optional as the event is focused for Developers

Participating as a member of the Scrum Team

Giving the Developers the technical feedback

Discussing upcming Product Backlog Items

Recording the meeting minutes

Participating as a member of the Scrum Team and facilitating as requested or needed

Selecting the most important action items

Ensuring conflict is avoided

At the end of every sprint

When the project is over

Immediately after sprint planning

When needed or requested

Companies no longer need to recruit and train software testing specialist

Test Automation tasks are now responsibility of developers instead of test team

Role barriers are eliminated and team members contribute to project success based on their unique skills and perspective

Project costs are lower because the need for specialized test team is eliminated

People and interactions of the team

Health of relationship between the team

The Definition of Done

Product Backlog Items for the next sprint

During the Sprint Retrospective

During the Sprint Planning

At the start of every sprint

During Daily Scrum

True

False

False. It will be added to product Backlog and will be worked on if the team has enough capacity

During Daily Scrum

It refers to emphasizing on achieving results by focusing on the needs of the scrum team

It refers prioritizing creation of high value deliverables over lower value deliverables

It refers to making improvements through adaptation

It refers to allowing all facets of scrum process to be observed by everyone

Self motivation and team responsibility

Individual responsibilities and accountability

Delegation of authority through planning

Extensive upfront planning and adherence to approved plans

Add them to Product Backlog and work on them when there is capacity

The most impactful improvements are addressed as soon as possible and may be added to sprint backlog for the next sprint

Order them on a saperate list and work on them from top to bottom

Let the Scrum Master select which items to add to the sprint

The Developers

The Scrum Master

The Product Owner

The Scrum Team

The Stakeholders

They are in User Story format

They are testable use cases

They are clear enough and clear information for the PO and Developers to understand the work that needs to be done and to create forecast of PBI to implement sprint goal

They are functional tasks (i.e desingn, frontend, backend, architecture) that are clear enough to know who will be doing what during the sprint

Combine the teams into a single scrum team

There should be separate PO and backlog for each scrum team

The product has only 1 Product Backlog and There should be single PO

Authoritarian

Decentralized

Persuasive

Assertive

The primary source of information, for the product comes from Product Backlog and items are small enough to be done within sprint

The Product Backlog updates or changes require stakeholders approval

The Product Backlog is maintained using online tool

The Product Backlog is a complete list of requirements for the product

Product Backlog items should be pre-assigned to individual team members and no larger than 8 story points or larger than 1 day

Add them to Hardening sprints

Add them to product backlog or Definition of Done

Add them to specific swim lane at the top of scrum board

Add them to external team to take care of

In between sequential sprints (i.e Sprint n & Sprint n+1)

1 or 2 sprints ahead or in actual sprint

In sprint 0

During Sprint Retrospective

True

False

Product Backlog is divided by future sprints

Product Backlog items are estimated in Story Points

Product Backlog is managed using JIRA

Product Backlog is ordered and available to all stakeholders

It supplements the requirement document

It is a complete project plan that the scrum team commits to complete

It is a living artifact that evolves as the product and the environment in which it will be used evolves

It should not have more than 6 months of work

True

False

They are discussed and planned during Sprint spikes

They are discussed during Sprint 0

They are added to Product Backlog or implemented along with functional development

The Scrum Master

The Developers themselves

The Product Owner

The Technical Architect

The Developers after clarifying the requirements with PO

It is an inventory of work to be done for the product

Ordered based on value , priority , risk and dependencies

It is a finalized list of requirements to be done for the product

It is managed by PO

What ever the PO decides is best

Highest priority items at the bottom and lowest priority items at the top

Items with smallest story points at the top and biggest at the bottom

Items are ordered by function (i.e desingn, frontend, backend, database)

Least risky at the top and riskiest at the bottom

True

False

A new product backlog is created to meet the needs to the users

Product backlog is static as it is a commitment to stakeholders

Product backlog is a living artifact that evolves as the product and the environment in which it will be used evolves

Identify a different market for current Product backlog

Anytime during sprint planning

Never. Even if the individuals work on specific sprint backlog items , the Developers as a whole remains accountable for the sprint backlog in its entirety

During Daily Scrum

When the SM assigns it

The Developers

The Product Owner

The Scrum Master

The Scrum Team

As soon as the SM identifies new work

As soon as the PO identifies new work

Only at Daily Scrum

As soon as they are identified

It refers to emphasizing on achieving results by focusing on the needs of the scrum team

It refers to achieving maximum business value in minimum time span

It refers prioritizing creation of high value deliverables over lower value deliverables

It refers to fixing certain amount of time for each process and activity in a scrum project

The Developers can ask PO for help if they need clarification or to optimize the work they are doing in the sprint

The Developers can collaborate with PO to adjust the amount of work in the sprint backlog

The Sprint Backlog emerges during the sprint

The Sprint Backlog is a finalized plan that the developers commit to completing by the end if the sprint

Bug Fixes

Use Cases

Tasks

User Stories

Any of these

It is a finalized list of items that the developers commit to complete by the end of the sprint

Each task is assigned an owner

It is developers plan for the sprint

User Stories no bigger than 8 story points

It is ordered by SM

True

False

To ensure all selected items from sprint planning has been done

For the purpose of transparency

Because it is PO's commitment to management

In order to maximize the utilization of developers

True

False

True , but only if the work done has dependencies on other scrum teams

False , multiple scrum teams will synchronize integrations at hardening sprints

False , each scrum team is independent

True, otherwise the PO and stakeholders may not be able to accurately inspect the work that was done in the sprint

The total no. of defects found during the project is much higher than on traditional waterfall

There is less rework because customer sees the product regularly

It is easy to determine the developer who introduces the most defects when integrating code

There is enough time to complete all features scheduled for the given iteration

At the end of each sprint

When it makes the most sense

After stakeholder approval

When all work to make increment shippable , is done

A release plan for delivering features based on projections from the business

An MVP used to validate market fit

A product plan that defines projected work for all future sprints

Completed functional requirements waiting for UAT

The sum of all the product backlog items completed during a sprint that complement those delivered in previous iterations

A release plan for delivering features based on projections from the business

An MVP used to validate market fit

A product plan that defines projected work for all future sprints

Completed functional requirements waiting for UAT

The sum of all the product backlog items completed during a sprint that complement those delivered in previous iterations

Daily Scrum

Grooming

Sprint Planning

Sprint Review

It proposes fixing a certain timeframe for each activity

It ensures the scrum team members don't take-up too much or too little work for a particular period of time

It is a principle through which scrum framework addresses the project constraint of time

It ensure there is detailed upfront planning before start of every sprint

PO is responsible for creating DOD and may receive feedback from the developers

Scrum team is responsible for creating DOD and may receive feedback from the PO

When the forecasted work becomes unachievable

When the PO is absent more often

When the Developers are unclear on what to do on the remaining work

When the sprint goal becomes obsolete

Modify DOD so that the item can be added to the increment

Add the completed work of the item to the increment and create separate product backlog items to make it done in "done" in the next sprint

Don't include the item in the increment, put it back to product backlog and let PO decide what to do with it

Extend the sprint until item is "done" and can be added to the increment

To ensure that the developers are completing their assigned tasks

So they know who to contact if they need to clarify the requirements

To have complete transparency and a common understanding of "done" work at the end of each sprint. Help manage the maintenance and ownership costs

To know what skills are needed to make a item "done" and who should be added to the team

When sprint time-box ends

When all tests are passed

When there is no more work remaining to make the item potentially shippable

When all of the tasks are complete

Daily Standup

Daily Scrum

Sprint Planning

Sprint Review

It increases transparency

It provides a shared understanding of what it means when the work is complete

It provides guidance on how many product backlog items the developer can select for the sprint

It defines what it takes for the increment to be ready for release

It guides the developers on what must be satisfied before the SM can close the sprint

Sending a daily status report to the stakeholders

Estimate the work needed to complete the items in hours rather than days

Log any technical debt incurred during development on a separate but transparent list

Doing the work that is necessary to meet the Definition of Done

Sprint Retrospective will be less painful

Scrum Master becomes optional

Their Definition of Done will expand to include more stringent criteria for higher quality

Sprint timeboxes will be shortened because the productivity is higher

Team membership will change in order to promote knowledge sharing

Storming : Team tries to accomplish work

Forming : Team is matured with experience

Norming : Team begins to sort out internal differences

Performing : Team efficiency is at its optimal level

The Scrum team ( if none is available from the organizational standard)

The PO as He/She is responsible for maximizing the value of the work done by the developers

The SM as He/She is responsible for managing the process

The company as it is responsible for providing the environment and support the scrum team needs

The Developers from each scrum team creates its own and ensures all other teams understand the difference

Developers from each scrum team will create and adhere to their own

They must follow a single DOD

Developers from all scrum teams must have DOD that makes their combined work potentially releasable

As much as the scrum team agrees is necessary to create enough ready product backlog items

As much as the PO deems necessary to create enough ready product backlog items

Upto 10% capacity of the developers in a typical sprint but as much as 90% in early sprints

No more than 1 day per week for the developers

Sprint Retrospective

Sprint Planning

Sprint Review

Product Backlog Refinement

The Product Owner

The Scrum Master

The Scrum Team

The Developers

Ask each developer what he/she did yesterday, will do today, and any impediments

Updating the Scrum board

Assigning tasks to each team member

Ensure developers understand and enact the Daily scrum to maximize value

All anwers apply

Daily Scrum

Sprint Review

Sprint Retrospective

Refining the Product Backlog

Sprint Planning

4 Wks

3 Wks

1 Wk

2 Wks

Any of these