tour de dart july 2009: volunteer expectations

6
On Track Project Progress, Challenge & Triumph

Upload: umdart

Post on 17-May-2015

166 views

Category:

Technology


0 download

DESCRIPTION

What volunteers should expect

TRANSCRIPT

Page 1: Tour de DART July 2009: Volunteer Expectations

On TrackProject Progress, Challenge & Triumph

Page 2: Tour de DART July 2009: Volunteer Expectations

What to expect as a volunteer

In this section:• Tasks for community resource group volunteers

• Design Team cycles and activities• The big challenge in the Design Phase

Page 3: Tour de DART July 2009: Volunteer Expectations

What can resource group volunteers expect?

•Email notifications and invitations to

▫Review design session recordings

▫Review design team documents

▫Provide feedback to design teams

▫Test/pilot software configurations

Page 4: Tour de DART July 2009: Volunteer Expectations

What can design team volunteers expect?

1. Preparation • Prioritize gaps and

determine which solutions make the most sense

2. Create “user scenarios”

• Based on experience and knowledge of fundraising business area

• Provide a guide for Blackbaud to develop the solution, and for testing

Design Cycle Preparation

“Sprint”(Blackbaud

develops a solution)

“Test”

5 Design Teams, working in cycles

Page 5: Tour de DART July 2009: Volunteer Expectations

What can design team volunteers expect?

3. Sprint• Blackbaud

develops solution based on the Design Team’s input

4. Testing• Confirm the

solution developed by Blackbaud meets identified needs

Design Cycle Preparation

“Sprint”(Blackbaud

develops a solution)

“Test”

Sprint – 4 week period of software development by Blackbaud.

While Blackbaud is in a Sprint, the Design Team will likely be reviewing the next area and creating user scenarios.

Page 6: Tour de DART July 2009: Volunteer Expectations

Design Phase Challenge: Prioritization

“Prioritization is…very important

because we want to make sure we get

to the things that are…most

important and have the greatest impact

for the development community.”

There’s a lot of work to do before launch

Not every requirement and gap can be filled before the first release (targeted for Spring 2011)

Must be swift, efficient, and thorough

Prioritizing helps ensure the first release meets the majority of our needs