Project Setup: Use Cases, Milestones, Roadmap

[felixboehm]

• [x] Add Features as Github Issues
• [x] Document Uses Cases in github Wiki (better ideas?)
• [ ] Define a Tag per Use Case and add it to Feature Issues
• [x] Highlevel Roadmap
• [x] Planning
• [x] Kanban Board

Maybe there is a better way to have Use Cases documented and Features linked to them?

We should also try the github "Discussions" for Ideas, Brainstorming, Discussing and decisions in the team.

---

Use Cases

Main - Motivation

• While traveling I want to find communities in the location I will go next.

OnBoarding and Discovery

• As a User I want to find people and activities around me based on my interests
• As a User I want to discover interests around me to develop my interests, then connect and learn upon them.

Discover local Communities, People and Activities

• Meet likeminded people in your area
• While traveling I want to find communities in the location I will go next.

My Communities

• Discover for yourself what are your interests
• Stay active in communitites which are important for you Participate in local Communities

Connecting

Governance / Trust

• As a “Community Manager” I want to create and grow a Community. Ownership should lie with the Community contributors and more active and trusted members should be able to govern transparently.
• As a passive member of a Community I want to delegate (liquid vote) trust to contributors to support them growing the Community.

[JKawohl]

• [ ] Add Features as Github Issues

• Agreed

• [ ] Document Uses Cases in github Wiki (better ideas?)

• It depends, if use cases are meant as user stories, i would create issues for them and tag them with approbiate tags, that are then linked to the feature. It all depends on the hierarchy -> A Feature can consist of n user stories / use cases. Should the user stories / use cases inherit the tag from the feature? Or vice versa ? -> I am open to this, both ways work. Allthough we would have probably mor tags for use cases than for Features, which could get confusing in hindsight.

• [ ] Define a Tag per Use Case and add it to Feature Issues

• please see above.

• [ ] Setup Basic Roadmap in github Projects Agreed

• [ ] Kanban Board? Yes! Especially for planning, backlog grooming etc.

Maybe there is a better way to have Use Cases documented and Features linked to them?

• As above It depends, if use cases are meant as user stories, i would create issues for them and tag them with approbiate tags, that are then linked to the feature. It all depends on the hierarchy -> A Feature can consist of n user stories / use cases. Should the user stories / use cases inherit the tag from the feature? Or vice versa ? -> I am open to this, both ways work.

We should also try the github "Discussions" for Ideas, Brainstorming, Discussing and decisions in the team.

• Agreed