Agile Scrum Methodology

Revision as of 18:41, 6 February 2022

Written by Océane Haddad - s212838

Abstract

blabla

Scrum methodology

Definition

Origin of the method (date, and where it comes from) ^[1]

Purpose of this method

Structure of the method

The Scrum roles

Definition of Product Owner, Scrum Master, team and Customers&Stakeholders: their roles and interactions with each other

The Scrum documents

Definition of the Product Backlog, the Sprint Backlog and Burndown charts

The Scrum events

Definition of the Sprint planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective

The typical conduct of the Scrum method

Step 1: Writing the Product Backlog

The Product Owner creates a list of ideas and features that could go into the product and prioritise them. Definition of user stories

Step 2: Sprint planning meeting

The Product Owner, the Scrum Master and the team discuss the content of the next sprint based on the top priority user stories.

Step 3: Writing the Sprint Backlog

List of user stories that have been committed to for the next sprint. The entire team and product owner have a solid understanding of what each of the user stories involves based on the discussions from the sprint planning meetings.

Step 4: Sprint

1 to 3 weeks.

During the sprint, daily scrums occur as a stand-up meeting where the team discusses what they have completed, what they are working on and any difficulties.

Outcome of the sprint = potentially shippable product

Step 5: Sprint review and Sprint retrospective meetings

- Sprint review: where the team showcases their work to the product owner

- Retrospective: where the team works on what they can do to improve their process

Application

Limitations

References

1. ↑ test ref 1