This keynote is made for my presentation about scrum. So much stuff is taken From Yahoo Scrum Training given by GC and Antonio of MEME team

1. AGILE

2. ADAPT FAST
and
ITERATE

5. WHAT IS SCRUM ?

8. • “Scrum is an agile framework for completing
complex projects. Scrum originally was
formalized for software development projects, but
works well for any complex, innovative scope of
work” - Scrum Alliance -
• “Scrum is an iterative and incremental agile
software development method for managing
software projects and product or application
development.” - Wikipedia -

9. 3
- roles
- ceremonies
- artifact

10. Roles

11. The Boss

12. Agile is about

13. Team
Product
Scrum master
Owner

14. Product Owner
• Worked in shared vision
• Manage and prioritized backlog
• Decide release dates and contents
• Responsible for ROI, audience, etc
• Interact with stakeholder and customer to define Product backlog
• Adjust feature and prioritize every sprint a needed
• Accept or reject work results during sprint review

16. Scrum master
• Protect values and principles
• Removes impedance
• Keep team fully functional and productive
• Enable cooperation
• Shield the team from the “dark force”
• Facilitate Integration
• Improves dynamics to reveal problem
• He/She does NOT allocate task

17. The Team

18. The Team
• Typically 5-9 People
• Cross functional : Programmer, tester, etc
• Full time allocated
• Self-organized
• Rich communication
• Responsible for quality
• Estimates complexity
• Commits to increments of deliverable Products

22. Pigs X Chickens

23. Artifacts

24. Product Backlog
• The product requirements
• Everything (idea, feature, epics)
• Expressed in User Story
• PO Keep it organized
• Always prioritized and estimate
• Maintained and visible

27. User story
I as a <client>
Wants <feature>
Because <ROI>
Acceptable Criteria

28. Sprint Backlog

29. Sprint Backlog
• User stories selected by team
• Will be executed in the next x days
• Fully estimated
• Prioritized
• Divided in Daily task
• Duration is < 1 day
• if > 1 days = split in 2 or more task

32. Project Board
Burndown chart

38. Definition of Done
• “DONE” or “NOT DONE”
• Avoid the 90% syndrome
• Code produced, commented, checked
in and tested
• Peer review
• Continuous Integration

39. Ceremonies

40. Ceremonies
• Sprint planning
• Sprint review
• Sprint retrospective
• Daily Scrum

42. Sprint Planning
• What are we going to build?
• How are we going to build it?

43. Sprint Planning
• Planning 1
• PO explains the scope
• Team estimates complexity
• Planning 2
• Team chooses the sprint backlog
• Team writes task to each story

44. Estimation Game

45. Sprint Review
• Team demo what was accomplished
during the sprint
• Each developer demo a story
• Informal, no slides
• Whole team participates
• Anyone invited to participate but only
(pigs talk)

46. Sprint Retrospective
• What was cool?
• What can we improve?
• What the team can solve?
• What the company need to solve?
• Only PO, SM and Team

47. Daily Standup
• What I did since last meeting?
• What will I do until next meeting?
• Any impedance?

48. The ZEN of Agile
• Honesty
• Commitment
• Small Victories 1000x > 1 Big Victories