Scrum In ActionMona Shokrof

Agile Coach and Trainer Scrum Master, ITWORX Education

What is Scrum

2

Agile framework for completing complex projects

Agile Values

Working Software over documentation

Individuals and interactions over process and tools

Responding to change over following a plan

Customer Collaboration over Contract Negotiation

3

Principles behind AgileOur highest priority is to satisfy the customer

through early and continuous delivery of valuable software.

Working software is the primary measure of progress.

Deliver working software frequently, from a couple of weeks to a couple of months, with a

preference to the shorter timescale.

Welcome changing requirements, even late in development. Agile processes harness change for

the customer's competitive advantage.

4

Principles behind AgileThe most efficient and effective method of

conveying information to and within a development team is face-to-face conversation.

Business people and developers must work together daily throughout the project.

Simplicity--the art of maximizing the amount of work not done--is essential.

Build projects around motivated individuals. Give them the environment and support they need,

and trust them to get the job done.

5

Principles behind AgileAgile processes promote sustainable development. The sponsors, developers, and users should be able

to maintain a constant pace indefinitely.

Continuous attention to technical excellence and good design enhances agility.

The best architectures, requirements, and designs emerge from self-organizing teams.

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts

its behavior accordingly.

6

Scrum been used by

• Microsoft

• Yahoo

• Google

• Apple

• Qualcomm

• Time Warner

7

• IBM

• Philips

• Siemens

• Nokia

• BBC

Scrum Usage

8

Scrum Origin

9

Characteristics

• Progress made through sprints

• Self organizing teams

• Inspection and adaption

• Team works as a unit , doing all work in iterations

10

Sprint

• One to four weeks long - constant duration

• No requirement change during the sprint

• Work on all stages until work done during the sprint

11

Scrum Roles

• Team

• Scrum Master

• Product Owner

12

Scrum Team

• 5-9 persons

• Cross-functional

• Co-located

• Self Organizing

13

Product Owner

• Represents the Business side

• Makes scope vs. schedule decisions

• Prioritize the features

• Works with the team closely

14

Scrum Master• Servant/Leader

• Focus on Agile values and principles

• Removes impediments

• Coach the team to be self organizing

• Protects the team from external interference

15

Scrum Artifacts

• Product Backlog

• Sprint Backlog

• Shippable Product Increment

16

Product Backlog

17

• Responsibility of the Product Owner

• Prioritized by the Product Owner

Product Backlog

• Features

• Defects

• Enhancements

• Experiments

Set of items that represent the components of the product

Product Backlog

Upcoming sprints (2-3)

Current release

Future releases

Sprint Backlog

• Set of tasks to work on Product backlog item

• Responsibility of the team

• Task state updated daily

• Emerging tasks are added while working

20

Sprint Backlog

21

Product increment

• Working part of the product

• Potentially shippable

• Approved by the product owner

22

Definition of "Done"

• Team agreement

• What “Done” means ??

• Product Backlog item

• Task

23

Scrum Events

• Sprint Planning

• Daily Scrum

• Sprint Review

• Sprint Retrospective

24

Sprint Planning

• All team attends the meeting

• Choose highest priority product backlog items to work upon

• Break down items into tasks

• Team estimate tasks

• Team commits to finish these items

25

Sprint Planning

• Typically 2 - 4 hours for 2 weeks sprint

• High level Technical design may be considered

26

Sprint Planning

• Sprint Goal : goal statement of the sprint

• Sprint Backlog

27

Output

Daily Scrum• aka daily standup

• maximum 15 mins

• Defined time and place everyday

• Team alignment

• Not status for Scrum Master

28

Daily Scrum

• What did you do yesterday?

• What will you do today?

• Is there anything blocking/delaying you?

29

Sprint Review

• Demo for potentially shippable product increment

• Product owner/team are attending

• Other stakeholders may attend

• Purpose is to inspect and adapt the product

30

Sprint Review

• Feedback gathered and put in Product Backlog

• Could include highlights of the done/remaining product backlog items

• Typically 30 - 60 mins

31

Sprint Retrospective• Team and Scrum master

• Product owner may attend

• Purpose is to inspect and adapt the process

• All team encouraged to speak

• Typically 1-2 hours

32

Sprint Retrospective

33

Scrum Brief

34

Additional Artifacts

• User Stories

• Burn down charts

• Burn up charts

35

User Stories

As a (user) , I want to (feature) so I can (reason-benefit)

Burn down chart

Burn up chart

Additional Events

• Release planning

• Backlog refinement

39

Release planning

40

Workshop

41

The Greeting Card Application

References

• Scrum Guidehttp://www.scrumguides.org/scrum-guide.html

• Mike Cohn Blog http://mountaingoatsoftware.com/

• Agile Manifesto http://agilemanifesto.org/

42

About MonaAgile Coach and Trainer

www.shokrof.com mona@shokrof.com

LinkedIn : Mona Shokrof Agile بالعربي