scrum
TRANSCRIPT
1
Introduction
Purpose:- Scrum is the framework for developing and
sustaining complex products.- Define scrum roles, events, characteristics
and art that binding them together
2
Agenda
- Scrum- Pillars of scrum frameworks- Scrum Event- Scrum team- Scrum activities
3
Agenda
- Scrum
4
Scrum
- Scrum is the framework- Address complex and adaptive problems- Productively- Creatively- Delivering product with good quality
5
Scrum
- Light weight- Easy to understand- Difficult to master
6
Agenda
- Scrum- Pillars of scrum frameworks
7
3 Pillars of scrum framework
- Transparency- Inspection- Adaptation
8
3 Pillars of scrum framework
Transparency- Team have the same point of view e.g. DOD, coding
standards…- Inside scrum team must be transparent, tell with scrum
master/customer about the bugs- Be honest, wen you hide problem, you make thing even
worse
9
3 Pillars of scrum framework
Inspection - Review the work- How the team using
Scrum- Project progress
10
3 Pillars of scrum framework
Adaptation WHEN?- New ideas, information- Deviate the result to
unacceptable goal- Adjust process- As soon as possible
11
Agenda
- Scrum- Pillars of scrum frameworks- Scrum Event
© Sioux 2014 | Confidential |
12
Scrum Events
- Project kick off meeting- Sprint planning- Daily scrum- Sprint review- Retrospective
13
Scrum Events
- Introduce project- Short talk to introduce each
other- Define definition of done- Define way of working
Project kick-off meeting
14
Scrum Events
- Implemented- Have unit test- Update SQTS- Update SRS, Architecture
documents- Tested- Committed- Reviewed- Reworked
Definition of done
15
Scrum Events
- Product owner, scrum master, scrum team
- Clarify, prioritize- Sprint goal- Sprint backlog
16
Scrum Events
- Estimation based on Exp- Estimation for your self- Split the feature to smaller task- Understand requirement clearly
Estimation
17
Scrum Events
- Update progress of team member
- Don’t skip the scrum meeting- Online/Offline- Scrum team (scrum master)- Everyday
Daily meetings
18
Scrum Events
- Be prepared- On time- Answer 3 questions- Short (less than 15 mins)- Don’t discuss technical issues
Daily meetings
19
Scrum Events
- Scrumboard:- Online- Offline- Update the scrum board
when you make some progress is also important
- TODO, TODAY, REVIEW, BLOCKING, DONE
Daily meetings
20
Scrum Events
- Product owner, scrum master and development team
- At the end of sprint- Informal- Ideally, developer will give
demonstration on his/her product backlog
Review meetings
21
Scrum Events
- The last done in sprint- For development team, but PO
and SM should participate- Be prepared- Review the previous actions- Define 1,2 actions and stick for
the next sprint.
Retrospective
22
Agenda
- Scrum- Pillars of scrum frameworks- Scrum Event- Scrum team
23
Scrum Team
Consist of:- Product Owner- Scrum Master- Development team
24
Scrum Team
Self organizing:- Scrum team choose how best to
accomplish their work
Cross functional- Team have all competencies to
accomplish their work without depending to the other team.
Characteristics
25
Scrum Team
- Lead developer effort by conveying his/her vision to team
- Consider stake holder and team- Available to answer questions
and deliver direction- Determine the product backlog
Product Owner
26
Scrum Team
Consists professionals who do the work of delivery a potentially increment of product every sprint
Development Team
27
Scrum Team
- Verbal communication- Writing- English- Clarify requirements- Say NO in a nice way
Sioux’s development Team
28
Scrum Team
Characteristic:- Self-organizing, no one tells
development team how to do things
- Cross functional with development, testing… skills
- There’s only development team members in the development team
- There’s no sub team- 3-9 people
Development Team
29
Scrum Team
Development Team
30
Scrum Team
- Think about the test before start to implement.
- The task can’t be done if the test does not available
- Don’t break the build server- Build server fail have highest
priority
Development Team
31
Scrum Master
- Make the team happy for the good progress
- Make customer happy- Improve the team
Scrum Master
32
Scrum Team
- Responsible for scrum master is understood and enacted
- Ensure scrum team adheres to scrum theories, practice and rules
- Review code- Help developer to do good
design
Scrum Master