Slides with an introduction on Scrum Agile process. Addressing the basics: Origins and Principles; The Roles of the Product Owner, Scrum Master and the Team; The Meetings (Daily Stand up, Sprint Planning, Sprint Review and Retrospective) and the artifacts (Sprint Backlog, Product Backlog and the charts)

1. Campus Party 2009
Agile Software
Development
with
RUM
SC
Friday, January 30, 2009

2. ANTONIO CARLOS SILVEIRA
Senior Software Development Manager
Yahoo!
Blog: http://www.acarlos.com.br/blog/
Twitter: acarlos1000
e-mail: acarlos@yahoo-inc.com
Friday, January 30, 2009

3. AGENDA
Origins and principles
1
Roles
2
Meetings
3
Artifacts
4
Friday, January 30, 2009

4. 1
Friday, January 30, 2009

5. Origins and
Principles
Friday, January 30, 2009

6. Conventional Process
Waterfall
Fonte: ROYCE 1970
Friday, January 30, 2009

7. Friday, January 30, 2009

8. Different reality
Different business needs and
dynamics
Friday, January 30, 2009

9. Waterfall
Friday, January 30, 2009

10. Continuous
Improvement
There is nothing new here
Friday, January 30, 2009

11. The pioneers
Taylor Ford Sloan Deming Ohno Nonaka Takeuchi
Friday, January 30, 2009

12. The Agilists
Jeff Ken Mike Alistair Martin Ron
Kent Beck
Sutherland Schwaber Cohn Cockburn Fowler Jeffries
Friday, January 30, 2009

13. Agile Manifesto
Agile Manifesto
Individuals and
Process and tools
over
interactions
Comprehensive
Working software over
documentation
Customer collaboration Contract negotiation
over
Responding to change Following a plan
over
Source: www.agilemanifesto.org
Friday, January 30, 2009

14. Agile Methodologies
Extreme Programming (XP)
!
Crystal Clear
!
Adaptive Software Development (ASD)
!
Scrum
!
Feature Driven Development (FDD)
!
Dynamic Systems Dev Method (DSDM)
!
Friday, January 30, 2009

15. Friday, January 30, 2009

16. SCRUM Who uses it?
quot;Microsoft quot;SalesForce.com
quot;Yahoo quot;Oracle
quot;Google quot;Time Warner
quot;Electronic Arts quot;Turner Broadcasting
quot;Lockheed Martin quot;Toyota
quot;Philips quot;BMC Software
quot;Siemens quot;CapitalOne
quot;Nokia quot; Abril (Brazil)
quot;BBC quot;Globo (Brazil)
quot;Nielsen Media quot;UOL (Brazil)
Friday, January 30, 2009

17. Delivery Focus
Transparency
Short and fixed cycles (15 days)
Total Quality
Team Work
Constant Communication
Commitment
Self organization
Reveal the problems
Friday, January 30, 2009

18. Key Characteristics
Self-organizing teams
Enhanced Communication
Commitment
Product progresses in a series of 15 days “sprints”
Requirements and needs go to the “product backlog”
Working software always as the delivery
Trust and Transparency
Fast adaptation
Time box
Reveal the Problems
Friday, January 30, 2009

19. Balance towards adaptation
ation
dapt
A
al
tion
i
Trad
ation
icip
Ant
Friday, January 30, 2009

20. Balance towards adaptation
Ant
icipa
tion
SCR
UM
Ada
ptat
ion
Friday, January 30, 2009

21. In the end its all about...
Friday, January 30, 2009

22. Clear Understanding
Clear Communication
Friday, January 30, 2009

23. Friday, January 30, 2009

24. AND ...
Friday, January 30, 2009

25. Trust
Falando em Agile 2008 -- Updated: Jan 30, 2009
Friday, January 30, 2009

26. Trust
Falando em Agile 2008 -- Updated: Jan 30, 2009
Friday, January 30, 2009

27. 1 Origin and principles
Friday, January 30, 2009

28. 2
Friday, January 30, 2009

29. Roles
Friday, January 30, 2009

30. The Boss
Friday, January 30, 2009

31. The Boss
Friday, January 30, 2009

32. with Scrum
The focus is on Team Work
Friday, January 30, 2009

33. Roles Product Owner
http://www.flickr.com/photos/toechsner/2864422157/
O Time
ScrumMaster
http://www.flickr.com/photos/roger_g1/317671375/
http://www.flickr.com/photos/digital_stability/61466858/
Friday, January 30, 2009

34. The Product Owner
Friday, January 30, 2009

35. Product owner
Define the features for the product
Decide on release dates and its contents
Responsible for the ROI, audience, etc.
Prioritize features according to market and strategic value
Interact with stakeholders and customers to define the
Product backlog
Adjust!features and prioritize every sprint, as needed!
Accept or reject work results during the Sprint Review
Friday, January 30, 2009

36. ScrumMaster
Friday, January 30, 2009

37. Protect values and principles
Removes impediments
Keep the team fully functional and productive
Enable cooperation
Shield the team from “dark forces”
Facilitates integration
He does NOT allocate tasks
Friday, January 30, 2009

38. The Team
Friday, January 30, 2009

39. The team
Typically 5-9 people
Cross-functional:
Programmers, testers, UED, etc.
Full-time allocated
Self-organized
Responsible for the quality
Estimates the complexity
Friday, January 30, 2009

40. Pigs X Chickens
Friday, January 30, 2009

41. 1 Origem e princípios
2 Roles
Friday, January 30, 2009

42. 3
Friday, January 30, 2009

43. Meetings
Friday, January 30, 2009

44. Meetings
Scrum Flow
Sprint Planning
Sprint Review
Sprint Retrospective
Daily Scrums
Friday, January 30, 2009

45. SCRUM Flow
Scrum Flow
Friday, January 30, 2009

46. Scrum Meetings
Time
Friday, January 30, 2009

47. Sprint Planning
What are we going to build?
1
How are going to build it?
2
Friday, January 30, 2009

48. Sprint Planning
Time
Boxed
A PO explains the scope max 4
h
B Team estimates the complexity
C Team chooses the Sprint backlog
D Team writes the tasks for each story
Friday, January 30, 2009

49. PO
Friday, January 30, 2009

50. Friday, January 30, 2009

51. Better
communication
To avoid things like this...
Friday, January 30, 2009

52. Friday, January 30, 2009

53. Sprint Review
Team demo what was accomplished during the sprint
Each developer demo a story
Informal, no slides
Whole team participates
Anyone is invited to participate (but only Pigs can talk)
Time
Boxed
max 2
h
Friday, January 30, 2009

54. Friday, January 30, 2009

55. Friday, January 30, 2009

56. Sprint Retrospectiva
What was cool?
What can we improve?
What the team can solve?
What the company needs to solve?
Only for PO, SM and Team
Time
Boxed
max 2
h
Friday, January 30, 2009

57. Daily Scrum
1 What I did since the last meeting?
What I will do until the next meeting?
2
Any impediments?
3
Friday, January 30, 2009

58. Friday, January 30, 2009

59. Friday, January 30, 2009

60. 1 Origins and principles
2 Roles
3 Meetings
Friday, January 30, 2009

61. 4
Friday, January 30, 2009

62. Artifacts
Friday, January 30, 2009

63. Friday, January 30, 2009
Product Backlog
http://www.flickr.com/photos/aeror/2312354037//74150717/

64. Sprint Backlog
The product requirements
Everything (ideas, features, epics)
Expressed in User Stories
PO keeps it organized
Always prioritized and estimated
Friday, January 30, 2009

65. A sample product backlog
Backlog item Estimate
Allow a guest to make a reservation 3
As a guest, I want to cancel a reservation. 5
As a guest, I want to change the dates of a 3
reservation.
As a hotel employee, I can run RevPAR 8
reports (revenue-per-available-room)
Improve exception handling 8
... 30
... 50
Friday, January 30, 2009

66. User Story
I as a<client>
want <feature>
because <ROI>
Friday, January 30, 2009

67. User Story
Acceptance Criteria
Friday, January 30, 2009

68. Uncertainty Cone
Barry Boehm
Friday, January 30, 2009

69. Uncertainty Cone
Friday, January 30, 2009

70. Uncertainty Cone
Friday, January 30, 2009

71. PB Iceberg
Friday, January 30, 2009

72. PB Iceberg We
b
r 2.0
Friday, January 30, 2009

73. Sprint Backlog
http://www.flickr.com/photos/aeror/2312354037//74150717/
http://www.flickr.com/photos/x180/469281131/
Friday, January 30, 2009

74. Sprint Backlog
User Stories selected by the Team
Will be built in next 15 days
Fully Estimated
Divided in daily tasks
Friday, January 30, 2009

75. No changes during
the Sprint
Friday, January 30, 2009

76. Definition of
DONE
Friday, January 30, 2009

77. DONE
“DONE” or “NOT DONE”
!
Avoids de 90% Syndrome
!
Code produced, commented,
!
checked in and run against current
version in source control and meeting
development standards
Peer reviewed (or produced with pair
!
programming)
Builds without errors (CI)
!
Friday, January 30, 2009

78. DONE
Unit tests written and passing (TDD)
!
Deployed to system test environment and
!
passed system tests
Passed UAT (User Acceptance Testing)
!
(Selenium)
Any build/deployment/configuration changes
!
implemented/documented/communicated
Relevant documentation/diagrams produced
!
and/or updated
Paranoid Compliant
!
Friday, January 30, 2009

79. complexity points
0
20
40
60
80
100
4/29/08
Friday, January 30, 2009
5/6/08
5/13/08
Burndown Chart
5/20/08
5/24/08

80. Burn up Chart
A sprint burn up chart
117.0
100
97.5
78.0
Number of tasks
58.5
39.0
19.5
0
4/29/08
5/6/08
5/13/08
5/20/08
5/24/08
Friday, January 30, 2009

81. Friday, January 30, 2009

82. Friday, January 30, 2009

83. 1 Origins and Principles
2 Roles
3 Meetings
4 Artifacts
Friday, January 30, 2009

84. Books
Friday, January 30, 2009

85. Reading List
Agile Software Development with Scrum by Ken
Schwaber and Mike Beedle
Agile Project Management with Scrum by Ken Schwaber
Lean software development by Mary Poppendieck
Agile and Iterative Development: A Manager’s
Guide by Craig Larman
Agile Estimating and Planning by Mike Cohn
Agile Retrospectives by Esther Derby and Diana Larsen
Scrum and The Enterprise by Ken Schwaber
Practices of an Agile Developer by Venkat Subramaniam
and Andy Hunt
Test Driven Development: By Example by Kent Back
Getting Real by 37Signals
Friday, January 30, 2009

86. Questions
Friday, January 30, 2009

87. Thank you
Blog: http://www.acarlos.com.br/blog/
Twitter: acarlos1000
e-mail: acarlos@yahoo-inc.com
Friday, January 30, 2009