Post on 17-May-2015
description
transcript
DART PROJECT UPDATE
Design Team Plans & Expectations
On TrackDesign Team Plans and Expectations
Aug 2009 Design and Development
Sept 2010
Syst
em
D
evelo
pm
en
t
Constituent Management(Aug 09 – Jan 10)
ESTIMATED TIMING FOR DESIGN TEAMS
Aug 2009 Design and Development
Sept 2010
Syst
em
D
evelo
pm
en
t
Revenue Management(Oct 05 – March 10)
Constituent Management(Aug 09 – Jan 10)
ESTIMATED TIMING FOR DESIGN TEAMS
Aug 2009 Design and Development
Sept 2010
Syst
em
D
evelo
pm
en
t
Revenue Management(Oct 05 – March 10)
Campaign / Annual Giving / Prospect Research (Jan 10 – May 10)
Constituent Management(Aug 09 – Jan 10)
ESTIMATED TIMING FOR DESIGN TEAMS
Aug 2009 Design and Development
Sept 2010
Syst
em
D
evelo
pm
en
t
Revenue Management(Oct 05 – March 10)
Campaign / Annual Giving / Prospect Research (Jan 10 – May 10)
Prospect Mgmt / Gift Plan / Stewardship (March 10 – July 10)
Constituent Management(Aug 09 – Jan 10)
ESTIMATED TIMING FOR DESIGN TEAMS
Aug 2009 Design and Development
Sept 2010
Syst
em
D
evelo
pm
en
t
Revenue Management(Oct 05 – March 10)
Campaign / Annual Giving / Prospect Research (Jan 10 – May 10)
Prospect Mgmt / Gift Plan / Stewardship (March 10 – July 10)
Event Mgmt / Online(May 10 – Sept 10)
Constituent Management(Aug 09 – Jan 10)
ESTIMATED TIMING FOR DESIGN TEAMS
VOLUNTEER RECRUITMENT CONTINUES
Reviewing existing volunteers
VOLUNTEER RECRUITMENT CONTINUES
Reviewing existing volunteers Considering several factors:
VOLUNTEER RECRUITMENT CONTINUES
Reviewing existing volunteers Considering several factors:
who has the right business knowledge
VOLUNTEER RECRUITMENT CONTINUES
Reviewing existing volunteers Considering several factors:
who has the right business knowledgewho has the right technical knowledge
VOLUNTEER RECRUITMENT CONTINUES
Reviewing existing volunteers Considering several factors:
who has the right business knowledgewho has the right technical knowledgewho has demonstrated the ability and
interest to think beyond what we’re doing today in DAC
VOLUNTEER RECRUITMENT CONTINUES
Reviewing existing volunteers Considering several factors:
who has the right business knowledgewho has the right technical knowledgewho has demonstrated the ability and
interest to think beyond what we’re doing today in DAC
Evaluating whether we have sufficient diversity of representation from schools, colleges, and units
DESIGN TEAM RESPONSIBILITIES AND EFFORT
DESIGN AND DEVELOPMENT STAGES
Pre-Design Activities
Heaviest time commitment by
design team members
“BTP” = Blackbaud Technical Preview• A package of the code, customizations, conversion data, and configurations for
each functional area• Delivered to U-M for testing and review
BUSINESS PROCESS ANALYSIS
Product/process training and methodology
3-4 weeks, 40-55% time commitment
BUSINESS PROCESS ANALYSIS
Product/process training and methodology Work with BSAs to document current business processes
3-4 weeks, 40-55% time commitment
BUSINESS PROCESS ANALYSIS
Product/process training and methodology Work with BSAs to document current business processes Review, re-assess, and prioritize Fit-Gap Requirements
3-4 weeks, 40-55% time commitment
BUSINESS PROCESS ANALYSIS
Product/process training and methodology Work with BSAs to document current business processes Review, re-assess, and prioritize Fit-Gap Requirements Develop desired workflows for new system
3-4 weeks, 40-55% time commitment
BUSINESS PROCESS ANALYSIS
Product/process training and methodology Work with BSAs to document current business processes Review, re-assess, and prioritize Fit-Gap Requirements Develop desired workflows for new system Policy review
3-4 weeks, 40-55% time commitment
USER SCENARIO DEVELOPMENT
3-5 weeks, 40-55% time commitment
Draft user scenarios for Blackbaud – these provide the “blueprint” for system design
USER SCENARIO DEVELOPMENT
3-5 weeks, 40-55% time commitment
Draft user scenarios for Blackbaud – these provide the “blueprint” for system design
Finalize or escalate policy decisions
USER SCENARIO DEVELOPMENT
3-5 weeks, 40-55% time commitment
Draft user scenarios for Blackbaud – these provide the “blueprint” for system design
Finalize or escalate policy decisions Assemble data output needs (reporting, etc.)
SPRINT DESIGN CYCLES
Finalize design timeline, requirements to be addressed
12-16 weeks, 0-25% commitment
SPRINT DESIGN CYCLES
Finalize design timeline, requirements to be addressed Review periodic demos of design concepts
12-16 weeks, 0-25% commitment
SPRINT DESIGN CYCLES
Finalize design timeline, requirements to be addressed Review periodic demos of design concepts Develop testing scenarios for end of design cycle (BTP)
12-16 weeks, 0-25% commitment
SPRINT DESIGN CYCLES
Finalize design timeline, requirements to be addressed Review periodic demos of design concepts Develop testing scenarios for end of design cycle (BTP) Work on data outputs, reporting, and analytics
12-16 weeks, 0-25% commitment
BLACKBAUD TECHNICAL PREVIEW (BTP)
3 weeks, 25-50% time commitment
Preview, test, and provide feedback on all newly incorporated design elements
Sign off on final functional area design
THERE’S STILL TIME…
VOLUNTEER TODAY!
Target dates for other design teams Revenue Management (Oct 05-March 10) Campaign/Annual Giving/Prospect Research (Jan 10-May
10) Prospect Mgmt / Gift Plan/ Stewardship (March 10-July 10) Event Mgmt / Online (May 10-Sept 10)
Volunteer positions are still available for some teams
Community Resource Group
HOW TO VOLUNTEER:
Open to everyone Supervisor approval
recommended Review the informatio
n packet Complete the sign up
form Send it to:
Cassidy Eaton3590 Varsity DriveAnn Arbor, MI 48108-2228caseaton@umich.edu
Supervisor approval required
Review the information packet
Contact Karen Isble for more time/effort specifics: ktisble@umich.edu
Share it with your supervisor and/or others in your unit
Complete the sign up form Send it to:
Cassidy Eaton3590 Varsity DriveAnn Arbor, MI 48108-2228caseaton@umich.edu
Dev / Fin Community Resource Group
Design Team Positions