The Team segment is where agile teams commit to user stories and execute on those commitments in an iterative manner. Each iteration will contain a set of agile rituals including sprint planning, the sprint demo, and a retrospective.

Within this segment, Scrum is used to manage the execution of these tasks in a Sprint based on the original PI commitments. This team is responsible for fulfilling their commitments and completing that work within the Sprint. Once the code has completed the Sprint process, it moves onto a Deploy phase.

The overall success rate of projects delivered using Scrum reported by respondents is 62%… Given the dismal results for innovation recorded on an economy-wide basis, this is a very encouraging result.1

This work happens in iterations. In most cases, the teams will adhere to a two week iteration schedule. Within this period of time, the teams will have sprint planning, a daily stand-up meeting, and then end the iteration with a sprint demo and retrospective. These agile ceremonies are put in place to ensure that the team can continue to improve from iteration to iteration.

Inputs

The Team segment begins with a set of commitments made at the PI Planning Event.

Outputs

The Team segment creates new digital value through new development or integrations. This completed work will be transitioned to the Deploy segment.

References