Agile CRM Applying the Scrum Methodology for Deployment

Agile CRM Applying the Scrum Methodology for Deployment Neil Benson

60 minutes Rome 31 January -1 February

Save your CRM project Rome 31 January -1 February

from disaster Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

request for proposal Rome 31 January -1 February

30 pages Rome 31 January -1 February

my initial estimate Rome 31 January -1 February

300 days Rome 31 January -1 February

Rome 31 January -1 February

300 users Rome 31 January -1 February

Analysis Design Development Testing Operation Rome 31 January -1 February

6 weeks’ analysis Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

j@rg 0 n Rome 31 January -1 February

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

Rome 31 January -1 February

mi__ing Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

2 weeks Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

50 Rome 31 January -1 February

Microsoft Micros oft Dyna mics CRM Rome 31 January -1 February

Analysis Design Development Testing Operation Rome 31 January -1 February

Rome 31 January -1 February

Source: http: //www. versionone. com/state_of_agile_development_survey/11/ Rome 31 January -1 February

daily scrum meeting sprint review meeting sprint planni ng meetin g visio n product owner scrum team 1 to 4 week sprint backlo g product increment sprint retrospective produc t backlo. Rome 31 January -1 February g

product owner Rome 31 January -1 February

business expert Rome 31 January -1 February

influential Rome 31 January -1 February

trusted Rome 31 January -1 February

available Rome 31 January -1 February

Rome 31 January -1 February

changes during sprint Rome 31 January -1 February

product backlog Rome 31 January -1 February

prioritized Rome 31 January -1 February

product backlog items Rome 31 January -1 February

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

Rome 31 January -1 February

epics Rome 31 January -1 February

big Rome 31 January -1 February

hairy Rome 31 January -1 February

Rome 31 January -1 February

Lead Nurturing “As the VP marketing, leads are nurtured, so that our timing is perfect. ” Rome 31 January -1 February

just in time epic refinement Rome 31 January -1 February

user stories Rome 31 January -1 February

Story Title “As a [type of user], I can [do something useful], So that [I achieve some goal]. ” 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. ” Rome 31 January -1 February

reminder to have a conversation Rome 31 January -1 February

conditions of satisfaction Rome 31 January -1 February

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

sprint planning meeting scrum team produc t backlo Rome 31 January -1 February g sprint backlo g

up to 4 hours Rome 31 January -1 February

estimation Rome 31 January -1 February

story points Rome 31 January -1 February

modified Fibonacci scale Rome 31 January -1 February

planning poker Rome 31 January -1 February

choose stories Rome 31 January -1 February

theme Rome 31 January -1 February

Item Type As a user, I can indicate that an asset has been replaced by another asset. Story 2 As a user, I can print a list of loan records with a particular loan status. Story 1 As a user, when I update a product the changes should cascade to all assets of that product. Story 3 As a user, I can generate multiple jobs at once. Story 5 Test whether the CRM 2011 Data Import Wizard can import resolved cases. Chore 0 Auto-number for jobs is not working. Bug 0 Rome 31 January -1 February Point s

sprint backlog Rome 31 January -1 February

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

time-boxed iteration Rome 31 January -1 February

1 to 4 weeks Rome 31 January -1 February

2 weeks works well Rome 31 January -1 February

deadline sacred Rome 31 January -1 February

Rome 31 January -1 February

drop stories Rome 31 January -1 February

don’t move deadline Rome 31 January -1 February

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

system d e t s e tested unit t meets ormanc f r e p coding tested e standards n o i r s e s pe egre r d e w t e s i e v t e r technical integration design tested updated e d i u user g d e t a d p u Rome 31 January -1 February

system d e t s e tested unit t meets ormanc f r e p coding tested e standards n o i r s e s pe egre r d e w t e s i e v t e r technical integration design tested updated e d i u user g d e t a d p u Rome 31 January -1 February

completeness velocity Rome 31 January -1 February

points velocity = points sprint Rome 31 January -1 February

35 Velocity 30 33 30 29 25 27 26 27 22 20 22 19 15 14 10 5 0 1 2 3 4 5 6 Sprint Rome 31 January -1 February 7 8 9 10

Scrum. Master Rome 31 January -1 February

expert in Scrum Rome 31 January -1 February

outside consultant Rome 31 January -1 February

remove impediments Rome 31 January -1 February

coach Rome 31 January -1 February

facilitate Rome 31 January -1 February

project manager Rome 31 January -1 February

Scrum team Rome 31 January -1 February

5 to 9 members Rome 31 January -1 February

dedicated Rome 31 January -1 February

self-organizing Rome 31 January -1 February

rules Rome 31 January -1 February

no titles Rome 31 January -1 February

commit Rome 31 January -1 February

daily Scrum meeting Rome 31 January -1 February

15 minutes 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? Rome 31 January -1 February

sprint review meeting product increment Rome 31 January -1 February

demo Rome 31 January -1 February

product owner & stakeholders Rome 31 January -1 February

collect feedback Rome 31 January -1 February

re-prioritize Rome 31 January -1 February

sprint retrospective Rome 31 January -1 February

inspect & adapt Rome 31 January -1 February

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

Rome 31 January -1 February

electronic vetting system Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

successful! Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

medical device asset management Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

product owner Scrum team Rome 31 January -1 February

x 10 2 -week sprints Rome 31 January -1 February

Rome 31 January -1 February

every project? Rome 31 January -1 February

no Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Analysis Design Development Testing Operation Rome 31 January -1 February

Rome 31 January -1 February

scrumalliance. org Rome 31 January -1 February

mountaingoatsoftware. com Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

Rome 31 January -1 February

agilescout. com Rome 31 January -1 February

try it! Rome 31 January -1 February

thank you Rome 31 January -1 February

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