Recommended
More Related Content
Similar to Tour de DART Sept 2009
Similar to Tour de DART Sept 2009 (20)
More from UM_DART
More from UM_DART (17)
Recently uploaded
Recently uploaded (20)
Tour de DART Sept 2009
- 1. DART Project Update Design Team Plans & Expectations On Track Design Team Plans and Expectations
- 2. Estimated timing for design teams Sept 2010 Aug 2009 Design and Development Constituent Management (Aug 09 – Jan 10) System Development
- 3. Estimated timing for design teams Sept 2010 Aug 2009 Design and Development Constituent Management (Aug 09 – Jan 10) Revenue Management (Oct 05 – March 10) System Development
- 4. Estimated timing for design teams Sept 2010 Aug 2009 Design and Development Constituent Management (Aug 09 – Jan 10) Revenue Management (Oct 05 – March 10) Campaign / Annual Giving / Prospect Research (Jan 10 – May 10) System Development
- 5. Estimated timing for design teams Sept 2010 Aug 2009 Design and Development Constituent Management (Aug 09 – Jan 10) Revenue Management (Oct 05 – March 10) Campaign / Annual Giving / Prospect Research (Jan 10 – May 10) System Development Prospect Mgmt / Gift Plan / Stewardship (March 10 – July 10)
- 6. Estimated timing for design teams Sept 2010 Design and Development Aug 2009 Constituent Management (Aug 09 – Jan 10) Revenue Management (Oct 05 – March 10) Campaign / Annual Giving / Prospect Research (Jan 10 – May 10) System Development Prospect Mgmt / Gift Plan / Stewardship (March 10 – July 10) Event Mgmt / Online (May 10 – Sept 10)
- 7. Volunteer Recruitment Continues Reviewing existing volunteers
- 8. Volunteer Recruitment Continues Reviewing existing volunteers Considering several factors:
- 9. Volunteer Recruitment Continues Reviewing existing volunteers Considering several factors: who has the right business knowledge
- 10. Volunteer Recruitment Continues Reviewing existing volunteers Considering several factors: who has the right business knowledge who has the right technical knowledge
- 11. Volunteer Recruitment Continues Reviewing existing volunteers Considering several factors: who has the right business knowledge who has the right technical knowledge who has demonstrated the ability and interest to think beyond what we’re doing today in DAC
- 12. Volunteer Recruitment Continues Reviewing existing volunteers Considering several factors: who has the right business knowledge who has the right technical knowledge who 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
- 13. Design Team Responsibilities and Effort
- 16. Business Process Analysis 3-4 weeks, 40-55% time commitment Product/process training and methodology Work with BSAs to document current business processes
- 17. Business Process Analysis 3-4 weeks, 40-55% time commitment Product/process training and methodology Work with BSAs to document current business processes Review, re-assess, and prioritize Fit-Gap Requirements
- 18. Business Process Analysis 3-4 weeks, 40-55% time commitment 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
- 19. Business Process Analysis 3-4 weeks, 40-55% time commitment 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
- 22. Finalize or escalate policy decisions
- 24. Sprint Design Cycles 12-16 weeks, 0-25% commitment Finalize design timeline, requirements to be addressed Review periodic demos of design concepts
- 25. Sprint Design Cycles 12-16 weeks, 0-25% commitment Finalize design timeline, requirements to be addressed Review periodic demos of design concepts Develop testing scenarios for end of design cycle (BTP)
- 26. Sprint Design Cycles 12-16 weeks, 0-25% commitment 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
- 29. 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
- 32. Review the information packet
- 33. Complete the sign up form
- 35. Review the information packet
- 36. Contact Karen Isble for more time/effort specifics: ktisble@umich.edu
- 37. Share it with your supervisor and/or others in your unit
- 38. Complete the sign up form
- 39. Send it to:Cassidy Eaton 3590 Varsity Drive Ann Arbor, MI 48108-2228 caseaton@umich.edu
Editor's Notes
- As-Is: During this period and before, high-level As-Is workflows will be reviewed and developed by the Design Team (documented by BSAs). The fit-gap priorities for that functional area will also be reviewed and re-ordered, as needed. Likely to require 10-15 hours of meetings per week. May be completed in 1 week or 2, depending on the number of workflows and priorities for that functional area.To-Be: During this period, the Design Team will work in meetings with Blackbaud design staff to review the As-Is workflows, discuss desired workflow changes, compare with product functionality and BB-considered "best practices" and determine where processes can/should be altered. Team will also meet with and gather feedback as available from members of the CRG. Likely to require 12-20 hours of meetings per week, depending on the number of requirements and workflows.
- As-Is: During this period and before, high-level As-Is workflows will be reviewed and developed by the Design Team (documented by BSAs). The fit-gap priorities for that functional area will also be reviewed and re-ordered, as needed. Likely to require 10-15 hours of meetings per week. May be completed in 1 week or 2, depending on the number of workflows and priorities for that functional area.To-Be: During this period, the Design Team will work in meetings with Blackbaud design staff to review the As-Is workflows, discuss desired workflow changes, compare with product functionality and BB-considered "best practices" and determine where processes can/should be altered. Team will also meet with and gather feedback as available from members of the CRG. Likely to require 12-20 hours of meetings per week, depending on the number of requirements and workflows.
- As-Is: During this period and before, high-level As-Is workflows will be reviewed and developed by the Design Team (documented by BSAs). The fit-gap priorities for that functional area will also be reviewed and re-ordered, as needed. Likely to require 10-15 hours of meetings per week. May be completed in 1 week or 2, depending on the number of workflows and priorities for that functional area.To-Be: During this period, the Design Team will work in meetings with Blackbaud design staff to review the As-Is workflows, discuss desired workflow changes, compare with product functionality and BB-considered "best practices" and determine where processes can/should be altered. Team will also meet with and gather feedback as available from members of the CRG. Likely to require 12-20 hours of meetings per week, depending on the number of requirements and workflows.
- As-Is: During this period and before, high-level As-Is workflows will be reviewed and developed by the Design Team (documented by BSAs). The fit-gap priorities for that functional area will also be reviewed and re-ordered, as needed. Likely to require 10-15 hours of meetings per week. May be completed in 1 week or 2, depending on the number of workflows and priorities for that functional area.To-Be: During this period, the Design Team will work in meetings with Blackbaud design staff to review the As-Is workflows, discuss desired workflow changes, compare with product functionality and BB-considered "best practices" and determine where processes can/should be altered. Team will also meet with and gather feedback as available from members of the CRG. Likely to require 12-20 hours of meetings per week, depending on the number of requirements and workflows.
- As-Is: During this period and before, high-level As-Is workflows will be reviewed and developed by the Design Team (documented by BSAs). The fit-gap priorities for that functional area will also be reviewed and re-ordered, as needed. Likely to require 10-15 hours of meetings per week. May be completed in 1 week or 2, depending on the number of workflows and priorities for that functional area.To-Be: During this period, the Design Team will work in meetings with Blackbaud design staff to review the As-Is workflows, discuss desired workflow changes, compare with product functionality and BB-considered "best practices" and determine where processes can/should be altered. Team will also meet with and gather feedback as available from members of the CRG. Likely to require 12-20 hours of meetings per week, depending on the number of requirements and workflows.
- As-Is: During this period and before, high-level As-Is workflows will be reviewed and developed by the Design Team (documented by BSAs). The fit-gap priorities for that functional area will also be reviewed and re-ordered, as needed. Likely to require 10-15 hours of meetings per week. May be completed in 1 week or 2, depending on the number of workflows and priorities for that functional area.To-Be: During this period, the Design Team will work in meetings with Blackbaud design staff to review the As-Is workflows, discuss desired workflow changes, compare with product functionality and BB-considered "best practices" and determine where processes can/should be altered. Team will also meet with and gather feedback as available from members of the CRG. Likely to require 12-20 hours of meetings per week, depending on the number of requirements and workflows.
- As-Is: During this period and before, high-level As-Is workflows will be reviewed and developed by the Design Team (documented by BSAs). The fit-gap priorities for that functional area will also be reviewed and re-ordered, as needed. Likely to require 10-15 hours of meetings per week. May be completed in 1 week or 2, depending on the number of workflows and priorities for that functional area.To-Be: During this period, the Design Team will work in meetings with Blackbaud design staff to review the As-Is workflows, discuss desired workflow changes, compare with product functionality and BB-considered "best practices" and determine where processes can/should be altered. Team will also meet with and gather feedback as available from members of the CRG. Likely to require 12-20 hours of meetings per week, depending on the number of requirements and workflows.
- As-Is: During this period and before, high-level As-Is workflows will be reviewed and developed by the Design Team (documented by BSAs). The fit-gap priorities for that functional area will also be reviewed and re-ordered, as needed. Likely to require 10-15 hours of meetings per week. May be completed in 1 week or 2, depending on the number of workflows and priorities for that functional area.To-Be: During this period, the Design Team will work in meetings with Blackbaud design staff to review the As-Is workflows, discuss desired workflow changes, compare with product functionality and BB-considered "best practices" and determine where processes can/should be altered. Team will also meet with and gather feedback as available from members of the CRG. Likely to require 12-20 hours of meetings per week, depending on the number of requirements and workflows.
- During the multi-week sprint cycles, Design Team members will be needed to approve the timeline for the design sprints, confirm the items to be completed, and be available for periodic reviews of new functionality to ensure Blackbaud designers are on track. The Design Team Lead must be available (usually by phone or email) to provide quick decisions to simple questions throughout this proces (or appoint one or more designees if unavailable). Team will also gather feedback as available from members of the CRG, some of whom may be invited to the sprint demos.Likely to require 4-6 hours per week to review demos and work with BSAs to aggregate feedback. There should be little to no time needed during the 2nd week of each sprint. Additional team work during this period may include more work on data output and reporting needs as well as drafting of user tests to implement at the end of the design cycle.
- During the multi-week sprint cycles, Design Team members will be needed to approve the timeline for the design sprints, confirm the items to be completed, and be available for periodic reviews of new functionality to ensure Blackbaud designers are on track. The Design Team Lead must be available (usually by phone or email) to provide quick decisions to simple questions throughout this proces (or appoint one or more designees if unavailable). Team will also gather feedback as available from members of the CRG, some of whom may be invited to the sprint demos.Likely to require 4-6 hours per week to review demos and work with BSAs to aggregate feedback. There should be little to no time needed during the 2nd week of each sprint. Additional team work during this period may include more work on data output and reporting needs as well as drafting of user tests to implement at the end of the design cycle.
- During the multi-week sprint cycles, Design Team members will be needed to approve the timeline for the design sprints, confirm the items to be completed, and be available for periodic reviews of new functionality to ensure Blackbaud designers are on track. The Design Team Lead must be available (usually by phone or email) to provide quick decisions to simple questions throughout this proces (or appoint one or more designees if unavailable). Team will also gather feedback as available from members of the CRG, some of whom may be invited to the sprint demos.Likely to require 4-6 hours per week to review demos and work with BSAs to aggregate feedback. There should be little to no time needed during the 2nd week of each sprint. Additional team work during this period may include more work on data output and reporting needs as well as drafting of user tests to implement at the end of the design cycle.
- During the multi-week sprint cycles, Design Team members will be needed to approve the timeline for the design sprints, confirm the items to be completed, and be available for periodic reviews of new functionality to ensure Blackbaud designers are on track. The Design Team Lead must be available (usually by phone or email) to provide quick decisions to simple questions throughout this proces (or appoint one or more designees if unavailable). Team will also gather feedback as available from members of the CRG, some of whom may be invited to the sprint demos.Likely to require 4-6 hours per week to review demos and work with BSAs to aggregate feedback. There should be little to no time needed during the 2nd week of each sprint. Additional team work during this period may include more work on data output and reporting needs as well as drafting of user tests to implement at the end of the design cycle.
- During the multi-week sprint cycles, Design Team members will be needed to approve the timeline for the design sprints, confirm the items to be completed, and be available for periodic reviews of new functionality to ensure Blackbaud designers are on track. The Design Team Lead must be available (usually by phone or email) to provide quick decisions to simple questions throughout this proces (or appoint one or more designees if unavailable). Team will also gather feedback as available from members of the CRG, some of whom may be invited to the sprint demos.Likely to require 4-6 hours per week to review demos and work with BSAs to aggregate feedback. There should be little to no time needed during the 2nd week of each sprint. Additional team work during this period may include more work on data output and reporting needs as well as drafting of user tests to implement at the end of the design cycle.