Scrum

Hoang Hai Hung

Nov 2016

1
Outline
1. Software development models

2. Agile

3. Scrum

4. Practices

5. Q&A
2
Outline
1. Software development models

2. Agile

3. Scrum

4. Practices

5. Q&A
3
Software development models
The software development models are the various processes or
methodologies that are being selected for the development of the project
depending on the projects aims and goals

4
Waterfall

5
Waterfall

6
Advantages of Waterfall
Approach is simple
More disciplined
Well structured
Easily understandable and explainable phases
Provides easily markable milestones in the development process

7
V Model

8
Incremental model

9
Spiral model

10
Software development in real
world

11
Outline
1. Software development models

2. Agile

3. Scrum

4. Practices

5. Q&A
12
Agile
Agile is a time boxed, iterative approach to software delivery that builds
software incrementally from the start of the project, instead of trying to
deliver it all at once near the end.

13
Agile

14
Manifesto for Agile
Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

15
12 principles behind the Agile
manifesto
1. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.

2. Welcome changing requirements, even late in development. Agile

processes harness change for the customers competitive advantage.

3. Deliver working software frequently, from a couple of weeks to a couple

of months, with preference to the shorter timescale.

4. Business people and developers must work together daily throughout the
project.
16
12 principles behind the Agile
manifesto
5. Build projects around motivated individuals. Give them the environment
and support they need, and trust them to get the job done.

6. The most efficient and effective method of conveying information to and

within a development team is face-to-face conversation.

7. Working software is the primary measure of progress.

8. Agile processes promote sustainable development. The sponsors,

developers, and users should be able to maintain a constant pace
indefinitely.
17
12 principles behind the Agile
manifesto
9. Continuous attention to technical excellence and good design enhances
agility.

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

essential.

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

organizing teams.

12.At regular intervals, the team reflects on how to become more effective,
then tunes and adjusts its behavior accordingly.
18
Outline
1. Software development models

2. Agile

3. Scrum

4. Practices

5. Q&A
19
History
Hirotaka Takeuchi and Ikujiro Nonaka introduced the word 'Scrum' as a term
in the context of product development in 1986 in their article on the New New
Product Development Game

20
Value

Commitment

Team members individually commit to achieving their team goals, each and every
Sprint.

21
Value

Courage

Team members know they have the courage to work through conflict and
challenges together so that they can do the right thing.

22
Value

Focus
Team members focus exclusively on their team goals and the Sprint Backlog;
there should be no work done other than through their backlog.

23
Value

Openness
Team members and their stakeholders agree to be transparent about their work
and any challenges they face.

24
Value

Respect
Team members respect each other to be technically capable and to work with
good intent.

25
Roles
Product owner

Scrum master

Development team

26
Product Owner
The Product Owner represents the product's stakeholders and the voice of
the customer, and is accountable for ensuring that the team delivers value to
the business

27
Scrum master
Responsible for making sure a Scrum team lives by the values and practices
of Scrum

Helping the team do the best work it possibly can, remove impediments

Coaching the Development Team in self-organization and cross-functionality

28
Development Team
5 - 9 members

Cross-functional, with all of the skills as a team necessary to create a

Product

Self-organizing

29
Workflow
Planning

Daily Scrum

Sprint review

Retrospective

30
Workflow

31
 1.Planning
A team planning meeting that determines what to complete in the coming
sprint.

Communicate the scope of work that is intended to be done during that

Sprint

Select Product Backlog Items that can be completed in one Sprint

Time-boxed to a four-hour limit for a two-week Sprint

32
 1.Planning Timebox
Two parts :
2 - 4h
First half

Selects the Product Backlog Items might be achievable in that Sprint (with priority)

Explain to make sure the Team understand about the User Stories

Second half, the Development Team

Decomposes Tasks, resulting in a confirmed Sprint Backlog

33
Estimate effort (by point) for each task using Planning Poker
Planning poker

34
Planning poker

35
2. Daily meeting (DM)
Answer three questions:

What did i do yesterday ?

Timebox
What will i do today ?
15
Any impediment ?

36
Kanban board

37
Burndown chart

38
3. Review meeting
Reviews the work that was completed and the planned work that was not
completed
Presents the completed work to the stakeholders (a.k.a. the demo)

Timebox
2h

39
4. Retrospective
Reflects on the past Sprint
Identifies and agrees on continuous process improvement actions

Timebox
1.5h

40
Retrospective

41
Retrospective

42
Why Scrum ?
Increase product quality, reduce cost

Flexibility

Keep team focus, improve quality of team members

Satisfy the customer

FUN !!!

43
44
Outline
1. Software development models

2. Agile

3. Scrum

4. Practices

5. Q&A
45
Q&A
1. How many meetings are there in Sprint ?

2. Who assign tasks for members in development team ?

3. Disadvantages of Scrum ?

46
THANK YOU !

47