Scrum.org defines Scrum as a management and control process that cuts through complexity to focus on building software that meets business needs. Management and teams are able to get their hands around the requirements and technologies, never let go, and deliver working software, incrementally and empirically.
Scrum itself is a simple framework for effective team collaboration on complex software projects
What is the Role of Scrum & Agile Teams?
Development Team – the role within a Scrum Team accountable for managing, organizing and doing all development work required to create a releasable Increment of product every Sprint.
Product Owner – represents all stakeholders and is the role in Scrum that is accountable for maximizing the value of a product, primarily by incrementally managing and expressing business and functional expectations for a product to the Development Team(s).
Scrum Master – responsible for the success and is the role within a Scrum Team accountable for guiding, coaching, teaching and assisting a Scrum Team and its environments in a proper understanding and use of Scrum.
Scrum Team – a self-organizing team consisting of a Product Owner, Development Team and Scrum Master who implement the Sprint.
Stakeholder – a person external to the Scrum Team interested in the product’s outcome as investors and users. Represented by the Product Owner and actively engaged with the Scrum Team at Sprint Review.
Other Key Scrum & Agile Terms:
Sprint – time-boxed event of 30 days, or less, that serves as a container for the other Scrum events and activities. Sprints are done consecutively, without intermediate gaps.
User Story – a requirement, feature, defect or other unit of business value that can be estimated, developed, tested, and delivered.
Product Backlog – an ordered list of the work to be done in order to create, maintain and sustain a product. Managed by the Product Owner.
Sprint Planning – time-boxed event of 1 day, or less, to start a Sprint. It serves for the Scrum Team to inspect the work from the Product Backlog that’s most valuable to be done next and design that work into Sprint backlog.
Daily Scrum – daily time-boxed event of 15 minutes, or less, for the Development Team to re-plan the next day of development work during a Sprint. Updates are reflected in the Sprint Backlog.
Sprint Review – time-boxed event of 4 hours, or less, to conclude the development work of a Sprint. It serves for the Scrum Team and the stakeholders to inspect the Increment of product resulting from the Sprint, assess the impact of the work performed on overall progress and update the Product backlog in order to maximize the value of the next period.
Velocity – an optional, but often used, indication of the average amount of Product Backlog turned into an Increment of product during a Sprint by a Scrum Team, tracked by the Development Team for use within the Scrum Team.
Sprint Retrospective – time-boxed event of 3 hours, or less, to end a Sprint. It serves for the Scrum Team to inspect the past Sprint and plan for improvements to be enacted during the next Sprint.
For additional information about Scrum & Agile please call (614) 481-6555, e-mail email@example.com or click on one of the following links: