Agile CRM Applying the Scrum Methodology for Deployment Neil Benson.

Slides:



Advertisements
Similar presentations
Iterative Development: Done Simply Emily Lynema NCSU Libraries Code4Lib 2010.
Advertisements

Agile Development Primer – Using Roundtable TSMS in an Agile Shop Michael G. Solomon Solomon Consulting Inc.
“Something called agile”
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Agenda −Scrum with TFS 2010 using MSF for Agile 5.0 −Planning the Project −How do you plan the project? −Project planning in TFS 2010 −Planning a Sprint.
Agile 101.
ECE44x SCRUM Overview slides adapted from Marty Stepp
Agile Project Management with Scrum
Agile Development and Data With Scrum and TDD Andy Leonard VSTeamSystemCentral.com With thanks to Brian Knight, SQL Server MVP SQLServerCentral.com.
Process and tools Individuals and interactions over Following a plan Responding to change over Comprehensive documentation Working software over Contract.
An Introduction to Agile SCRUM Methodology
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
NAUG NAUG Knowledge Evening – th February 2007.
Introduction to Scrum.
Scrum 1.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Muthu Swamy S, APSM, PMP, CSM, PM-2008 Friday, October 1, 2010
Rules of the Game  Loosely based upon the TV show, “Who wants to be a millionaire.®”  Once the question is read, you will have 30 seconds to discuss.
Agile development By Sam Chamberlain. First a bit of history..
Agile Methodologies for Project Management By – Komal Mehta.
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
By: Jean Ballard and Kurt Rasmussen
Tuesday, June 8 th, Agile Development-Successful Delivery & Implementing Across the Enterprise.
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
Release and Iteration Planning September 13, 2008.
SCRU M Scrum Overview - Commonly Used Terms Ali Qureshi, parorrey.com – 31 st Aug, 2015 PI Media parorrey.com.
Stephen Chief Strategy Officer Telerik
Process is continuously improving Have Definition of Done (DoD) DoD achievable within each iteration Team respects DoD The bottom line Delivering working,
Copyright © 2012 by Mark J. Sebern Scrum Overview (from
OFFICE OF INFORMATION AND TECHNOLOGY Mobile Applications Scrum Framework November 21, :00 am (EST) Seal of the U.S. Department of Veterans Affairs.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Het einde van het beroep van tester - Wat Agile, DevOps en Scrum betekenen voor het testvak -
Agile Information Management Development. Agile Project Management Characteristics  Acceptance and even welcome of changing requirements  Incremental.
What Is Agile? Agile is a group of software development methodologies Scrum Extreme Programming (XP) Lean Etc. Key Characteristics: Small increments Adaptive.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
SCRUM.
Using Scrum to Improve Teamwork, Communication, Quality and Speed
Lecture 5 17/9/15. What is Scrum? Scrum is one of the leading agile software development processes Agile framework for completing complex projects. Originally.
Agile 101. Feasibility Study SDLC – What is it? Systems Development Life Cycle: The most commonly used, and generally accepted, project management approach..
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
The Agile Manifesto Some thought starters for Ogilvy on how to work with Agile and SCRUM approaches to managing projects.
Introduction to Agile. Introduction Who is this guy?
Agile Project. Agile - Project proj·ect präj ˌ ekt noun an individual or collaborative enterprise that is carefully planned and designed to achieve a.
Software Quality Assurance Chip Ene, February 14, 2015.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Scrum Process Proposal 1/16/09. User Stories Scrum Process Proposal.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Change your look and feel to how you work! Let’s SCRUM Change your look and feel to how you work!
Agile Project Management Methodology Scrum Overview
Scrum.
Wael Ellithy, Ph.D. Arx ICT
SCRUM.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Scrum Management
By: By: Agile Scrum Master Online Training.
Product Backlog List of things that needs to be done to make the product come into existence 
Project Management and the Agile Manifesto
Scrum MODULE 3 – Part 3.
Summarizing Our Models to Date
Scrum Overview.
SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES
Introduction to Agile Blue Ocean Workshops.
Scrum in Action.
Sprints.
Agile product development
Presentation transcript:

Agile CRM Applying the Scrum Methodology for Deployment Neil Benson

Rome 31 January -1 February 60 minutes

Rome 31 January -1 February Save your CRM project

Rome 31 January -1 February from disaster

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

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 1.Entity 2.Attribute 3.Workflow

Rome 31 January -1 February

mi__ing

Rome 31 January -1 February

2 weeks

Rome 31 January -1 February

50

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

Rome 31 January -1 February Analysis Design Development Testing Operation

Rome 31 January -1 February

Source:

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

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

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

epics

Rome 31 January -1 February big

Rome 31 January -1 February hairy

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 address

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

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

Rome 31 January -1 February sprint backlog

Rome 31 January -1 February sprint daily scrum meeting 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

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 meets coding standards system tested unit tested integration tested performance tested regression tested technical design updated user guide updated peer reviewed

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

Rome 31 January -1 February completeness velocity

Rome 31 January -1 February velocity = points points sprint

Rome 31 January -1 February

ScrumMaster

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

electronic vetting system

Rome 31 January -1 February

successful!

Rome 31 January -1 February

medical device asset management

Rome 31 January -1 February

product owner Scrum team

Rome 31 January -1 February 2-week sprints x10

Rome 31 January -1 February

every project?

Rome 31 January -1 February no

Rome 31 January -1 February

Analysis Design Development Testing Operation

Rome 31 January -1 February

scrumalliance.org

Rome 31 January -1 February mountaingoatsoftware.com

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 customery.com