Agenda

• Target Users: Web 2.0
• Scooby 1.0 Vision
• 6 month plan
• 0.2 plan
• What's our process for Scooby product planning?

Assumptions

• Not to block 0.2 development
• Product process-->move faster/shorter release cycles then Chandler

Goals (3 month plan)

• Data availability = "The data you have is the data you see"

0.2 Plan (3 month goal: data integrity)

• continue down the 2 month plan (original May deliverables)
• Jump to field
• Subscriptions needed to show up in scooby as well as published calendars-->send to design list
• Timeline on the left
• Visual tweaks-->consistent to Chandler
• Overlapping events displayed correctly (3 months?)
• TZ display correctly (3 months?)
• Basic mini cal (ask for SWAG, might be 6 months)
• Special Chandler event types display correctly in Scooby (@time, anytime events)

6 month UI explorations

• navigation
• calendar canvas/data display
• editing and creating new events
• (internal visual exploration) - "Take it or leave it" need to meet immediate needs in a low impact way. Introduce this design process to the list.

-- use cases & exploration--ppl send to scooby list of their favorite [blah] ie. navigation, design sessions

1.0 Plan Target User

• CSG University
  • admin staff
  • students
• Possibility of using calendars
• Check university calendars
• Kiosk-->access personal information

1. Who are users? *University execs.-Blackberries (probably not a target user?)

• staff
• admin
• students

2. Scenarios

1. kosk (specific user case) --> where is my class?
2. web access" public stuff university -->football game this weekend?

3. Environment --> need to interview small collages (come up with list)

• Exchange
• Oracle (calDev)
• Some mixture

Need to do Scooby 1.0 (further discussion)

• tenets
  • Slick look and feel � la "take it or leave it"
  • Might be to just have one department (student union) or wireless sync (side kicks)
• target users
• use cases