r9 - 12 Jul 2007 - 08:35:15 - MimiYinYou are here: OSAF >  Journal Web  >  ContributorNotes > PriscillaChungNotes > CosmoTargetUserDescriptions

Draft Cosmo Target User Descriptions (Take Two)

In progress

Here is a list of target users to help classify different types of users which have been brought up various times on the design list. Though it's possible after Preview there might be other users we have not defined here. This is just a tool for us to help identify users so that we are able to base prioritize features based on the user's needs. Satisfying one user base may also overlap other target user's needs even though they are not the target user we are currently satisfying for that particular release. Ideally when we hear feedback from users who are dogfooding the application, we would try and prioritize features so that we can also satisfy their needs as well.

Cosmo Target Users for Preview

End-user Casual Collaborator (CC) - A light CC user (not using the application regularly) who has clicked on a URL/ticket sent from a Chandler user. A heavy CC user (using the application regularly) who is not only using the CC UI (PIM features). Though is not an administrator. See CC diagram. Created back in May 2006

OSAF Administrator - tools for the administering hosting Chandler Hub.

An example relationships between the CC and the Chandler desktop user are:

  • CC could be another Helen the Hub, Bart the Busy Body, Angie the Apex, Eli the Executive Assistant or Ivan the Individual Contributor. See target user descriptions.
  • CC could be in the same working group as Helen the Hub or outside of the working group
  • CC does not use Chandler desktop to manage their information, however, CC does need to collaborate with Helen the Hub on a periodic basis
  • Collaboration can be sparse (a few times a month) to frequent (a few times a week)

The nature of collaboration between the CC and the Chandler desktop user is relatively low. For example:

  • Checking on Helen the Hub's schedule
  • Adding personal PTO time to a shared group calendar
  • Updating status on a task in a group task dashboard
  • Checking status on tasks in a group task dashboard

Collaboration that is not supported by Preview. Example:

  • The heavy back and forth collaboration such as like Angie the Apex and Eli the Executive Assistant managing and negotiating Angie's schedule.


Cosmo Target Users for Post Preview

This a proposal for target users Post Preview. Note the definitions below could all change once Preview is released.

The goal for defining the target user for Cosmo post preview may be to continue down the path in driving more heavy duty collaboration between the CC and the Chandler Desktop. For example, collaboration between Helen the Hub and Bart the Busy Body editing back and forth on a single item to draft a proposal. There will also be consistent improvements to performance and stability of the application in addition to feedback from users outside the company.

Target users defined for Chandler Hub and Server post preview. There is always some end user and a power user for each category.

  • Power end-user CC - A CC who may be more committed in using Cosmo more frequently. Would most likely have set up an account and know what they are doing when looking through their 'Account Browser'. Uses the Cosmo interface to work with Chandler desktop users along with file sharing. Might be needing to use this for debugging purposes. Might use file sharing on Chandler Hub.

  • Stand-alone
    • Stand-alone calendar user - A user who has set up OSAF bundle on their own personal server, uses the web-based calendar from the OSAF bundle and does not use Chandler desktop.
    • Generic administrator (downloaded OSAF bundle and is the administrator of their own server) - A user who has downloaded and set up Cosmo on their own server. Admin privileges, primarily viewing account list. My also be a stand-alone calendar user.
    • End-user file share user - A user who is only using Cosmo as a file sharing server. Does not use the calendar interface to share collection information with a Chandler desktop users. Account might have been set up by the Generic Admin.

  • Desktop remote
    • Chandler desktop users (Consultative User) who are reading their calendars on Chandler Hub This implies casual use, meaning that the experience should be as lightweight as possible - no login required. This may be only 10% of Chandler desktop remote users. See What's blocking Consultative usage of Cosmo.
    • Chandler desktop remote user who is using Chandler Hub as their primary calendar + tasks (personal information manager, PIM). They are using Chandler desktop in conjunction with Chandler Hub regularly, perhaps between two machines (work + home). They keep their browser open all day while work and manage their time, make meeting requests and coordinates w/ a small group using Chandler Hub. Having the application open all day is the equivalent of using other AJAX web based e-mails such as GMail, Yahoo Mail (beta). This may imply Cosmo to have all or has enough features as Chandler Desktop.

  • Data hub developer
    • Generic developer (downloaded OSAF bundle and is the administrator of their own server) - A user who has downloaded and set up Cosmo as their own server. May or may not be using the calendar interface but sets up some other application to run on Cosmo. ie. foxmarks develop their own application for their using it as their platform. (webDAV, or some other Hub.)

Second Draft Ends Here.


Notes from PPD Meeting:

  • the consultative 10% of the chandler desktop remote

*person running it at home

  • person running it for small business
  • person organizing it for a service

  • early adopters as file sharing

  • All types of users have a power users vs. end users.


First Draft of Target Users Descriptions

There was an attempt to have this isolate who the target users are for Cosmo 1.0 release.

Chandler Hub Target User

  • Casual Collaborator (CC) - Non-Chandler users viewing calendars published from Chandler. This is the target user we are focused satisfying for Preview.

  • Consultative Chandler Users - Chandler users reading calendars on the web using Cosmo. This implies casual use, meaning that the experience should be as lightweight as possible - no login required.

We are aware there are other users who are using Cosmo Hub and Server. Here is an attempt to describe these other target users which for now, are not our primary focus for the Cosmo 1.0 release. Note the features which fall under the the CC, will be useful to these other types of users.

Additional Chandler Hub Target User

  • Stand alone calendar user - A user who is using Chandler Hub on an independent server, not osaf.us. The user uses the web-based calendar from the OSAF bundle and does not use Chandler desktop.

  • Chandler remote user - A user who is using Chandler Hub as their primary calendar + tasks (personal information manager, PIM). They are not using Chandler desktop or is using both regularly perhaps between two machines (work + home). They keep their browser open all day while work and manage their time, make meeting requests and coordinates w/ a small group using Chandler Hub. Having the application open all day isthe equivalent of using AJAX web based e-mails such as GMail, Yahoo Mail (beta).

Related links:

  • Mimi's notes on the comparison of features for the CC and the Consultative Chandler User: What's blocking consultative usage of Cosmo?
  • Specific workflows described for the Cosmo 0.6 and Preview target user.


Chandler Server Target User

Defining the 'Administrator' target users

Also found described from Cosmo 0.6 spec. Here is a list of target users to help classify different types of users which have been brought up in discussion on the design list:

  • OSAF administrator - tools for the admin hosting Cosmo on osaf.us
  • End-user Casual Collaborator (CC) - A light CC user who has clicked on a URL/ticket sent from a Chandler user. A heavy CC user who is not only using the CC UI (PIM features) but also using it for filesharing. Though is not an administrator.
  • Power end-user CC - A CC who may be more committed in using Cosmo more frequently. Would most likely have set up an account and know what they are doing when looking through their 'Account Browser'. Uses the CC UI to work with Chandler users along with file sharing. Might be needing to use this for debugging purposes. Might use file sharing.
  • Generic administrator (downloaded OSAF bundle and is the administrator of their own server) - A user who has downloaded and set up Cosmo on their own server. Admin privileges, primarily viewing account list.
  • End-user file share user - A user who is only using Cosmo as a file sharing server. Does not use the CC UI to share collection information with a Chandler user.
  • Stand alone calendar user - A user who has set up Cosmo on their own personal server, uses the web-based calendar from the OSAF bundle and does not use Chandler.

Some features will overlap, but the UI features listed in 0.6 are primarily focused on the top three users listed above; OSAF Admin, CC end user and the CC power user.

Next actions:

  • Confirm target users for Chandler Hub/Server for Preview. Perhaps for 1.0?
  • Confirm on the design list (tagged w/ Cosmo)?
  • Add target users to 0.7 spec.—start writing 0.7 spec. wink

-- PriscillaChung - 20 Mar 2007

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r9 < r8 < r7 < r6 < r5 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.