SQL Database Design For Developers at php[tek] 2024
Scrum
1. Introduction
Purpose:
- Scrum is the framework for developing and
sustaining complex products.
- Define scrum roles, events, characteristics
and art that binding them together
1
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
8
9. 3 Pillars of scrum framework
Inspection
9
- Review the work
- How the team using
Scrum
- Project progress
10. 3 Pillars of scrum framework
Adaptation
10
WHEN?
- New ideas, information
- Deviate the result to
unacceptable goal
- Adjust process
- As soon as possible
13. Scrum Events
13
- Introduce project
- Short talk to introduce each
other
- Define definition of done
- Define way of working
Project kick-off meeting
14. Scrum Events
14
- Implemented
- Have unit test
- Update SQTS
- Update SRS, Architecture
documents
- Tested
- Committed
- Reviewed
- Reworked
Definition of done
16. Scrum Events
16
- Estimation based on Exp
- Estimation for your self
- Split the feature to smaller task
- Understand requirement clearly
Estimation
17. Scrum Events
17
- Update progress of team
member
- Don’t skip the scrum meeting
- Online/Offline
- Scrum team (scrum master)
- Everyday
Daily meetings
18. Scrum Events
18
- Be prepared
- On time
- Answer 3 questions
- Short (less than 15 mins)
- Don’t discuss technical issues
Daily meetings
19. Scrum Events
19
- 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
20
- 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
21
- 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
24. Scrum Team
24
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
25
- 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
27. Scrum Team
27
- Verbal communication
- Writing
- English
- Clarify requirements
- Say NO in a nice way
Sioux’s development
Team
28. Scrum Team
28
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
30. Scrum Team
30
- 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
31
- Make the team happy for the
good progress
- Make customer happy
- Improve the team
Scrum Master
32. Scrum Team
32
- 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
Editor's Notes
It’s not a process or a technique to build product.
Rather, it’s a framework thin you can employ various techniques and processes.
Scrum make clear the relative efficacy of product management and development praticse so we can improve
It’s bad if we tell the customer that our product has some bugs. But it even worse if we hide them and let the customer find it.
Scrum prescribe four formal events for inspection and adaptation
Select product backlog
Give estimation
Solve conflict in estimation
Agree upon
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
Each people have their own characteristic, but as a team we should agree upon
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
E.g.
Niko project:
Build architecture
Build UI for Android
