Scrum methodology advocates for a planning meeting at the start of the sprint, where team members figure out how many items they can commit to, and then create a sprint backlog – a list of the tasks to perform during the sprint.ĭuring an agile Scrum sprint, the Scrum team takes a small set of features from idea to coded and tested functionality. In keeping with an agile methodology, sprints are timeboxed to no more than a month long, most commonly two weeks. The Scrum model suggests that projects progress via a series of sprints. The product owner (PO) is the other role, and in Scrum software development, represents the business, customers or users, and guides the team toward building the right product. The first is a ScrumMaster, who can be thought of as a coach for the team, helping team members use the Scrum process to perform at the highest level. Within agile development, Scrum teams are supported by two specific roles. Those are issues that are decided by the team as a whole.Īnd in Scrum, a team is cross functional, meaning everyone is needed to take a feature from idea to implementation. The scrum team is self-organizing in that there is no overall team leader who decides which person will do which task or how a problem will be solved. Scrum relies on a self-organizing, cross-functional team. This is why in Scrum development, for example, a sprint planning meeting is described in terms of the desired outcome (a commitment to a set of features to be developed in the next sprint) instead of a set of Entry criteria, Task definitions, Validation criteria, Exit criteria (ETVX) and so on, as would be provided in most methodologies. This is because the team will know best how to solve the problem they are presented. In the agile Scrum world, instead of providing complete, detailed descriptions of how everything is to be done on a project, much of it is left up to the Scrum software development team.

Scrum meaning