A.Exploratory.

B.Functional.

C.Unit.

D.Integration.

E.Manual regression.

F.Performance.

A.Deductive

B.Hybrid

C.Empirical

D.Technical

A.Release planning

B.Daily scrum

C.Sprint review

D.Sprint retrospective

E.Refinement meeting

A.No, because the increment has to be approved at the Sprint Review before it can be released, and a 2- week Sprint would not be considered continuous.

B.No, because stakeholders may have already seen the new features and the Sprint Review will be meaningless.

C.No, because before releasing an Increment it first has to fulfill the Definition of Done.

D.No, because the Product Owner may not be available each time a PBI is done, and the Product Owner has to decide if it should be released.

E.Yes, there is nothing in Scrum that conflicts with Continuous Delivery.

A.Handle them during a risk mitigation phase before development

B.Scrum is for functional, frontend development only

C.Include them in the Product Backlog

D.Before the release, they should be tested and validated in a hardening sprint

E.Specific expectations can be used as acceptance criteria to specific product backlog items

F.Important, recurring non-functional requirements can be added to the definition of done