1. Agile CRM Applying the Scrum Methodology for Deployment Neil Benson

2. Rome 31 January -1 February 60 minutes

3. Rome 31 January -1 February Save your CRM project

4. Rome 31 January -1 February from disaster

5. Rome 31 January -1 February

11. request for proposal

12. Rome 31 January -1 February 30 pages

13. Rome 31 January -1 February my initial estimate

14. Rome 31 January -1 February 300 days

15. Rome 31 January -1 February

16. 300 users

17. Rome 31 January -1 February Analysis Design Development Testing Operation

18. Rome 31 January -1 February 6 weeks’ analysis

19. Rome 31 January -1 February

21. j@rg0n

22. Rome 31 January -1 February 1.Entity 2.Attribute 3.Workflow

23. Rome 31 January -1 February

24. mi__ing

25. Rome 31 January -1 February

29. 2 weeks

30. Rome 31 January -1 February

34. 50

35. Rome 31 January -1 February Microsoft Microsoft Dynamics CRMMicrosoft Dynamics CRM

36. Rome 31 January -1 February Analysis Design Development Testing Operation

37. Rome 31 January -1 February

38. Source: http://www.versionone.com/state_of_agile_development_survey/11/

39. Rome 31 January -1 February product owner vision product backlog sprint backlog sprint planning meeting scrum team daily scrum meeting sprint review meeting product increment sprint retrospective 1 to 4 week sprint

40. Rome 31 January -1 February product owner

41. Rome 31 January -1 February business expert

42. Rome 31 January -1 February influential

43. Rome 31 January -1 February trusted

44. Rome 31 January -1 February available

45. Rome 31 January -1 February

46. changes during sprint

47. Rome 31 January -1 February product backlog

48. Rome 31 January -1 February prioritized

49. Rome 31 January -1 February product backlog items

50. Rome 31 January -1 February 1.stories 2.bugs 3.chores

51. Rome 31 January -1 February

52. epics

53. Rome 31 January -1 February big

54. Rome 31 January -1 February hairy

55. Rome 31 January -1 February

56. Lead Nurturing “As the VP marketing, leads are nurtured, so that our timing is perfect.”

57. Rome 31 January -1 February just in time epic refinement

58. Rome 31 January -1 February user stories

59. Rome 31 January -1 February Story Title “As a [type of user], I can [do something useful], So that [I achieve some goal].”

60. Rome 31 January -1 February Lead Notification “As a sales representative, I am notified when a new lead has been assigned to me, so that I can respond to enquiries within 1 hour.”

61. Rome 31 January -1 February reminder to have a conversation

62. Rome 31 January -1 February conditions of satisfaction

63. Rome 31 January -1 February Lead must include: person’s name, company name, lead source, and a phone number or email address

64. Rome 31 January -1 February sprint planning meeting product backlog sprint backlog scrum team

65. Rome 31 January -1 February up to 4 hours

66. Rome 31 January -1 February estimation

67. Rome 31 January -1 February story points

68. Rome 31 January -1 February modified Fibonacci scale

69. Rome 31 January -1 February planning poker

70. Rome 31 January -1 February choose stories

71. Rome 31 January -1 February theme

72. Rome 31 January -1 February ItemTypePoints As a user, I can indicate that an asset has been replaced by another asset.Story2 As a user, I can print a list of loan records with a particular loan status.Story1 As a user, when I update a product the changes should cascade to all assets of that product. Story3 As a user, I can generate multiple jobs at once.Story5 Test whether the CRM 2011 Data Import Wizard can import resolved cases.Chore0 Auto-number for jobs is not working.Bug0

73. Rome 31 January -1 February sprint backlog

74. Rome 31 January -1 February sprint daily scrum meeting 1 to 4 week sprint

75. Rome 31 January -1 February time-boxed iteration

76. Rome 31 January -1 February 1 to 4 weeks

77. Rome 31 January -1 February 2 weeks works well

78. Rome 31 January -1 February deadline sacred

79. Rome 31 January -1 February

80. drop stories

81. Rome 31 January -1 February don’t move deadline

82. Rome 31 January -1 February when is a story done?

83. Rome 31 January -1 February meets coding standards system tested unit tested integration tested performance tested regression tested technical design updated user guide updated peer reviewed

84. Rome 31 January -1 February meets coding standards system tested unit tested integration tested performance tested regression tested technical design updated user guide updated peer reviewed

85. Rome 31 January -1 February completeness velocity

86. Rome 31 January -1 February velocity = points points sprint

87. Rome 31 January -1 February

88. ScrumMaster

89. Rome 31 January -1 February expert in Scrum

90. Rome 31 January -1 February outside consultant

91. Rome 31 January -1 February remove impediments

92. Rome 31 January -1 February coach

93. Rome 31 January -1 February facilitate

94. Rome 31 January -1 February project manager

95. Rome 31 January -1 February Scrum team

96. Rome 31 January -1 February 5 to 9 members

97. Rome 31 January -1 February dedicated

98. Rome 31 January -1 February self-organizing

99. Rome 31 January -1 February rules

100. Rome 31 January -1 February no titles

101. Rome 31 January -1 February commit

102. Rome 31 January -1 February daily Scrum meeting

103. Rome 31 January -1 February 15 minutes

104. Rome 31 January -1 February 1.What did you do yesterday? 2.What will you do today? 3.What, if anything, is in your way?

105. Rome 31 January -1 February sprint review meeting product increment

106. Rome 31 January -1 February demo

107. Rome 31 January -1 February product owner & stakeholders

108. Rome 31 January -1 February collect feedback

109. Rome 31 January -1 February re-prioritize

110. Rome 31 January -1 February sprint retrospective

111. Rome 31 January -1 February inspect & adapt

112. Rome 31 January -1 February 1.stop doing? 2.keep doing? 3.start doing?

113. Rome 31 January -1 February

114. electronic vetting system

115. Rome 31 January -1 February

117. successful!

118. Rome 31 January -1 February

121. medical device asset management

122. Rome 31 January -1 February

126. product owner Scrum team

127. Rome 31 January -1 February 2-week sprints x10

128. Rome 31 January -1 February

129. every project?

130. Rome 31 January -1 February no

131. Rome 31 January -1 February

136. Analysis Design Development Testing Operation

137. Rome 31 January -1 February

138. scrumalliance.org

139. Rome 31 January -1 February mountaingoatsoftware.com

140. Rome 31 January -1 February

144. agilescout.com

145. Rome 31 January -1 February try it!

146. Rome 31 January -1 February thank you

147. Rome 31 January -1 February Neil Benson neil.benson@slalom.com linkedin.com/in/neilbenson @customery customery.com