Module 2: Plan the sprint

During sprint planning, the team needs to evaluate the impact of the proposed requirements on the technical solution. Design information is crucial for estimating the development effort.

The assumption is that Al the architect has worked with the product owner to prioritize the release backlog. Sprint 1 is finished and the rest of the self-paced training describes the activities during sprint 2 of a release.

When the sprint starts, the product owner reviews the backlog to identify the stories and nonfunctional requirements that can be contained in a defined period of time, which is also referred to as a timebox.

After the requirements are identified, the architect explores technical solutions for high-risk items. Then the team commits to completing a set of features based on their understanding of the development and test effort.

[CLM scenario] During sprint planning, the developers estimate the development effort and the test specialists plan the test effort according to the requirements that the product owner proposed.

Jazz.net icon Money that Matters Lifecycle Scenario on Jazz.net

Sprint 1 is complete and the team is now focusing on sprint 2. Bob, the product owner, is preparing for the sprint planning meeting. While reviewing the backlog, he finds a new story that a stakeholder submitted. He also finds a new security requirement for the application.

During the sprint planning, Al the architect assesses design needs that relate to the new requirements.

The team checks that every requirement links to an implementation story and a test case. The objective is to ensure that the most important business needs are covered and that the sprint can contain the related design, development, and testing activities.


Feedback