The sprint backlog

Potentially shippable product

increment

The product backlog

The deployment

by comparing user stories to each

other

by comparing the Product Owner and

the Scrum Master's feedback

by comparing use cases to

each other

by comparing the minimum viable

product (MVP) to the stakeholder's feedback

A requirements documents and a product backlog

A test plan and a product backlog

A sprint backlog and sprint goal

A requirements documents and a test

plan

to interact with stakeholders and

maintain the product vision

to define and manage the backlog of

work to be done and prioritize those work items

to order the work and ensure that

Scrum Team members clearly understand the details of the requests

to help the Scrum Team resolve

day-to-day issues and counterbalance the ongoing requirements changes

aspects

of which are negotiable

testing

isn’t necessary

that

should be dependent on each other

that

are set in stone

a

shared understanding of the system

enables

reverse engineering

only

shows what can be done in a single sprint

is

a preliminary conception of the system

An architectural design of the

solution

A document containing test cases

for the current sprint

Wireframes designs for User

Interface

An increment of Done software

Enhanced

collaboration

Scalability

Adaptability

Reduced

communication overhead

Project Sponsor

Scrum Master

Lead Developer

Product Owner

Whenever the team suggests

Whenever the ScrumMaster suggests

At the project closing

Whenever needed

At the end of each Sprint