Tasks are easier to complete.

Scrum Teams are smaller in size.

Too large to be completed in a Sprint.

Take considerably longer time to review.

User Story Workshops are held as part of Sprint Review.

Acceptance Criteria provide the objectivity required for the User Story to be considered as Done or not

Done.

The Scrum Master defines and communicates the Acceptance Criteria to the Scrum Team.

During the Sprint Retrospect Meeting, the Acceptance Criteria provide context for the Product Owner to

decide if a User Story has been completed satisfactorily.

A and В

A, В and C

C and A

D and A

The Development Team needs a Sprint Goal to create a communications plan of who does what and when.

The Development Team needs a Sprint Goal to communicate exactly who'll do what in the Sprint.

The Development Team needs a Sprint Goal to create synergy among the Development Team members.

The Development Team needs a Sprint Goal so they'll see the value and importance of completing all of the user stories selected for the Sprint meet the definition of done.

Sprint Goal

Roles and Responsibilities

Product Backlog

Team charter

When the Scrum Master realizes that the Scrum framework is not followed entirely

When priorities change in the Product Backlog, in a way that Sprint Backlog items are no longer the highest ones

When the Product Owner determines that it makes no sense to finish the Sprint

When we realize that we cannot deliver all of the Sprint Backlog items

Assessing the Agile maturity level of the organization

Ensuring that all teams are trained in the Scrum framework

Having leadership create and demonstrate an Agile mindset

Setting up autonomous self-regulating, cross-functional teams

Create a task “Correct bugs” and estimate it.

Create a task “Correct bugs” and let the Product Owner prioritize it.

Create a User Story “As a client I want a zero defect product” and estimate it.

Create a User Story “As a client I want a zero defect product” and let the Product Owner prioritize it.

You should demand the Development Team host a retrospective as it is a rule of Scrum.

You should discuss the situation with the Product Owner to see how she feels about no longer having a Sprint Retrospective.

You should require the key Development Team members to participate in the Retrospective to shorten its duration.

You should do nothing as the Development Team is self-organized and self-managed.

Updated Sprint Burndown chart and Impediment log.

Updated Scrumboard and Unapproved Change Requests.

Updated Sprint Burndown chart and Motivated Scrum Team.

Updated Scrumboard and Dependencies.

Eliminating all changes that may affect the quality of deliverables and processes

Facilitating identification of Change Requests by the Scrum Team and their assessment and prioritization

by the Product Owner.

Providing requests for changes in a project.

Approving changes that are amended, removed, or added according to project requirements, and

communicating the same to the Scrum Team.

Seeking help from team members

Experienced team members mentoring new members

Recording Lessons learned to improve processes and address problems

Using information radiators to track the project progress

It helps recognizing who wrote which code

It is beneficial to knowledge transfer

It makes development faster and cheaper

Ask the Product Owner to put the feature on the product backlog with an appropriate priority to protect the team from interruptions of the sprint

Discuss the product goal with the customer and assure them the team will meet the product goals to keep the customer engaged and happy

Ensure the customer understands the value of the current work ask them to reorder the features, and notify them of the new timeline

Reorganize the team's current work and inform the Product Owner of an extension of the sprint to include the new feature in the current sprint

A and В

B and D

A and C

В and C

Changed requirements and estimation mode

Changed requirements and revised estimates

Fixed requirements and estimation mode

Fixed requirements and revised estimates

That any team member can do any of the tasks in the sprint

That the team has team members in each of the Scrum roles

That the team makes their own decisions on how they work

That together the team members have all stalls necessary

Productivity will increase.

Productivity will stay the same.

Productivity will decrease.

It depends on the project's velocity.

Complete incomplete Stories

Increase or re-estimate Velocity

Re-estimate all small Stories

Switch to using Ideal days

The Daily Standup Meeting is a short daily meeting, time-boxed to 15 minutes.

The meeting may be cancelled or delayed if one or more members are not able to attend.

Team members assemble to report their progress in the Sprint and plan the day's activities.

The information provided by the Team members is used to identify the impediments in the way of project

progress.

Colocated Team : War Rooms

Colocated Team: Wall displays

Distributed Team: Video Conferencing

Distributed Team : Manual Scrumboard

Agree with the Product Owner Achieving flow in sprints was the main reason Developers chose to introduce WiP-limits and moving the ticket will improve flow

Agree with the Product Owner Getting work completed is more important than wasting time on an activity that has some impediment preventing it from getting to done

Disagree with the Product Owner Only Developers may decide to move tickets on the Scrum board, so moving the ticket will invalidate the principle of serf-managing teams

Disagree with the Product Owner Work on the blocker ticket is in progress and moving the ticket back artificially increases the WiP-limit to 3 and leaves the block in place

Any quality related error must be fixed only at the end to ensure that the deliverable is Done.

Iterative Product development, repetitive testing, and documentation help ensure quality is inherent in each

Done deliverable.

Any quality requirement must consider the capacity and willingness of the organization to meet the

business need.

The changing needs of the customers must be incorporated during the increments.

The Product Owner must proactively help the team solve issues during the meeting.

The Product Owner should discuss the issues with the management and come up with solutions after the

meeting.

Discuss and resolve issues as and when they are spoken about during the meeting.

Discuss among Core Roles after the meeting and resolve the issues.

I am not sure and would like to go with the group's consensus conclusion.

I agree with the group's conclusion and would like to discuss some minor issues.

I disagree with the group's conclusion and have major concerns.

I wholeheartedly agree with the group's conclusion.

Epics

Themes

User Stories

Views

The Development Team

The Product Owner

The Project Manager

The Scrum Master

Updated with new tasks and completed tasks.

Placed besides the new one to compare team velocities in Sprints.

Analyzed by the Scrum master to understand the project progress in that particular sprint.

Reset or wiped off.

A, В, and С

A

A, C, and D

С