1

SCRUM IN ACTIONHacen Dadda

Algiers Tech Meetup

2

ME

Hacen Dadda

Web DeveloperConsultant CTO @

@hacentechhdadda@hivedigit.comhttp:\\about.me\hacen

3

AGENDA

Agile MethodsScrum Scrum SoftwaresSuccessful Scrum

4

Agile Methods

F a c t s

5

Manifesto for Agile Software Development

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

6

Agile Methods

● Extreme Programming (XP)● Crystal● Dynamic Systems Development Method (DSDM)● Feature-Driven Development (FDD)● Kanban● Scrum

7

Scrum

F a c t s

8

Story

9

Story

Scrum is a lightweight agile project management framework and incremental projects of all types. Ken Schwaber, Jeff Sutherland and others have contributed significantly to the evolution of Scrum over the last decade. Scrum has garnered increasing popularity in the agile software development community due to its simplicity, proven productivity, and ability to act as a wrapper for various engineering practices promoted by other agile methodologies.

10

Scrum

Scrum is:● Lightweight● Simple to understand● Difficult to master

11

Scrum Theory: Transparency

12

Scrum Theory: Inspection

13

Scrum Theory: Adaptation

14

Scrum Overview

.

15

The Scrum Team: The Product Owner

The product owner is the project’s key stakeholder and represents users, customers and others in the process. The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.

16

The Scrum Team: The Scrum Master

The ScrumMaster is responsible for making sure the team is as productive as possible. The ScrumMaster does this by helping the team use the Scrum processThe ScrumMaster is responsible for making sure the team is as productive as possible. The ScrumMaster does this by helping the team use the Scrum process

17

The Scrum Team: The Development Team

The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. Development Teams are structured and empowered by the organization to organize and manage their own work.

18

Scrum Events: Sprint Planning

The sprint planning meeting is attended by the product owner.The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.

19

Scrum Events: Daily Scrum

The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. During the meeting, the Development Team members explain:

● What did I do yesterday?● What will I do today?● Are there any impediments in your way?

20

Scrum Events: Daily Review

At the end of each sprint, the team demonstrates the completed functionality at a sprint review meeting, during which, the team shows what they accomplished during the sprint. Typically, this takes the form of a demonstration of the new features, but in an informal way; for example, PowerPoint slides are not allowed. The meeting must not become a task in itself nor a distraction from the process.

21

Scrum Events: Scrum Retrospictive

Also at the end of each sprint, the team conducts a sprint retrospective, which is a meeting during which the team (including its ScrumMaster and product owner) reflect on how well Scrum is working for them and what changes they may wish to make for it to work even better.

22

Scrum Artifacts: Product Backlog

The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.

23

Scrum Artifacts: Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.

24

Strory Point

Story point is a arbitrary measure used by Scrum teams. This is used to measure the effort required to implement a story.

In simple terms its a number that tells the team how hard the story is. Hard could be related to complexity, Unknowns and effort.

25

Burn Down Chart

As a definition of this chart we can say that the Burndown chart displays the remaining effort for a given period of time.

When they track product development using the Burndown chart, teams can use a sprint Burndown chart and a release Burndown chart.

26

Scrum Task Board

When practicing Scrum, we can make the sprint backlog visible by putting it on a Scrum task board. Team members update the task board continuously throughout the sprint.Either during or before the daily scrum, estimates are changed (up or down), and cards are moved around the board.

27

let us remember

28

Scrum Softwares

F a c t s

29

Choose the right tool

30

Successful Scrum

F a c t s

31

Success?

32

Team Spirit

33

Reduce the Tunnel Effect

34

Open to Changes

35

Continuous Improvement

36

Architecture

37

Optimize the Communication

38

Motivation

39

Mastery

40

LEAN

41

References

https://www.wikipedia.org/

https://www.mountaingoatsoftware.com/

http://www.scrumguides.org/

42