Meeting notes: defining personas, kickoff, ownership, process.

What is the scope of this effort?

Focus on 0.6: Personas might have needs that won't be served by 0.6 but we won't go into much detail when that arises.

Focus on OSAF Office (because of Dogfood focus for 0.6): Right now the reason why we would adopt 0.6 for dogfood usage is because of a requirement and ambition to use our own software, so the personas used for 0.6 don't need to be the normal kind of early adopter.

Focus on Calendar: Our 0.6 goals are mostly to make calendar usage possible so we'll focus on the calendaring needs of personas.

What do the personas include?

• Include "spoke" roles as well as "hub" role. The "Hub" persona (the person who connects and coordinates people and their schedules) is one we've already focused on in our ad hoc approach to use cases. We should include at least one persona that represents this role. However, because sometimes a whole team needs to choose a piece of scheduling software or a process, we should include "spoke" roles -- the people who can prevent adoption if the software doesn't work for them.

• Include techies as well as non-techies

• Include people who are interested in the plausible promise of a PIM as well as people who just want a working calendar.

Rough idea of initial personas

• A manager with a busy schedule organized by somebody else, including travel
• An office admin or assistant who schedules manager's schedule or meeting rooms
• A program manager or somebody else who coordinates a lot of work and plans meetings with attendees
• A worker bee, or somebody who doesn't coordinate other work but gets invited to meetings

Use cases will bring aspects of these personas. E.g. the person who does a lot of travel may have a use case of sharing work calendar with family members, and those family members aren't personas on their own right but are included in the persona's use cases.

What we use personas for initially

Personas will be used as input to a couple other Chandler processes:

• Product planning: help us choose, prioritize features
• Specifications: We will name and use our personas to illustrate features described in specs.

Next steps

• Chao and Mimi will work together overall on writing definitions
• Chao will do interviews to generate details for these personas -- at least one interview per persona to start with.
• Goal is to have some personas rather roughly defined in only a week's time so they can be used in 0.6 specs as examples.
• Chao will send an email to design list asking for particularly non-OSAF volunteers to participate by filling in a 15-minute survey (no obligation)

Status reporting sources

Gathering the links and list I'll need to put together a consolidated status report...

• BuildProject^?
• ServicesWorkingGroup
• Email from Sheila on Design
• RepositoryFramework
• Apps team report from Philippe?
• Email from BCM on Cosmo
• QA?