Bicycle Hackerspace

There is a practice, in software engineering, of writing stories that explain a task's value proposition. A slightly formalized way of expressing needs that people automatically recognize. It is a structural pattern for a sentence:

As a [role], I want [a feature], so that [I can achieve a goal].

These are some of the core feature requirements for a productive Bicycle Hackerspace, in this case known as "The Space".

Volunteering

As a Volunteer, I want to spend some of my personal time doing things for The Space, so that I can contribute to society.

When to Volunteer (People Scheduling)

As a Volunteer, I want to know the best time for me to participate, so that I can contribute meaningfully.

The Space has limited resources, and lots of Volunteers. Prioritize use of limited resources based on the net benefit. If one person is building new storage for wheels and the other is trying different wheels on their personal bike and those projects conflict, the person building the new storage takes priority. Show good judgment and be considerate.

Customers come to The Space in waves. Focus on customer service Volunteer slots when there are lots of guests in The Space.

There are slow times at the shop. Noisy or disruptive things are better done during these times.

What to Do (Task Management)

As a Volunteer, I want to know what needs to be done, so that I can apply my time toward important things.

Some tasks may be best at certain times or on certain days.

Some tasks will have potential conflicts, like for use of a tool or station.

How to Grow

As a Volunteer, I want to gain new skills, so that I can contribute more and learn new things.

What to Grow

As a Volunteer, I want to know what skills The Space needs, so I can focus on things that interest me and help me contribute.