that

should be dependent on each other

that

are set in stone

aspects

of which are negotiable

testing

isn’t necessary

to help the Scrum Team resolve

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

to interact with stakeholders and

maintain the product vision

to order the work and ensure that

Scrum Team members clearly understand the details of the requests

to define and manage the backlog of

work to be done and prioritize those work items

A requirements documents and a test

plan

A test plan and a product backlog

A requirements documents and a product backlog

A sprint backlog and sprint goal

by comparing user stories to each

other

by comparing the minimum viable

product (MVP) to the stakeholder's feedback

by comparing use cases to

each other

by comparing the Product Owner and

the Scrum Master's feedback

Potentially shippable product

increment

The sprint backlog

The deployment

The product backlog

product owner

developers

project manager

Scrum Master

Whenever needed

At the end of each Sprint

Whenever the ScrumMaster suggests

At the project closing

Whenever the team suggests

Adaptability

Enhanced

collaboration

Scalability

Reduced

communication overhead

Liskov

substitution

Interface

segregation

Open/closed

principle

Dependency

inversion

Single

responsibility