What is Scrum? Why should we hold daily stand-up, sprint planning, sprint review and sprint retrospective meeting? Why should we use Scrum? When we apply Scrum?

1. Scrum
Nguyen Thanh Tuan – PM at Paymentwall

2. Agenda
 What is Scrum?
 Why should we hold daily stand-up,[ sprint
planning, sprint review] and sprint retrospective
meeting?
 Why should we use Scrum?
 When we apply Scrum?
 Discussion

4. What is Scrum?
 Scrum is a process framework that has been used to
manage complex product development.
 Scrum relies on a fixed cadence of iterative cycles
called sprints.
 Scrum is characterized by a high level of feedback
and transparency, both within the team and outside
it
 Its short cycles and collaborative nature make it
ideal for projects with rapidly changing and/or
highly emergent requirements.

5. 5 core values
 Focus
 Respect
 Commitment
 Courage
 Openness

6. 3 distinct roles
 Development team member (Cross functional)
 Scrum Master (help team practice Scrum and
protect team)
 Product owner (manage backlog, push work)

7. 3 artifacts
 Product Backlog
 Sprint Backlog
 Burn chart

8. 4 meetings
 Sprint planning meeting
 Sprint daily stand-up meeting
 Sprint review meeting
 Sprint retrospective meeting

10. Scrum board

11. Why do we need Daily
Stand-up meeting?
 Successful project teams adopt various methods for
keeping team members in sync with one another,
identifying problems that others on the team can
help resolve, and ensuring that progress is
continually made towards achieving the project
goal.
 The stand-up meeting is when each team member
re-validates that they are properly allocating their
time on the most important project activities.

12. Rules of daily stand-up
meeting
 The stand-up meeting is conducted daily
 The meeting time-box is 15 minutes
 All team member attend and participate
 Each team member presents three topics
 What I have accomplished since the last meeting.
 What I am going to accomplish before the next
meeting.
 What obstacles are preventing progress.

13. Sprint retrospective
meeting
 If you want to solve the problems that you are
having, and deliver more value to your customers,
you have to change the way you do your work. That
is why agile promotes the usage of retrospectives:
To help teams to solve problems and improve
themselves!
 Each team member is asked to identify specific
things that the team should:
 Start doing (What have I learned?)
 Stop doing
 Continue doing (What went well?)

14. What makes retrospectives
different, and what’s the benefit of
doing them?
 One retrospective benefit is that they give power to the team.
Since the team members feel empowered, there will be little
resistance to do the changes that need to be done.
 Another benefit is that the actions that are agreed in a
retrospective are done by the team members, there is no hand-
over! The team analyses what happened, defines the actions, and
team members do them. This is much more effective, and also
faster and cheaper.
 These benefits make retrospectives a better way to do
improvements. And they explain why retrospectives are one of
the success factors for using scrum and getting benefits. You can
use different retrospective techniques to get business value out of
retrospectives. And retrospectives are also a great tool to establish
and maintain stable teams, and help them to become agile and
lean.

15. Questions

16. Why should we use Scrum?

17. Why should we use
Scrum?
 Improved stakeholder satisfaction
 Greater employee engagement
 Higher productivity and lower costs
 Faster time to market
 Managing risk and change effectively.
 Functional tests are frequent in the process.
 Direct collaboration with the client.
 Motivation and responsibility of teams.

18. Why should we use
Scrum?
 As the timeframe is short, developers can plan their
work precisely.
 The team delivers finished software that is ready to test.
 The whole company is involved. By announcing Sprints
internally and making progress visible, the entire
organization knows what the development team is
currently working on.
 The team likes the diversity in tasks
 It is fun to work in a committed team that is self-
organized.

19. When we should use
Scrum?

20. Discussion
THANK FOR ATTENDING