Scrum

An agile Overview

Introduction

Scrum Simple framework for project management Is Agile Is Iterative

Values Focus on people Empowered and committed teams Self-Managed

The Framework

Roles Product Owner

Keep update the Product Backlog Add business value to user stories Certify the final product

ScrumMaster Maintains the processes Facilitator Help to resolve impediments No authority on the team

Team Cross functional Involved in tasks Self-Managed

Chickens & Pigs

Chickens Can not talk in the daily meetings Involved in the project

Pigs Can talk in daily meetings Committed in the project

Artifacts - Product Backlog

Keep updated by the Product Owner Divided in user stories User stories are sorted by business value The team estimates the effort of user stories

(usually in points) Large items are split and clarified

Artifacts – Sprint & Sprint Backlog Always same duration (1-4 weeks) User stories are split in small tasks (ideally 1

day effort) Visible increments Task “Done”

Artifacts – Task Board

Visible to all team Columns

ToDo Doing Done

Also Burn down chart is used

Meetings – Sprint Planning

Participants Team, SM, PO, others stakeholders

User stories are split into short tasks The team committed the tasks

Meetings – Daily Meeting

All days meeting All team involved in the meeting Reporting to the team, rather to a boss 15 minutes duration Team must answer

What they did? What they are doing? Do they have problems?

Meetings - Retrospective

Take place to the end of the sprint All people can talk The team reflects on its own process Idea is do better what is wrong and improve

what is right

Conclusion

Scrum.. Is Easy Is Hard Works

Links

http://www.scrumalliance.org/ http://www.implementingscrum.com/ http://www.controlchaos.com/ http://www.jeffsutherland.com/