4. ● Agile methodology is an approach to project and
team management
● Based on Agile Manifesto - a mindset that all agile
teams should strive for
● Agile Manifesto includes: 4 values and 12 principles
DEFINITION
5. 4 VALUES
Individuals and
interactions over
processes and tools
Working software over
comprehensive
documentation
Customer collaboration
over contract
negotiation
Responding to change
over following a plan
10. ● A framework for developing, delivering and
sustaining a complex product
● The most popular framework under agile
methodology
● Scrum includes: 3 pillars and 5 values
● Key characteristics: roles in scrum; sprint; product
backlog; user stories and estimation
DEFINITION
12. ROLES IN SCRUM
PRODUCT OWNER SCRUM MASTER DEVELOPMENT TEAM
● Ensuring that the
team is building
the right product
● Act as voice of
client
● Ensure Product
Backlog is
transparent to
Scrum Team
● Help team
understand,
implement Scrum
& to manage
Product Backlog
● Coaching team on
Agile/Scrum
practices, rules &
values
● Who build the
product: BA,
Developer, Tester
● Range from: 3 - 9
members/team
● Cross-functional
13. PRODUCT BACKLOG
● An ordered list of what needs to be done in the
whole projects
● The single authoritative source for items the Scrum
Team work on
● Attributes: description, value, order, estimate & size
● Backlog Refinement
14. USER STORIES
● A backlog item
● Short, simple descriptions of a feature told from the
perspective of the user
● Include 3 elements:
○ The user
○ The action user will take
○ The benefit to user
● As [user] I have to [action] to get [value]
● Epic include many user stories
15. STORIES POINT
● A technique to estimate effort needed for a User
Story
● The Fibonacci sequence (1,2,3,5,8, etc)
● Process:
○ Sorts through the remaining backlog items
○ Agrees on an estimate for each item
○ Captures it in the backlog management system
V
17. SCRUM EVENTS
1
2
3
4
RETROSPECTIVE
At the end of Sprint, Team reflect
what done and brainstorm potential
future improvements
REVIEW
Where the product is
demonstrated to determine
which aspects are finished &
which aren’t
DAILY
Time for the Scrum Team to
synchronize & prioritize
activities for the day
PLANNING
- Team meets to confirm: capacity,
time, people available during new
Sprint
- Identify Sprint Backlog
