1. Lennon Manchester
@leManchester
lennon.manchester@staunchrobots.com

2. Scrum

3. Agile Methodology

4. Agile Manifesto

5. Individuals and interactions over processes and tools
Agile Manifesto

6. Individuals and interactions over processes and tools
Working software over comprehensive documentation
Agile Manifesto

7. Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Agile Manifesto

8. Individuals and interactions over processes and tools
Responding to change over following a plan
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Agile Manifesto

9. 2001 A Space Odyssey

10. Principles

11. Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

12. Welcome
changing
requirements, even
late in
development.
Agile processes
harness change for
the customer's
competitive
advantage.

13. The best architectures, requirements and designs
emerge from self-organizing teams.

14. multidisciplinary
self-organizing
trust
team work
Agile value
continues
team
collaboration
commitment
frequently
communication
sustainable
effective

15. Kent Beck
Mike Beedle
Arie van Bennekum
Alistair Cockburn
Ward Cunningham
Martin Fowler
James Grenning
Jim Highsmith
Andrew Hunt
Ron Jeffries
Jon Kern
Brian Marick
Robert C. Martin
Steve Mellor
Ken Schwaber
Jeff Sutherland
Dave Thomas

17. Time boxes
Planning
Review
Retrospective
Daily
Sprint

18. Sprint
- Defined cycle of work
2 - 4 weeks?

19. Review

20. Review
- review meeting 2.5% of the total sprint

21. Review(2 hr)
- review meeting 2.5% of the total sprint

22. Review(2 hr)
- review meeting 2.5% of the total sprint
- scrum team + client

23. Review(2 hr)
- review meeting 2.5% of the total sprint
- scrum team + client
- review what is delivered

24. Daily

25. Daily15 min

26. Daily15 min
- What I did from the last daily until now

27. Daily15 min
- What I did from the last daily until now
- What I'm going to do until the next

28. Daily15 min
- What I did from the last daily until now
- What I'm going to do until the next
- Blockers

29. Daily
- Same time always
15 min
- What I did from the last daily until now
- What I'm going to do until the next
- Blockers

30. Retrospective

31. Retrospective
3.75% - 3hr

32. Retrospective
- Positive items to keep
3.75% - 3hr

33. Retrospective
- Positive items to keep
- Negative items to improve
3.75% - 3hr

34. Retrospective
- Do not take it personal
- Positive items to keep
- Negative items to improve
3.75% - 3hr

35. Retrospective
- Do not take it personal
- Positive items to keep
- Negative items to improve
3.75% - 3hr

37. Planning

38. Planning
5% of the Sprint

39. Planning
5% of the Sprint
4 hr

40. Planning I

41. Planning I
- What is going to be done?

42. Planning I
- What is going to be done?
- PO what is explain the priority story

43. Planning I
- What is going to be done?
- PO what is explain the priority story
- Explain the business

44. Planning I
- Dev’s estimate that story
- What is going to be done?
- PO what is explain the priority story
- Explain the business

45. Planning I
- Dev’s estimate that story
- What is going to be done?
- PO what is explain the priority story
- Explain the business

46. Planning II

47. Planning II
- How is it going to be done?

48. Planning II
- How is it going to be done?
- Break stories to tasks of 8 hrs

49. Planning II
- How is it going to be done?
- Break stories to tasks of 8 hrs (max)

50. Planning II
- How is it going to be done?
- Break stories to tasks of 8 hrs (max)
- That’s stories goes to the Kanban board

51. Planning II
- Define the meta
- How is it going to be done?
- Break stories to tasks of 8 hrs (max)
- That’s stories goes to the Kanban board

52. To be, or not to be, that is the question:
Whether ler in the mind to
The S
end them: to die, to
nd
sleep, to say we end
rows of outr
Or a Sea
to say we endThe
No
Tis a consummationActors
drea
ui

53. Scrum Team

54. Scrum Team
- auto organization
- flexibility
- focus
- quality
- be on time on the meetings

56. - keep the backlog updated

57. - keep the backlog updated
- breath the product

58. - keep the backlog updated
- breath the product
- control expectations

59. - keep the backlog updated
- breath the product
- control expectations
- defend the interest of the product

60. - keep the backlog updated
- breath the product
- control expectations
- defend the interest of the product
- define sprint meta

61. - answer the business questions
- keep the backlog updated
- breath the product
- control expectations
- defend the interest of the product
- define sprint meta

62. Scrum Master

63. Scrum Master
- solve blocks

64. Scrum Master
- solve blocks
- motivation

65. Scrum Master
- solve blocks
- motivation
- education of the team

66. Scrum Master
- solve blocks
- motivation
- education of the team
- give the right focus

67. Scrum Master
- solve blocks
- motivation
- education of the team
- give the right focus
- identify weirdness

68. Scrum Master
- keep the continues flow
- solve blocks
- motivation
- education of the team
- give the right focus
- identify weirdness

69. Dev Team

70. Dev Team
- estimate

71. Dev Team
- estimate
- help each other

72. Dev Team
- estimate
- help each other
- share the knowledge

73. Dev Team
- estimate
- help each other
- share the knowledge
- update kanban board

74. Dev Team
- have the technical knowledge
- estimate
- help each other
- share the knowledge
- update kanban board

76. Kanban

81. Kanban Boards

82. References
http://agilemanifesto.org/
http://scrum.org/Scrum-Guides
http://www.caelum.com.br/curso-agile-scrum/
http://images.google.com/
https://www.pivotaltracker.com/
http://scrumtool.me/
http://leankit.com/

83. Questions?
Thanks
Lennon Manchester
@leManchester
lennon.manchester@staunchrobots.com