Absolute Free CTFL4 Exam Practice for Comprehensive Preparation 

are often documented following in rule-oriented format using the following template: "As a [role], I want [feature], so that I can [benefit]"

can be written in different formats and represent an aspect of a user story referred to as confirmation' of the so called "3 C's" 

Only developers and testers should be involved in retrospectives, as involving people in other roles is very likely to prevent developers and testers from having open and constructive discussions that really help identify process improvements.

Retrospectives can be very effective in identifying process improvements and can also be very efficient and cost-effective especially since, unlike reviews, they do not require any follow-up activities

On Agile projects, well-conducted retrospectives at the end of each iteration can help the team reduce and sometimes even eliminate the need for dairy stand-up meetings.

During retrospectives, in addition to identifying relevant process improvements, participants should also consider how to implement these improvements and retain them based on the context of the project, such as the software development lifecycle.