Infosys Global Agile Developer Certification

The Agile meeting where the project team members give a demo of the software to the stakeholders at the end of the Sprint is known as the "Sprint Review Meeting." So, option 1, "Sprint Review Meeting," is the correct answer.

The ideal time to conduct the Sprint Retrospective Meeting by the Agile Team is "Option 4: At the end of the Sprint to analyze how the Sprint was." This meeting typically occurs after the Sprint Review meeting and provides the team with an opportunity to reflect on the completed Sprint and discuss what went well, what could be improved, and how to make adjustments for the next Sprint.

In Agile, a story can be considered as "DONE" when it meets the Acceptance Criteria and fulfills the Definition of Done (DoD) established by the team. So, "Option 4: Story has passed Acceptance Criteria" is the correct choice. The DoD typically encompasses various criteria, including completion of development, testing, and meeting business requirements, before a story can be considered done.

"Option 4: Following a plan over responding to change" is NOT part of the Agile Manifesto. The Agile Manifesto values responding to change over following a plan. The correct statement in the Agile Manifesto is "Responding to change over following a plan." The Agile Manifesto prioritizes adaptability and flexibility in response to changing requirements and priorities.

The fourth basic activity in eXtreme Programming (XP) is "Listening." So, the correct option is "Option 4: Listening." In XP, listening to customer feedback and needs is a fundamental aspect of the development process.

The most appropriate sequence for planning poker estimation for story points in Agile is typically a modified Fibonacci sequence to reflect the uncertainty and complexity of different tasks.

Option 2, "0, 1, 2, 3, 5, 8, 13, 21, 40, 100, 8," is a commonly used sequence and is more aligned with Agile estimation practices. It includes smaller numbers for simpler tasks and then larger gaps for more complex and uncertain tasks.

Options 1, 3, and 4 are not as commonly used in Agile planning poker for story point estimation.

In Agile, particularly in Scrum, testing-related activities should ideally be integrated into the development process from the beginning of the Sprint. Therefore, "Option 3: Right from the beginning of the Sprint" is the most appropriate choice.

Testing activities, such as test planning, test design, and test execution, should be performed in parallel with coding and other development activities. This helps identify and address issues early in the Sprint and ensures that potentially shippable increments of the product can be delivered at the end of each Sprint.

In Agile and Scrum, the estimate for a User Story's effort should ideally be a collaborative effort involving the entire development team. Therefore, "Option 4: Team Member - After arriving at a consensus by providing justification" is the most appropriate choice.

Estimates are typically determined through discussion, consensus, and the collective input of the development team members. The team members should provide their estimates and reasoning, and through discussion, they should work towards a consensus estimate. It's important to consider the diverse perspectives and expertise within the team, including the Subject Matter Expert, but the final estimate should be a collective decision.

While the Product Owner's input is valuable, they shouldn't unilaterally dictate the estimate, and the Scrum Master typically facilitates the process but doesn't provide the estimate. The goal is to achieve a consensus estimate that the team believes is reasonable and achievable.

To determine the probable end date of a release in an Agile project, the key inputs considered typically include:

(a) Prioritized User Stories: The order and priority of user stories in the product backlog influence which features will be included in the release.

(b) User Story Estimates in size: Estimations of user story sizes (e.g., story points or other relative size measures) provide insight into the complexity and effort required for each user story.

(d) Team Velocity: The team's historical velocity, which is a measure of how much work the team can complete in a given time frame (usually in story points or similar units), helps in forecasting how many story points can be completed in the release.

So, the correct answer is "Option 4: a, b, c, and d." All of these inputs are valuable for making an informed decision about the probable end date of the release during release planning.

During the task estimation activity of a Sprint Planning meeting, the role that is typically not directly involved is the "Product Owner" (Option 4).

The key roles involved in Sprint Planning and task estimation are typically:

1. Developers: These team members are responsible for breaking down user stories into tasks and estimating the effort required to complete them.

2. Testers: Testers are part of the development team and are involved in task estimation, particularly when estimating testing-related tasks.

3. Scrum Master: The Scrum Master facilitates the Sprint Planning meeting and ensures that the Scrum process is followed but doesn't usually participate in task estimation.

The Product Owner's primary involvement is in providing clarity on user story requirements and prioritization. They may offer insights during the Sprint Planning meeting but are not directly involved in task estimation, as this is primarily a responsibility of the development team.