Agile projects achieve the intent of process area 3.2 Peer Reviews by conducting continual, less-formal, peer reviews throughout development.
Which of the following is NOT an example of peer reviews typically performed within Agile projects?
A.
Having refinement / grooming sessions on the specifications (e.g., user stories) with the team and business stakeholders on a regular basis throughout an iteration.
B.
Conducting sprint retrospectives every 2-3 iterations to identify process improvement opportunities.
C.
Daily meetings with other team members to discuss openly and provide feedback on the work products (e.g., code or tests) being developed.
D.
The demonstration of products early and often to customers, at least at the end of an iteration during the iteration review.
Sprint retrospectives are held at the end of every sprint (not every 2-3 iterations) to evaluate the team's performance and identify opportunities for improvement. Retrospectives are a core Agile practice, but they are not considered peer reviews, which typically involve reviewing work products such as code or design documents. Peer reviews focus on product quality, while retrospectives focus more on team performance and process improvements.
[Reference:"Agile projects focus on continual peer reviews during development, such as reviewing code or tests, while retrospectives are more process-oriented"., ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit