[meta] Scoping the use-case [#1354088]

Goal

Arrive at a solid vision for the product, a common denominator of use-cases.
A project page description based on that vision.

Use-cases

#1341338: A specific use-case: Freelance photographer
#1354086: A specific use-case: Personal web site
#1360570: A specific use-case: freelance musician or a band
#1361194: A specific use-case: Developer
#1361826: A specific use-case: Digital Philosopher
#1361872: A specific use-case: Book Author
#1362184: A specific use-case: Personal Chef
Personal Site Design - Developer Wanted | drupal.org

Details

As one of the first official products designed and developed by the community, we can be less strict about the scope and use-case.
As long as the intention isn't muddied and the main purpose stays the same, it should be acceptable to allow slightly different perspectives on the application.
Such a direction can easily become problematic in terms of product design and management. But it's probably legit to account for multi-purpose scenarios of a product, as long as the product's design parameters stay single-purpose.

Comments

Comment #1

yoroy CreditAttribution: yoroy commented 27 November 2011 at 20:40

No problem. These use cases are like user research: you take inventory of related but differing use cases and aim for the common challenges that are worth providing solutions for. There's a risk for too-generic in that, but if we develop a primary persona for this we have a clear focus point.

Comment #2

Grayside CreditAttribution: Grayside commented 3 December 2011 at 18:12

I'm somewhat concerned that the functionality around the photographer's gallery is a huge thing with it's own stack of specific modules. This should be a product, but getting into more than 5-6 modules for a specific person seems like a lot to me.

The core Portfolio project might have a design around a conceptual "gallery" that can be configured for Open Source Development (Drupal -> Maintained Modules), Photography (Weddings->Photos), Recipes (Vegan Menu -> Dishes), Testimonials (Private Customers -> Reviews), Writing (Short Stories -> Stories).

Comment #2.0

Grayside CreditAttribution: Grayside commented 3 December 2011 at 18:12

Issue summary:

View changes

Updated issue summary.

Comment #3

dww

we/he/they

CreditAttribution: dww commented 4 December 2011 at 10:16

I just added #1360570: A specific use-case: freelance musician or a band to the list of case studies in the summary. Hope it's useful.

Comment #4

yoroy CreditAttribution: yoroy commented 4 December 2011 at 13:07

Yes, thanks dww. At this time, the best feedback on the given use cases is adding new ones!

yoroy CreditAttribution: yoroy commented 7 December 2011 at 10:55

Issue summary:

View changes

added link, paid services forum request

Comment #6

dasjo

he/him

German

Zurich

CreditAttribution: dasjo commented 8 December 2011 at 08:04

different use cases might require different features. so i think some sort of select-possible-features-functionality to configure my portfolio site would be great. (this is what drupal gardens offers for example)

Comment #7

sun

German

Karlsruhe

CreditAttribution: sun commented 15 December 2011 at 21:33

Issue tags:

+use case

Comment #8

sun

German

Karlsruhe

CreditAttribution: sun commented 18 March 2012 at 02:42

Huge update today! :)

See:
#1372320: Document project milestones and history
#1488250: Portfolio manifesto // design parameters
+ the first 4 of 9 use-cases filled out in the new spreadsheet matrix over in #1399188: Analyze common functionality and content requirements of use-cases!

Some parts of the revised spreadsheet probably need some explanation - hope to clarify them ASAP. But anyway, I'd *love* to learn about your thoughts and questions, so please share your feedback! :)